Ember (Diskussion | Beiträge) K (make map link englisch) |
Ember (Diskussion | Beiträge) K (readability fixes) |
||
Zeile 55: | Zeile 55: | ||
==== Configuration on Apple Devices ==== | ==== Configuration on Apple Devices ==== | ||
You can configure the WiFi youself, or use our provided signed profiles for the different modes: | |||
* [https://cloud.entropia.de/s/s2K2DMf3N7jCzp9/download?path=%2F&files=GPN%20-%20Isolated%20WiFi-Signed.mobileconfig Normal, protected] | * [https://cloud.entropia.de/s/s2K2DMf3N7jCzp9/download?path=%2F&files=GPN%20-%20Isolated%20WiFi-Signed.mobileconfig Normal, protected] | ||
Zeile 62: | Zeile 62: | ||
==== Configuration on most systems ==== | ==== Configuration on most systems ==== | ||
*Username/Identity: see above | |||
*Password: see above | |||
*Domain: <code>radius.noc.gulas.ch</code> | |||
*CA certificate: <code>Use system certificate</code> or Trust on first use (on modern Android Devices) | |||
**Otherwise use the [https://letsencrypt.org/certs/isrgrootx1.pem ISRG Root X1] from [https://letsencrypt.org/certificates/ 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 <code>radius.noc.gulas.ch</code> is issued by [https://letsencrypt.org/certificates/ Let's Encrypt].<div class="home-card home-card--col2"> | If you want to check that you really connect to the insecure network of ''your'' choice, please verify the certificate of CN <code>radius.noc.gulas.ch</code> is issued by [https://letsencrypt.org/certificates/ Let's Encrypt].<div class="home-card home-card--col2"> | ||
=== Colocation === | === Colocation === | ||
Like the years before we are | 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. | 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 ==== | ==== Location ==== | ||
Zeile 82: | Zeile 85: | ||
This location has limited cooling and power budget and cannot accommodate for power hungry devices. | This location has limited cooling and power budget and cannot accommodate for power hungry devices. | ||
==== Basic Rules and Policy ==== | |||
==== Basic Rules and | |||
* be excellent to each other! | * be excellent to each other! | ||
* we reserve the right to disconnect your server | * we reserve the right to disconnect your server | ||
* access is only allowed in the presence of NOC staff | * access is only allowed in the presence of NOC staff | ||
* devices must be labeled with an | * 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. | * prepare your server before placing it in colocation. O utside of placing and picking up, we can only grant access to the colocation in exceptional cases | ||
==== How to connect ==== | ==== How to connect ==== | ||
* bring you own SFP(+) transceivers and cables (we do not have any cables or transceivers for the colocation) | * bring you own SFP(+) transceivers and cables (we do not have any cables or transceivers for the colocation) | ||
* add a label with your | * add a label with your e-mail(must) / DECT(should) on any devices in the colocation | ||
* talk to | * talk to NOC | ||
** you will receive a clothespin with an ip-address (v4 and v6) | ** 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 | ** exchange PSK with NOC (you will need your DECT or PSK to retrieve your server) | ||
==== How to retrieve your server ==== | ==== How to retrieve your server ==== | ||
* shutdown your server remotely (minimize time spent in colocation) | * shutdown your server remotely (minimize time spent in colocation) | ||
* talk to | * talk to NOC | ||
** is your server powered off? | ** is your server powered off? | ||
** | ** NOC will provide access to the colocation | ||
** verify yourself with DECT or PSK | ** verify yourself with DECT or PSK | ||
** collect your server | ** collect your server |
Version vom 27. Mai 2024, 20:06 Uhr
Wireless
You can find the WiFi credentials below
SSID | Authentication | Security |
GPN-open | WPA3 OWE/WPA2 open | |
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 youself, or use our provided signed profiles for the different modes:
Configuration on most systems
- Username/Identity: see above
- Password: see above
- 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.
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. O utside 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
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 on the YoloColo. Having two network-cards is recommended. You can find more information here: GPN22:Pixelflut
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 this (X is your laundry clip number):
IPv4
Address: (will be added soon)
Gateway: (will be added soon)
IPv6
Address: (will be added soon)/64
Gateway: (will be added soon)