VLAN and IP address-space information (Do Not Migrate)
This page documents established network assignments (that is manually maintained). For the
definitive list of VLans in use (that includes projects under developement) refer to this
CSCF Vlan Information
or
IST's
nsbuild application.
For a discussion about general policies and our general network architecture, see the
network schema discussion.
Additional references
Router configurations
All of our vlans are routed one of five HP routers, as shown in the "Location" column of the reference tables below. The ONA links to their configurations are:
If two location labels appear (eg: mc-dc) that indicates an inter-building trunk (typically a /30 point-to-point network).
"Network name" column in the following tables
The network name column is intended to show the router name of the network, not the DNS name. The DNS name for the network is, by convention, assigned to the ".0" address (the address of the network) and can be determined from a standard DNS lookup.
Please be sure to use the correct name in the column. Router network names can be determined from the ONA vlan summary for the router on which the network is routed (see the bullet list above).
Current VLAN assignments
VLAN 438 is IST wired authentication or 802.1x (building independent)
Date: Thu, 14 Feb 2013 13:54:30 -0500
To: <noc@ist.uwaterloo.ca>, <ist-mgmt@lists.uwaterloo.ca>,
<ctsc@lists.uwaterloo.ca>, <cnsc@lists.uwaterloo.ca>, <watcard@uwaterloo.ca>,
<ist-css@lists.uwaterloo.ca>, <ist-itms@lists.uwaterloo.ca>,
<acohelp@watarts.uwaterloo.ca>, <admin-support@lists.uwaterloo.ca>,
<tg-networks@cscf.cs.uwaterloo.ca>, <kevin.kennedy@family-medicine.ca>,
<esag@engmail.uwaterloo.ca>, <cmseitz@uwaterloo.ca>,
<admin@pdeng.uwaterloo.ca>, <faccus@lists.uwaterloo.ca>,
<isthd@ist.uwaterloo.ca>, <acoccia@uwaterloo.ca>, <sbradley@uwaterloo.ca>,
<wcarroll@uwaterloo.ca>, <tkanerva@uwaterloo.ca>,
<uw.network@rumours.uwaterloo.ca>, <reshelp@uwaterloo.ca>,
<cskingle@uwaterloo.ca>, <rddigby@uwaterloo.ca>, <arbhagat@uwaterloo.ca>,
<kjjack@uwaterloo.ca>
Subject: NETWORK ALERT - 2013-02-19 - Activation of 802.1x in MC
From: <daldwinc@uwaterloo.ca>
Description: Activation of 802.1x in MC
Date: (YYYY-MM-DD) 2013-02-19
Start Time: 7 AM
End Time: 8 AM
Impact:
Resolution:
Submitted By: daldwinc@uwaterloo.ca
Comment: On the morning of February 19th, a number of network ports in MC will have 802.1X authentication turned on.
Ports in public locations may require users to authenticate before the port becomes fully active.
Dave Aldwinckle
IST Network Services
Notice Submitted: Thu Feb 14 13:54:30 EST 2013
Note: If you have any questions or concerns please contact the IST Help Desk at ext: 84357 or helpdesk@uwaterloo.ca
Subject: [UW-RT #273071] FW: NETWORK ALERT - 2013-02-19 - Activation of 802.1x in MC
From: David Aldwinckle via RT <rt@rt.uwaterloo.ca>
To: <isthelpd@uwaterloo.ca>
CC: <trevor.grove@uwaterloo.ca>
Date: Fri, 15 Feb 2013 11:26:58 -0500
The ports in question are all on either MATH or AS switches. There will be no changes to CS devices at this time.
> 1) which ports are affected?
Those that have historically had authentication enabled (the old aruba captive portal page), and are now sitting on VLAN 438 with no authentication enabled.
> 2) how will users know if they are supposed to authenticate?
Users will DHCP a private address and all of their web traffic will be redirected to a web page that explains that they are using a port that requires authentication.
> 3) how will they authenticate (if necessary)?
The page mentioned above will have instructions on how to configure 802.1x for Windows 7 and Ubuntu 12.04. OS X clearly prompts the user for authentication.
The most important things to note are:
Authentication Type: PEAP
Inner authentication: MSCHAPv2
Certificate: GlobalSign Root CA (built-in to Windows, Ubuntu, OS X)
UserID: MUST have the @uwaterloo.ca suffix.
Specific user issues can be handled through RT.
Please let me know if you have any additional questions.
Dave
VLAN 439 in the future will be wired authentication or 802.1x (building independent)
Research external network
VLANs in 129.97.0.0/16
129.97.152.0/24 Notes
- On IST RT#350945 and CS ST#94616 129.97.152.0/24 was split into small networks as follows (to allow for CS networks in other buildings)
- 129.97.152.0/25 into /28 (16 IPs) blocks
- 129.97.152.128/25 into /29 (8 IPs) blocks
VLANs in 192.168.0.0/16
VLANs in 172.19.0.0/16
172.19.20.0/24 Notes
- On IST RT#350945 and CS ST#94616 172.19.20.0/24 was created to support CS management and ILOM access in MC
VLANs in 10.0.0.0/8
IST networks of interest
These are of interest, not as vlan information but for the address-range information, for use in setting up local firewalls or access restrictions.
Campus IPv4 network address ranges
IPv4 range |
Description |
NATted range |
172.16.36.0/22 |
campus VPN address range |
n/a |
10.20.0.0/14 |
campus wireless, divided into: |
10.22.0.0/15 |
main campus, divided into: |
10.20.0.0/16 |
Eduroam |
129.97.124.0/23 |
10.21.0.0/16 |
uw-guest/uw-unsecured |
129.97.124.0/23 |
10.22.0.0/15 |
ResNet, divided into: |
10.22.0.0/16 |
Eduroam |
129.97.124.0/23 |
10.23.0.0/16 |
uw-guest/uw-unsecured |
129.97.124.0/23 |
172.31.192.0/18 |
ResNet wired (ie dorm rooms) address range |
129.97.131.0/24 |
And for those of you keen on IPv6:
Campus IPv6 network address ranges
IPv6 range |
Description |
2620:101:f000:700::/62 |
campus wireless, divided into: |
2620:101:f000:700::/63 |
main campus, divided into: |
2620:101:f000:700::/64 |
Eduroam |
2620:101:f000:701::/64 |
uw-guest/uw-unsecured |
2620:101:f000:702::/63 |
ResNet, divided into: |
2620:101:f000:702::/64 |
Eduroam |
2620:101:f000:703::/64 |
uw-guest/uw-unsecured |
2620:101:f000:3000::/54 |
ResNet wired (ie dorm rooms) address range |
All IPv6 addresses are public, so no NATting is required.