Ember (Diskussion | Beiträge) (add wifi credentials) |
|||
Zeile 7: | Zeile 7: | ||
{| | {| | ||
|'''SSID''' | |'''SSID''' | ||
|''' | |'''Authentication''' | ||
|'''Security''' | |'''Security''' | ||
|- | |- | ||
Zeile 15: | Zeile 15: | ||
|- | |- | ||
|GPN | |GPN | ||
| | |see below | ||
|WPA3/WPA2 enterprise | |WPA3/WPA2 enterprise | ||
|} | |} | ||
Zeile 33: | Zeile 33: | ||
</div></div> | </div></div> | ||
<div class="home-card home-card--col2"> | === WiFi-Credentials === | ||
Normal, protected WiFi: | |||
{| | |||
|'''Username''' | |||
|'''Password''' | |||
|'''d''' | |||
|- | |||
|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 | |||
|} | |||
*for PEAP/MSCHAPv2 and most others: | |||
**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 | |||
*for TTLS/PAP**Domain: <code>radius.noc.gulas.ch</code> | |||
**Everything else: <anything you like - we don't care>. If you don't use the above credentials, you will be put in the protected pool. | |||
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, once more, providing a colocation at GPN22. | Like the years before we are, once more, providing a colocation at GPN22. |
Version vom 27. Mai 2024, 19:37 Uhr
Wireless
You can find the WiFi credentials below
SSID | Authentication | Security |
GPN-open | WPA3 OWE/WPA2 open | |
GPN | see below | WPA3/WPA2 enterprise |
Contact
WiFi-Credentials
Normal, protected WiFi:
Username | Password | d |
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 |
- for PEAP/MSCHAPv2 and most others:
- Username/Identity: see above
- Password: see above
- Domain:
radius.noc.gulas.ch
- CA certificate:
Use system certificate
or Trust on first use
- for TTLS/PAP**Domain:
radius.noc.gulas.ch
- Everything else: <anything you like - we don't care>. If you don't use the above credentials, you will be put in the protected pool.
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, once more, providing a colocation at GPN22.
In case of problems, find us at the NOC desk or call DECT 6620.
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.
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!
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 email-address and a DECT-Number (if you have one). Any other information is voluntary
- prepare your server before placing it in colocation. We can only grant access to the colocation in exceptional cases outside of placing and picking up
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 email(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)