Network Infrastructure and Services: Difference between revisions
imported>Mutantmonkey Corrected details about IPv6 |
imported>Mutantmonkey No edit summary |
||
| Line 17: | Line 17: | ||
=== Controversies === | === Controversies === | ||
In addition to the network policies stated above, the following controversial activities have arisen: | In addition to the network policies stated above, the following controversial activities have arisen: | ||
* CNS has begun deploying [[w:Network Address Translation | NAT]] to dorm buildings, starting with [[Ambler Johnston Hall]], as it has done in the past with wireless access points | * CNS has begun deploying [[w:Network Address Translation | NAT]] to dorm buildings, starting with [[Ambler Johnston Hall]], as it has done in the past with wireless access points. | ||
* In January 2013, emergency maintenance was done at Virginia Tech's uplink in Ashburn, but users were not informed in advance of the potential downtime. This initially took out VT's edge IPv4 access for several hours, and later resulted in intermittent routing issues at the BGP level until the next morning. | * In January 2013, emergency maintenance was done at Virginia Tech's uplink in Ashburn, but users were not informed in advance of the potential downtime. This initially took out VT's edge IPv4 access for several hours, and later resulted in intermittent routing issues at the BGP level until the next morning. | ||
* Like most administrative university offices, CNS is often regarded as having much bureaucracy. For example, the processes for obtaining SSL certificates or a DNS entry directly under "vt.edu" are especially tedious. | * Like most administrative university offices, CNS is often regarded as having much bureaucracy. For example, the processes for obtaining SSL certificates or a DNS entry directly under "vt.edu" are especially tedious. | ||