Difference between revisions of "Infrastructure:Network Architecture"
imported>Pew (→Current) |
imported>Pew |
||
Line 30: | Line 30: | ||
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
− |
Revision as of 01:54, 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
Contents
General Information
IPv4
Most Internet-connected computers communicate using Internet Protocol version 4, usually abbreviated IPv4. IPv4 assigns an address to each computer. These addresses are 32 bits long, and can be written as a period-separated list of four numbers from zero to 255. One example would be 192.168.1.1, an address commonly given to home networking equipment. The 32-bit address space of IPv4 allows for about four billion addresses. Given that there are over six billion people on the planet, it's clear that these addresses will eventually run out. It turns out that due to the way these addresses are allocated in blocks, we actually already have run out.
IPv6
Enter IP version 6, or IPv6. IPv6 uses 128 bits for each address, but is not yet very widely used. Virginia Tech, being the cutting edge institution it is, already supports IPv6 campus-wide. While this does not directly affect your computing experience, connecting your computer to a native IPv6 networks has a few implications you should be aware of.
Stateless Autoconfiguration and Privacy Extensions
In IPv4, a computer would need to be told its address either manually or by using a network service called DHCP. In DHCP, the computer asks a server to assign it an IP address that is not in use by anyone else.
In IPv6, the address space is so large that a mechanism called "stateless autoconfiguration" can be used. In stateless autoconfiguration, a computer asks a nearby router for the network prefix (the first few digits of the IP address that will be the same for all computers on the network), and then the computer fills in the rest of the bits by using the hardware address of the network adapter. This means that by default, your IP address could be used to uniquely identify your computer anywhere on the Internet, threatening your privacy online.
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