Differences between revisions 46 and 47
Revision 46 as of 2012-08-01 11:19:17
Size: 6669
Editor: DavidAdam
Revision 47 as of 2012-08-01 23:21:48
Size: 6669
Editor: BobAdamson
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Australiading 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. 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.

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.

Layer One

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). 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.

Machine Room

The machine room contains two switches and a router:

  • Murasoi, a linux-based router running iptables.

  • Bitumen, a Cisco Catalyst 4507R running IOS which has 2 SupIV supervisor engines, 96 GigE ports and 12 GBIC slots.

  • 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 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.

Layer Two

See also: Network/SwitchConfiguration

Internal VLANs

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.

External VLANs

ITS trunks to us the following VLANs:

  • VLAN 13: Our main uplink, provides us our internet connection and address space. This extends to the Faculty of Arts where we have colocated machines.
  • VLAN 102: Guild clubs. Not used by UCC, was forwarded on to UniSFA.

Layer Three

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:

  • is the public address space for our AARNet connection. This range is routed to us via VLAN 13.
    • is the machine room address range, internally routed on VLAN 2.
    • is the clubroom address range, internally routed on VLAN 3.
  • 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.
    • is for public wireless (unauthenticated clients).
    • is the range we use for PPTP.
    • is the loft network range.
    • is the UCC wireless network range (for authenticated clients).
  • 192.168.13.x/24 is the uplink range, routed on VLAN 13 by UWA. Machines colocated in Arts also have addresses on this range.
  • 192.168.2.x is the management VLAN IP range. This is not allocated to us by UWA and not routed outside UCC.

Addressing scheme

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

Murasoi, 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 Murasoi 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 Murasoi.

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, 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 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.

Higher Layers

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, since we're cheap and only have one SSL certificate.

There is a PPTP server running on Murasoi, though SSH tends to be the most reliable protocol for tunneling about UWA.


Information on configuring the core switches can be found at Network/SwitchConfiguration. Information on configuring routing and firewalling can be found at Network/Firewall.


There are various monitoring packages installed, links to which can be found on MissionControl.