GPN23:NOC

Wireless

You can find the WiFi credentials below

SSID	Authentication	Security
GPN-Open		WPA3 OWE/WPA2 open
GPN-PSK	IoT-at-GPN	WPA3 SAE/WPA2 PSK
GPN	gpn/gpn	WPA3/WPA2 enterprise

Contact

WPA-Enterprise

WiFi-Credentials

Username	Password	Mode
gpn	gpn	Default. Protected; no inbound connections allowed
event-inbound-only	event-inbound-only	Inbound connections only allowed from the Event Network
yolo	yolo	Yolo-Mode; Inbound allowed from anywhere

Configuration on Apple Devices

You can configure the WiFi yourself, or use our provided signed profiles for the different modes:

These will be provided shortly.

If you don't use the profiles, you must click trust on the certificate for radius.noc.gulas.ch.

Configuration on most systems

Username/Identity: see above
Password: see above
(only on MacOS) Identity: none
Domain: radius.noc.gulas.ch
CA certificate: Use system certificate or Trust on first use (on modern Android Devices)
- Otherwise use the ISRG Root X1 from Let's Encrypt.

If you want to check that you really connect to the insecure network of your choice, please verify the certificate of CN radius.noc.gulas.ch is issued by Let's Encrypt.

You can find example configs on GPN23:NOC/Wireless

GPN-Open WPA3 OWE

WPA3 Opportunistic Wireless Encryption will use an individualized encryption after joining the GPN-Open network.

Android

After connecting you will see "enhanced open" as connection type.

Linux NetworkManger (nm)

GUI on some systems has issues connecting. Connecting via CLI works: nmcli device wifi connect GPN-Open

Wireless FAQ

iwd does not configure the default route

iwd together with EnableNetworkConfiguration=true has been reported to not configure the routes received via DHCP. Workaround: Use an other DHCP Client.

Colocation

Like the years before we are providing a colocation at GPN.

In case of problems, find us at the NOC desk or call DECT 6620.

We will try to provide the colocation as best effort. Normal GPN-Network has priority.

You should be able to use the colocation starting Thursday afternoon.

We close the colocation on Sunday 12:00 PM , please fetch your devices before then!

Location

This year it is most likely on the Lichtbrücke. More Information is available at our Help-desk.

This area is off limits - please ask the Help-desk to bring you there. This area is not locked! We are not responsible for any physical security of your equipment, please take own precautions if necessary.

This location has limited power budget and cannot accommodate for power hungry devices.

Basic Rules and Policy

Be excellent to each other!
we reserve the right to disconnect your server
access is only allowed in the presence of NOC staff
devices must be labeled with an e-mail-address and a DECT-Number (if you have one)
prepare your server before placing it in colocation. Outside of placing and picking up, we can only grant access to the colocation in exceptional cases

How to connect

bring you own SFP(+)/SFP28 transceivers and cables (we do not have any cables or transceivers for the colocation)
add a label with your e-mail(must) / DECT(should) on any devices in the colocation
talk to NOC
- you will receive a label with an IP-address (v4/v6)
- only NOC will provide access to the colocation

How to retrieve your server

shutdown your server remotely (minimize time spent in colocation)
talk to NOC
- is your server powered off?
- NOC will provide access to the colocation
- collect your server

Connection/Uplink

Your server can connect with a SFP/SFP+/SFP28 (1/10/25G) to our YoloColo-Switch.

We provide an additional 1G RJ45 Switch.

Metrics

If you're interested in some metrics about the NOC operations, visit our publish dashboard.

Pixelflut

Pixelflut is not hosted by NOC. Some people are building a completely separate network just for Pixelflut. You can find more information here: GPN23:Pixelflut