From 33C3_Public_Wiki
Jump to: navigation, search

There will be a network! Available in both wired and wireless flavours Be sure to read the Survival Guide before connecting your devices.

Rules of Conduct

  • Be fair! Do not do to others what you do not wish done to yourself!
  • Protect your computer! We cannot be held responsible for any damage your computer may face due to attachment to our network. Be reminded that both internet access and the local network are unfirewalled and unfiltered. Even well-maintained systems can be attacked and get hacked, even more so at a hacker event.
  • Do not run your own DHCP server! Doing so is harmful.
  • Do not send IPv6 Router Advertisements.
  • Do not ARP spoof or otherwise impede the operation of the network!
  • While we are generally quite able to find and disconnect you in case of network misuse if necessary, we still prefer to not have to do so and that everybody respects the other visitors.
  • Think twice before you do something that affects others! If you hack someone, you might be prosecuted. Be aware that we cannot prevent law enforcement from acting within or related to our network.


You can't live without wireless access, so we've built an awesome wireless network again. The setup is improved from last year:


The following SSIDs are provided:

  • 33C3 (WPA2 802.1X (see below), 5GHz)
  • 33C3-legacy (WPA2 802.1X (see below), 2.4GHz)
  • 33C3-open (open, 5GHz)
  • 33C3-open-legacy (open, 2.4GHz)
  • spacenet (federated hacker authentication system, WPA2 802.1X, 5GHz)
  • 33C3-PSK (WPA2 PSK, shared private SSID for 33C3 teams/projects using non-802.1X capable devices, 2.4GHz)

WPA2 802.1X, encryption

Due to popular demand (and with security in mind) we provide WPA2 802.1X. This will encrypt your traffic, preventing attackers from sniffing your data. Keep in mind that this won't protect you from other network attacks and you should still be aware that you are at a hacker conference! Your link layer should be secure if you do certificate checking (see below).

You might think: "WTF!? Do I need to register a user and password blah, blah". Fortunately not. You can use any username/password combination using EAP-TTLS with PAP to login (example: "user: fbhfbhiaf pass: bgufwbnkqo" is valid), because we don't care who logs in and who you are. We just want to encrypt your data.

Users which use MSCHAPv2 (like Windows users with default 802.1X supplicant) should use a fixed username and password. You can use "33C3/33C3" or "guest/guest" as "username/password".

Client Settings

Also see Network/802.1X client settings for a list of OS-specific client settings.

SSID: 33C3 or 33C3-legacy


Phase 1: EAP-TTLS
Phase 2: PAP


Phase 1: PEAP
Phase 2: MSCHAPv2 or EAP-MSCHAPv2 or PAP

CN =
CA = DST Root CA X3
SHA256 Fingerprint = 4F:96:E5:AD:0B:D1:20:B7:D9:5F:C0:EB:0E:63:68:3D:B2:2B:58:F7:CB:B4:FE:F2:9A:5A:79:8D:EC:35:03:74

Make sure you check the certificate in order to know you are connecting to the correct network (you should check on both the CN and the CA). Check here for the complete certificate.

Services / VLANs

Previously there were separate SSID's available for additional services like Fixed-IP. This year we're using WPA2 802.1X to push your client in the correct VLAN. The reason we are doing this is to keep the number of SSID's per wireless band to a minimum; this way we are saving airtime by not wasting it too much with 802.11 beacons/mgmt-frames. Use the following user/password combinations:

  • nat64/nat64 (for the nat64 VLAN)
  • fixip/fixip (fixed IP - to be confirmed)
  • 33C3/33C3 or 33c3/33c3 or guest/guest (for regular user VLAN - for devices that have correctly implemented MSCHAPv2, like Windows)

Please note the username AND password are case-sensitive.

2.4GHz & 5GHz

The 2.4GHz spectrum is very limited. Previously we've tried to use the vendor implemented workarounds like band-steering and band-select to persuade clients to use 5GHz. This might work in a controlled enterprise environment, but it doesn't work with 5000 hackers with 50 different operating systems.

The default SSIDs are 5GHz only. The "legacy" SSIDs are 2.4GHz only. If your client supports both, don't use the *-legacy SSIDs. If you only see the legacy SSIDs, consider upgrading your device. We cannot guarantee that 2.4GHz works.


To keep the wireless working for you, keep a few things in mind:

  • We're aware you can break the WiFi infrastructure. We're hoping that you won't and don't want to be chased by 5000 hackers through Hamburg.
  • If you want to download terabytes of data, you might be better off connecting to the wired network
  • Don't set up any of your own access points.


If you have questions about the network or need help connecting or want to drop off a server for collocation during the event, drop by the friendly people of the NOC Helpdesk, located near the Infodesk in the Main Foyer.


Please see the NAT64 page for more details.


This is a list of companies providing network hardware and connectivity services. The event would not have been possible without their support (and a few unlisted), and we thank them for it.

Who For
Supporter-aruba-hpe.png WiFi Network Equipment
Supporter-babiel.jpg Servers
Supporter-corebeerbone.gif IP Uplink
Supporter-dtag.png IP Uplink
Supporter-ecix.png Peering Port
Supporter-eventinfra.png Network equipment loan
Supporter-flexoptix.jpeg Optical Networking Equipment
Iphhlogo neu.png Colocation / Logistics
Supporter-juniper.png Network Equipment
KPN Logo.png IP Uplink
Supporter-lonap.png Network Equipment
Supporter-lwlcom.png IP Uplink
Supporter-pylonone.png WiFi Network Equipment
Supporter-servtec.gif Dark fibre uplink
Supporter-teamix.png Network Equipment


The CCC NOC team has a Twitter account: @c3noc