Difference between revisions of "Infrastructure:Network Architecture"
imported>Pew (→Historic) |
imported>Pew (→DNS) |
||
| Line 18: | Line 18: | ||
We have no other hardware in use | We have no other hardware in use | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | [ | + | See [[Infrastructure:Network#DNS]] for DNS information |
| + | |||
See [[Deprecated Network]] for historic information | See [[Deprecated Network]] for historic information | ||
Revision as of 01:48, 4 January 2018
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
See Infrastructure:Network#DNS for DNS information
See Deprecated Network for historic information
