GPN22:NOC

Wireless

You can find the WiFi credentials below

SSID	Authentication	Security
GPN-Open		WPA3 OWE/WPA2 open
GPN-PSK	IoT-at-GPN22	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:

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 GPN22: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 has on some systems issues connecting. Connecting via CLI `nmcli device wifi connect GPN-Open`

Colocation

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

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 (timestamp will be added soon), please fetch your devices before then!

Location

This year it is in the Pförtnerhäuschen, which is the locked space that housed the YoloColo back at GPN19.

This location has limited cooling and 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(+) 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 clothespin with an IP-address (v4 and v6)
- NOC will provide access to the colocation
- NOC will verify the label with the DECT-number on the server
- exchange PSK with NOC (you will need your DECT or PSK to retrieve your server)

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
- verify yourself with DECT or PSK
- collect your server

Connection/Uplink

YoloColo is connected with 100G to our core.

Your server can connect with 10G to our YoloColo-Switch.

Addressing

IP addressing is static only. We use "Laundry Clip DHCP": Get your laundry clip at the NOC Desk and attach it to your network cable. Please bring back the laundry clips after the event.

Configure your network interfaces like shown below (X is your laundry clip number).

IPv4

Address: 151.216.65.X/24

Gateway: 151.216.65.1

IPv6

Address: 2a0e:c5c1:0:10c9::X/64

Gateway: 2a0e:c5c1:0:10c9::1

Pixelflut

Pixelflut is not hosted by NOC. Some people create a completely separated and isolated network with no access to the GPN-Network.

You will find a dedicated switch for Pixelflut in the YoloColo. Having two network-cards is recommended. You can find more information here: GPN22:Pixelflut