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.

Wireless

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

CCC SSIDs

The following SSIDs are provided:

  • 30c3 (WPA2 802.1X (see below), 5GHz)
  • 30c3-legacy (WPA2 802.1X (see below), 2.4GHz)
  • 30c3-open (open, 5GHz)
  • 30c3-open-legacy (open, 2.4GHz)
  • spacenet (federated hacker authentication system, see https://spacefed.net/wiki/index.php/30c3)

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 "30c3/30c3" or "guest/guest" as "username/password".

Client Settings

SSID: 30c3 or 30c3-legacy
Phase 1: EAP-TTLS or PEAP
Phase 2: MSCHAPv2 or EAP-MSCHAPv2 or PAP

CN = eventradius.spacefed.net
CA = StartCom
Fingerprint = 88:4C:4F:41:C0:24:C8:53:87:10:1E:8F:90:22:F3:67:F2:B1:32:79

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). The certificate that is installed on the RADIUS server is same as for the local spacenet-service, it is signed by StartCom (aka StartSSL) of which the root-certificate should be pre-installed on most devices. Check here to see more information about the certificate that is installed.

WICD

You need an additional crypto setting for WiCD. Put this file into /etc/wicd/encryption/templates/eap-ttls (debian systems, might be different with other *nix flavours):

name = EAP-TTLS 30c3
author = Felicitus
require identity *Identity password *password
-----
ctrl_interface=/var/run/wpa_supplicant
network={
 ssid="$_ESSID"
 scan_ssid="$_SCAN"
 identity="$_IDENTITY"
 password="$_PASSWORD"
 proto=WPA2
 key_mgmt=WPA-EAP
 group=CCMP
 pairwise=CCMP
 eap=TTLS
 ca_cert="/etc/ssl/certs/StartCom_Certification_Authority.pem"
 anonymous_identity="$_ANONYMOUS_IDENTITY"
 phase2="auth=PAP"
 #priority=2
}

Edit /etc/wicd/encryption/templates/active to include the eap-ttls config template. Restart the WiCD daemon, choose the proper encryption (EAP-TTLS 30c3) and enter a random username/password.

Jolla/connman

/var/lib/connman/30c3wifi.config :

[service_30c3]
Type=wifi
Name=30c3-legacy
EAP=peap
Phase2=MSCHAPV2
Identity=$_IDENTITY
Passphrase=$_PASSWORD
wpa_supplicant.conf

/etc/wpa_supplicant/wpa_supplicant.conf :

network={
	ssid="30c3"
	key_mgmt=WPA-EAP
	eap=TTLS
	identity="fpletz"
	password="fpletz"
        # ca path on debian 7.x, modify accordingly
	ca_cert="/etc/ssl/certs/StartCom_Certification_Authority.pem"
        subject_match="CN=eventradius.spacefed.net"
	phase2="auth=PAP"
}
interfaces

As an alternative, you can specify the wpa_supplicant config options directly in /etc/network/interfaces:

iface wlan0 inet dhcp
	wpa-ssid 30c3
	wpa-identity edward
	wpa-password snowden
	wpa-proto WPA2
	wpa-key_mgmt WPA-EAP
	wpa-group CCMP
	wpa-pairwise CCMP
	wpa-eap TTLS
	wpa-phase2 "auth=PAP"

Services

Last year we had separate SSID's 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:

  • fixip/fixip (for the Fixed-IP VLAN - get your static IP at the NOC Helpdesk)
  • nat64/nat64 (for the nat64 VLAN)
  • 30c3/30c3 or guest/guest (for regular user VLAN - for devices that have correctly implemented MSCHAPv2, like Windows)

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.

Rules

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. Wireless experimentation is only allowed in the hackcenter, 2.4GHz at channel 1 (2412MHz, 20MHz channel) and 5GHz at channel 36 (5180MHz, 20MHz channel). When we find you, the AP is ours!

Helpdesk

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.

NAT64/DNS64

Please see the NAT64 page for more details.

Supporters

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-a10 logo-sm.jpg http://www.a10networks.com/ A10 hardware loan from BMA Networks
Supporter-atrato.jpeg http://www.atrato-ip.com IP Uplink
Supporter-babiel.jpg http://www.babiel.com/ Servers
Supporter-flexoptix.jpeg http://www.flexoptix.net Optical Networking Equipment
Supporter-ghip.jpeg http://www.ghipsystems.com/ Optical Networking Equipment
Supporter-iphh.gif http://www.iphh.net/ Colocation / Logistics
Supporter-Juniper.gif http://www.juniper.net/ Network Equipment
Supporter-kaia.png http://www.kaiaglobal.com/ IP Uplink
Supporter-kpn.jpeg http://www.kpn-international.com IP Uplink
Supporter-Ruckus.png http://www.ruckuswireless.com Wifi Network Equipment
Supporter-rrbone.png https://www.rrbone.net/ IP Uplink