Infrastructure:Network Architecture
TODO: change name to "Network Architecture" and change content to more generally describe how the univerersity network works, with specifics about VTLUUG's setup. Direct to Infrastructure:Network with talkinga about specific IPs and mention that link a lot throughout the page when we fix the wiki so this isn't confused Infrastructure:Network and move Historic section to and leave a link here
This is an attempt to document VTLUUG's overly complex networking setup. Apologies for the disorganization, this is mainly just a way to get everything in one place. --Mjh (talk) 21:43, 28 December 2014 (EST
Note: This is extraordinarily dated. Revisions are in progress, but currently, do not consider it to be remotely correct. --echarlie
Current
We currently have a ~1Gbit NI&S port in the ECE server attic
Hardware:
- "luug5" or "temp88191": a Poweredge 2650 with 2 NICs configured as an Ubuntu 14.04 router
- cyberdelia
Cyb has a private network for NFS on 10.99.0.0/24, and temp88191 does NDP proxying, static ARP using jkh's Nat script (see github), and hands out dhcp leases somewhere in 10.0.0.0/8
We have no other hardware in use
DNS
See also: Infrastructure:Network#DNS
www. Required for Subdomains
Requiring www. in front of many subdomains is a known but ignored issue. Apparently, nobody at CNS has bothered to fix it. Rumor has it that the utility of their 25-year-old maintenance scripts is to blame for this issue and other DNS complications like difficulty maintaining MX records. Resolving this issue must be done individually at each department by addressing the problem to the relevant network liasion.
See Deprecated Network for historic information
