|Deletions are marked like this.||Additions are marked like this.|
|Line 17:||Line 17:|
|UCC uses seven VLANs internally for various purposes:||UCC uses six VLANs internally for various purposes:|
|Line 22:||Line 22:|
| * VLAN 6: Wireless network.
* VLAN 7: Printers. (currently largely unused)
|* VLAN 6: Authenticated wireless network.|
|Line 37:||Line 36:|
|* 10.13.13.0/24 is a private range used for network printers, but is not currently used. These addresses reside on VLAN 7 and are not routed outside.|
|Line 43:||Line 41:|
|* 192.168.2.x is the management VLAN IP range. This is not routed outside UCC.|
|Line 79:||Line 78:|
|All HTTP goes through mooneye, and is proxied to various other machines for processing, primarily mussel. HTTPS is served by mussel on secure.ucc.asn.au, however IMAPS, POPS and SMTPS are NATted by madako to go to mooneye, since we're cheap and only have one SSL certificate.||HTTP goes through mussel or mooneye. HTTPS is served by mussel on secure.ucc.asn.au, however IMAPS, POPS and SMTPS are NATted by madako to go to motsugo, since we're cheap and only have one SSL certificate.|
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 long piece of CAT5 running through the walls from the machine room to the Guild machine room in Cameron Hall (across from UWAnime). This plugs in to a 100M D-Link media converter, which leads to a similar media converter in the Guild comms room in the main Guild building. Our uplink is into an ITS managed switch called 'cruzob'. 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.
The machine room contains two switches and a router:
- Madako, a linux-based router running iptables.
- Coconut, a Cisco Catalyst 2948G-GE-TX running CatOS which has 48 GigE ports and 4 SFP slots.
Curviceps, an HP ProCurve 1800-24G which has 24 GigE ports and 2 SFP slots.
These are all labeled and in the rack. There is also a patch panel for the clubroom wall-ports at the top of the rack.
There is CAT5 cabling run from a patch panel at the top 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.
See also: Network/SwitchConfiguration
UCC uses six VLANs internally for various purposes:
- VLAN 1: Network and server management.
- VLAN 2: Machine room network.
- VLAN 3: Clubroom network.
- VLAN 5: Loft network (used for LANs).
- VLAN 6: Authenticated wireless network.
- VLAN 8: Untrusted wireless network.
ITS trunks to us the following VLANs:
- VLAN 11: SNAP.
- VLAN 13: Our main uplink, provides us our internet connection and address space.
- VLAN 102: Guild clubs. Not used by UCC, forwarded on to UniSFA.
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:
- 22.214.171.124/24 is the public address space for our AARNet connection. This range is routed to us via VLAN 13.
- 126.96.36.199/26 is the machine room address range, internally routed on VLAN 2.
- 188.8.131.52/26 is the clubroom address range, internally routed on VLAN 3.
- 172.26.42.0/24 is for 'untrusted client machines' - there is some history here, but they are never routed outside the Uni (unless NAT is involved, which it is).
- 172.26.42.0/26 is for public wireless (unauthenticated clients).
- 172.26.42.96/27 is the range we use for PPTP.
- 172.26.42.128/26 is the loft network range.
- 172.26.42.192/27 is the UCC wireless network range (for authenticated clients).
- 192.168.2.x is the management VLAN IP range. This is not routed outside UCC.
- 10.11.0.0/24 on the SNAP vlan (10.11.0.0/16 in total) is not leased out by the central SNAP dhcp server, so some IPs in this range can be taken for services. Currently 10.11.0.13 is the UCC SNAP SSH forward (which ends up at martello) and .11 is used by evil.
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
Madako, the Linux router, is a beast of burden. See Network/Firewall for further information on the way it operates.
UCC has 2405:3C00:1:4200::/56 (which is :4200:: to :42ff:: inclusive).
This is advertised by radvd on madako which most machines autoconfigure from, however some machines have statically assigned addresses. There is a rudimentary IPv6 firewall. 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:1:13::1 from Madako.
Mail will be received over IPv6 if it is sent to [email protected] (or ipv6.ucc.gu.uwa.edu.au).
- 2405:3C00:1:13::2/64 uplink (equivalent to 192.168.13.2, UWA VLAN 13)
- 2405:3C00:1:4200::/64 machine room (VLAN 2)
- 2405:3C00:1:4201::/64 clubroom (VLAN 3)
- 2405:3C00:1:4203::/64 loft (VLAN 5)
- 2405:3C00:1:4204::/64 wireless (VLAN 6)
- 2405:3C00:1:4206::/64 public wireless (VLAN 8)
- 2405:3C00:1:42A0::/59 PPTP VPN (each link gets a ::/64)
IPv6 link-local addresses are handed out by the PPTP/PPP daemon, and radvd is started for each link to hand out globally-routeable addresses - see here (although the address ranges have changed slightly).
UWA runs multicast in sparse PIM mode, and madako 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 madako to go to motsugo, since we're cheap and only have one SSL certificate.
There is a PPTP server running on madako, though SSH tends to be the most reliable protocol for tunneling about UWA.
There are various monitoring packages installed, links to which can be found on MissionControl.