Understanding UCC's network can be a bit challenging at first, but after some reading you'll find that it is actually very challenging, and give up. This article is a general overview of how it works.
There is a CAT6 cable running straight up out of the Guild machine room, along the rafters and back down into the UCC machine room, terminated on a block on the North machine room wall.
In addition, there is a long piece of CAT5 (that was previously the primary uplink!) running through the walls from the machine room to the Guild machine room in Cameron Hall (across from UWAnime). If you're looking for where the cable runs, it's possibly disguised as a network outlet cable in one of the other student clubrooms.
In the Guild machine room is a Cisco 3508XL called sesame Cisco 4507 called lard but in DNS as sesame. This connects to the CAT5/CAT6 above and to single mode fibre, which runs into an ITS managed distribution switch located in the Science library and is imaginatively titled science-dr-01.
The machine room contains four switches and a router:
Murasoi, a linux-based router running iptables.
Kerosene, a Cisco Catalyst 4506-E running IOS which has a Supervisor 6-E engine, 96 GigE ports and 2 10GE-capable X2 slots.
These are all labeled and in the rack. There is also a patch panel for the clubroom wall-ports at the bottom of the right-most rack beneath Bitumen.
There is CAT5 cabling run from a patch panel at the bottom of the rack to a number of wall ports throughout the room. Where not enough wall-ports are available, there are small 5-port unmanaged switches used to attach more devices to the network.
The wireless network is also available in the clubroom.
See also: Network/SwitchConfiguration
UCC uses seven VLANs internally for various purposes:
- VLAN 1: Network and server management.
- VLAN 2: Machine room network.
- VLAN 3: Clubroom network.
- VLAN 4: Member VM network
- VLAN 5: Loft network (used for LANs).
- VLAN 6: Authenticated wireless network.
VLAN 7: IoT device network (wired & wireless).
VLAN 8: Untrusted wireless network. (deprecated)
ITS trunks to us the following VLAN:
- VLAN 13: Our main uplink, provides us our internet connection and address space.
Layer three at UCC is reasonably straightforward these days. A brief summary:
There are a number of IP ranges used at UCC for various things:
- 126.96.36.199/24 is the public address space for our AARNet connection. This range is routed to us via VLAN 13.
- 188.8.131.52/26 is the machine room address range, internally routed on VLAN 2.
- 184.108.40.206/26 is the clubroom address range, internally routed on VLAN 3.
- 220.127.116.11/26 is the member VM address range, internally routed on VLAN 4.
- 192.168.2.0/24 is the management VLAN IP range. This is not allocated to us by UWA and not routed outside UCC.
192.168.9.0/24 is the Virtual UCC (VUCC) network (ask [FVP]), routable via vucc0.ucc.asn.au (18.104.22.168)
- 192.168.13.0/25 is the uplink range, routed on VLAN 13 by UWA. Machines colocated in Arts have addresses in the top half of this /24 (i.e. 192.168.13.128/25).
- 192.168.16.0/22 is the authenticated UCC clients range
192.168.16.0/23 is the UCC wifi range, currently configured as a /24
- 192.168.18.0/24 is the IPsec VPN client range
- 192.168.19.0/24 is the OpenVPN client range
- 192.168.20.0/22 is the untrusted / unauthenticated UCC range
192.168.20.0/24 is the new Loft range
192.168.21.0/24 is the public wifi range -- reserved for future use
- 192.168.22.0/23 is the IoT range, also currently configured as a /24
- 172.26.42.0/24 is for 'untrusted client machines' and is allocated to us by UWA and routed to us via VLAN 13. There is some history here, but these addresses are not routed outside the Uni. This subnet may be NATted to public IPs for external access.
- Currently unused.
Most of UCC's subnets use DHCP to assign addresses based on MAC address. Further details can be found at Network/Services#DHCP.
Routing and Firewall
UCC has 2405:3C00:5200:100::/58 (which is :100:: to :13f:: inclusive).
(This is unusually small. RFC-6177 recommends that small end sites - such as a home user with devices in the "dozens or less" - should be allocated a /56 range.)
This is advertised by radvd on Murasoi which most machines autoconfigure from, however some machines have statically assigned addresses. There is an IPv6 firewall that matches our IPv4 firewall very closely. IPv6 traffic is free.
Many machine room systems have IPv6 address, which are statically assigned. These are available in DNS using the ipv6.ucc zone (e.g. martello.ipv6.ucc.asn.au), and usually in the main DNS entry. There is no reverse DNS delegation at this stage, so reverse DNS is UCC-only.
Mooneye's DNS record doesn't have an AAAA record, because we are scared of this breaking Things(tm).
IPv6 is routed to 2405:3C00:10:4::1 from Murasoi.
Mail will be received over IPv6 if it is sent to email@example.com (or ipv6.ucc.gu.uwa.edu.au).
- 2405:3C00:10:4::2/64 uplink (equivalent to 192.168.13.2, UWA VLAN 13)
- 2405:3C00:5200:100::/64 machine room (VLAN 2)
- 2405:3C00:5200:101::/64 clubroom (VLAN 3)
- 2405:3C00:5200:102::/64 member VMs (VLAN 4)
- 2405:3C00:5200:103::/64 loft (VLAN 5)
- 2405:3C00:5200:104::/64 wireless (VLAN 6)
- 2405:3C00:5200:105::/64 IoT (VLAN 7)
2405:3C00:5200:106::/64 public wireless (VLAN 8)
- 2405:3C00:5200:120::/120 IPsec VPN
- 2405:3c00:5200:121::/64 OpenVPN
- 2405:3c00:5200:9100::/64 VUCC "Virtual UCC" IP range (note: not technically owned by UCC and hence not routable from the Internet)
UWA runs multicast in sparse PIM mode, and Murasoi runs pimd as noted here. Make sure pimd is only listening once per interface, otherwise things won't work quite right. Multicast traffic is also free.
HTTP goes through mussel or mooneye. HTTPS is served by mussel on secure.ucc.asn.au, however IMAPS, POPS and SMTPS are NATted by Murasoi to go to Motsugo, for the historical reason that UCC could only afford one SSL certificate. Nowadays, UCC uses LetsEncrypt for everything (including secure.ucc.asn.au) and this is no longer necessary.
There are various monitoring packages installed, links to which can be found on MissionControl.