Internet & Network Access

From LCA2014 Delegate Wiki
Revision as of 19:43, 6 January 2014 by Martin Krafft (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  • All conference wireless access points will broadcast the SSID 'lca2014', and are secured with a WPA and WPA2 PSK of 'linuxconfau'. As always, it is considered best practice to consider the conference network as a "hostile" network, and secure your laptops and mobile devices appropriately. If you join the lca2014 wireless network and receive a private IP address, or an IP address that is not part of the above range, please let the network team know immediately (see below).
  • The IPv4 range for delegates is 182.255.120.0/22 and is provided via DHCP on both the wired and wireless network.
  • The IPv6 prefix for the delegates is 2001:388:a098:120::/64, and announced via route advertisements on our edge router for stateless autoconfiguration. IPv6 is currently not yet working on wireless links, the network team is working on it.
  • With thanks to our friends at BigAir Community Wireless, cabled internet is available in most rooms in Trinity and St George's college accommodation as of Friday (3rd January) afternoon. we've taken over their network within the ressies, and will be using this to extend the conference network into the university accommodation. Limited wireless internet access will be available within the two conference accommodation colleges Trinity and St George using the BigAir AP equipment. As delegates you will need to provide your own data cable to connect to the University accommodation network ports.
  • If you experience any issues with the conference network, or need to contact the network team, you can email the networks team at 'network@lists.lca2014.linux.org.au' or tweet us at '@LCAnetworks'. If you can give us any extra details, including some local machine log, traffic info, room numbers, along with a contact number, that'd be great!
  • It's worthwhile implementing the great fix Andrew Pam pointed out last year if you're the victim of a rogue DHCP server, by adding a reject rule to /etc/dhcp/dhclient.conf (or equivalent);
# cat /etc/dhcp/dhclient.conf

##
#see http://lists.lca2013.linux.org.au/pipermail/chat_lists.lca2013.linux.org.au/2013-January/000428.html
##

reject 192.168.0.0/16;
reject 172.16.0.0/16;
reject 10.0.0.0/8;