From the Linux and Unix Users Group at Virginia Teck Wiki
Jump to: navigation, search

This page documents VTLUUG's infrastructure post-CVL eviction.

Physical Infrastructure

NFS Hosts

  • dirtycow - Primary NFS server, 8x2TB raidz2 array
  • cyberdelia - OFF, 7x1TB raidz2 array, sitting on shelf instead of shelf

VM Hosts

  • meltdown - Primary VM/docker host
  • spectre - Secondary VM/docker host, for example user VMs


All hosts are on our own 1 Gb/s port with joey, a gateway featuring ARP proxying, and full delegation of the 2607:b400:6:cc80/64 prefix.

Virginia Tech has started blocking inbound ports 22 and 3389 and outbound port 25 at the campus border, in a move echarlie is calling Cyber Auschwitz. Contact for firewall exceptions. When deploying new hosts, make ssh listen on both 2222 and 22. Acidburn currently listens on 3128 as well.

Other hosts

  • Wood is sitting in our rack turned off because we don't have a use for it currently. It is in a 4U case capable of fitting several GPUs.
  • sunway and a SuperMicro server were all transferred to WUVT. Older hosts have either been thrown out or given to members.

See VTLUUG:Strategic_plan for things we plan to do in the future.

On the Network Architecture

Further Information: Infrastructure:Networking and Infrastructure:Network

A simple network diagram by pew. Update June 2021: Joey is dead, long live Joey. Shellshock is the new router. Cyberdelia is off.

We currently have some services with public IPv4 address, and all hosts have an internal IPv4 address on the 10.98.x.x/16 subnet and an IPv6 address assigned via SLAAC. In the future, VPN/Iodine should be used.

In theory, services can be provided via a hidden service such as Tor, but that introduces other complications. Alternately, services can require use of the VPN on acidburn, Iodine, or ssh tunnelling, although all of these limit usage to members with a shell account. All of these have the benefit of NAT transversal, however.


Further information: Category:Services

acidburn and the website must be accessible through real services, and it is preferable other hosts are too. This means we must use our public IPv4 & IPv6 Addresses allotted by ECE.

Website details

Current Setup

All vtluug websites are run on nginx on sczi. These sites are currently functional:

  • (redirects to

All of these sites exclusively allow for the use of TLS connections. All services use automatically updated letsencrypt certs.

Main Page

The main VTLUUG page was scraped from the Internet Archive and added created as a github page at, and is reverse-proxied through sczi.


The wiki currently runs fully on MediaWiki hosted on nginx using a modified version of the official mediawiki docker image. You can auth with the admin account, wiki-admin or a Google account. See note on Main_page about why LDAP isn't working yet.


Runs on the same Mediawiki instance as this wiki. Similarly to LUUGWiki, only Google accounts or the admin user are supported logins.

Needs Restoration

These are VTLUUG services that haven't yet been properly restored:

  • - For Wadsworth's .pickfood and .foodvote commands. This is jpo's fault.
  • - mhazinsk's Tahoe-LAFS grid
  • - git hosting; previously a redirect to gitweb with gitosis as the SSH backend
  • - git hosting; previously gitweb
  • - OSM based map of VT


See Dead_projects for historic information


See VTLUUG:Strategic_plan#Web_Services for future goals involving web services


VTLUUG currently has DNS with Message officers for access (please don't be scared :D).

We currently hold the IPv6 prefix 2001:470:8:6d9::/64 from HE's allocation due to our tunnel. When CNS finally sets up prefix-delegation, we might be able to get something from 2607:b400::/32, which is VT's largest allocation.


This page describes specifics about VTLUUG's current network. For an overview, see Infrastructure:Networking


ECE DNS VTLUUG DNS IPv4 Private Internal IPv4 IPv6 2607:b400:6:cc80:0:aff:fe62:b 2607:b400:6:cc80:21e:c9ff:feef:13f8 2607:b400:6:cc80:0:aff:fe62:c 2607:b400:6:cc80:0:aff:fe62:3 2607:b400:6:cc80:0:aff:fe62:a 2607:b400:0006:cc80:0230:48ff:fe7e:28da 2001:468:c80:6103:211:43ff:fe30:a72 N/A *Not sure if we can actually use this IP* N/A N/A
N/A (Internal v4 only) N/A N/A
N/A N/A 2607:b400:6:cc80:0:aff:fe62:4
N/A N/A 2607:b400:0006:cc80:0215:17ff:fe12:7670
N/A N/A 2607:b400:6:cc80:215:17ff:fe12:7670

See Deprecated_Network for historical information.



  • SLAAC on 2607:b400:0006:cc80::/64
  • internal NAT
    • Static IPs:
    • DHCP: -
    • Iodine:
  • publicly accessible hosts

All hosts have an internal address (static or DHCP) and some hosts also have a globally accessible address.


joey also functions as DNS server for internal hosts

  • 2607:b400:0006:cc80::1


CNS maintains a few DNS servers on campus

  •, 2001:468:c80:2101:0:100:0:22,
  •, 2001:468:c80:4101:0:100:0:42,
  •, 2001:468:c80:6101:0:100:0:62,

See Also