https://vtluug.org/w/api.php?action=feedcontributions&feedformat=atom&user=RskLinux and Unix Users Group at Virginia Teck Wiki - User contributions [en]2026-04-22T18:47:58ZUser contributionsMediaWiki 1.31.1https://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8275Infrastructure:Bastille2026-03-08T01:59:05Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs (Both connected), and one Intel X520 2x10G SFP+ (Unused)<br />
* notably, no peripheral ports other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from [[Infrastructure:Vesuvius]] as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)<br />
* tor relay (rsk)<br />
** both of the above possibly better as a slim nixos VM on something like spectre?<br />
* nix build server (clj)<br />
* build/parameter optimization rust compiler (clj)<br />
* folding@home (ap, eri)<br />
* port sczi over (mkl)<br />
** slskd/slskd:latest<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** <s>luuul/4get:latest</s> ported<br />
** linuxserver/qbittorrent:latest<br />
** qmcgaw/gluetun<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** mariadb:10.4.32<br />
** vtluug/mediawiki-vtluug:1.1<br />
** linuxserver/swag<br />
** vectorim/element-web:latest<br />
** quay.io/dexidp/dex:latest<br />
** <s>vtluug/pyqdb</s> ported<br />
** thelounge/thelounge:latest<br />
** vtluug-site-vtluug-site<br />
** vaultwarden/server:latest<br />
** gitea/gitea:nightly<br />
** t4skforce/syncthing-relay-discovery:latest<br />
* Tigerbeetle (clj, meme suggestion)<br />
* Something like Sagemath but in a way that doesn't give people free ACE (clj)<br />
* map stuff (mhazinsk)<br />
** OSM tile server<br />
** async LIDAR processing - laz2ept/[https://caves.science/ sinkholes], etc<br />
* [https://github.com/coder/coder coder] ephemeral dev environments for members (mhazinsk)<br />
* [https://aleph.occrp.org/ OCCRP Aleph] for VT FOIA requests as a hokieprivacy project (mhazinsk)<br />
* [https://ooni.org/install/cli OONI probe] (mhazinsk)<br />
* browsertrix (pew)<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Naming_schemes&diff=8268Naming schemes2026-02-15T02:47:43Z<p>Rsk: un-rot tumblrgenders link</p>
<hr />
<div>'''Naming schemes''' are used when dealing with a number of objects which need memorable names, e.g. servers. Choosing names that are all related helps ensure the names are not difficult to remember. The process of picking a naming scheme can be a slow and difficult process often delaying work, so below is a list of naming schemes to help make that process easier. Most of these were collected from [[Pound vtluug|#vtluug]] but others may have been added later.<br />
<br />
# People at work<br />
# Pokemon<br />
# LOTR<br />
# Norse gods<br />
# Latin words<br />
# Phonetic alphabet<br />
# Circuit components<br />
# Types of shoes<br />
# Radio scientists<br />
# Dumb hashtags (yolo, swag, nsfw)<br />
# Failed memes<br />
# VT football players<br />
# Small disease carrying rodents<br />
# Flavours of milk<br />
# Nicholas cage filmography<br />
# Things that look bad without spaces (pen island)<br />
# Racial slurs<br />
# Cheeses<br />
# Post it note knock off brand names<br />
# Jellies<br />
# Knock off cereals<br />
# Types of pasta<br />
# Body parts<br />
# Knock off brands of shoes<br />
# Knock off brands of gaming systems<br />
# Letters<br />
# Local radio stations<br />
# Mexican radio stations<br />
# Non-corresponding [[Linux]] distros<br />
# Shitty Christmas presents<br />
# [[User:Wallmani|wallmani]]'s alternate handles <br />
# Lesser known holidays<br />
# Pagan holidays<br />
# NSFW subreddits<br />
# Mental diseases<br />
# Popes<br />
# Soviet leaders<br />
# Religions<br />
# Pony names<br />
# Profanity in foreign languages<br />
# x86 mnemonic opcodes<br />
# "whore" in different languages<br />
# Alternate names for brothel<br />
# Innocuous words that are also stripper names (destiny, candy, unique)<br />
# Words that are euphemisms for child pornography<br />
# Slang for erections<br />
# Condom brands<br />
# Sexual innuendos<br />
# Owners of the rings of power<br />
# Penn state rape puns<br />
# Popular song titles<br />
# Different *sexuals (homosexual, heterosexual, metrosexual)<br />
# Different fetishes<br />
# Types of naming schemes (colours, norsegods)<br />
# Song lyrics<br />
# Bike manufacturers<br />
# Names of weird subcultures<br />
# Different types of video files<br />
# Text editors<br />
# Sith lords<br />
# Fandoms<br />
# Common vim key sequences<br />
# Dragon shouts<br />
# Marijuana strains<br />
# Drugs<br />
# Nucleotide bases<br />
# Take the IP address in quad dot notation and convert every number to the corresponding letter of the alphabet, and replace . with -<br />
# Every machine = 'lo' * last number in IP address<br />
# Chopstick manufacturers<br />
# Bender's catchphrases<br />
# Starship captains<br />
# Last octet of the IP address<br />
# Goa'ulds<br />
# Classes at VT<br />
# Linux kernel maintainers<br />
# Cthulu mythos<br />
# YouTube ids of Rickroll videos<br />
# The nth unique word from a Claude Shannon paper<br />
# Ant pheromones<br />
# Hashes of the 100 most used passwords<br />
# Last names of graduates from a VT department for a certain year<br />
# Names of people listed as graduates from VT on Wikipedia<br />
# Famous comedians<br />
# Different words to describe a bit that is 1 (up, high, on)<br />
# Pixar movies<br />
# Members of VTLUUG<br />
# Buzzwords<br />
# Dr. Who companions<br />
# Cryptography ciphers<br />
# Vulcans<br />
# Comic book fighting sounds<br />
# VT presidents<br />
# VT hall names<br />
# Dubstep sounds<br />
# Names of teen magazines<br />
# Names of tabloids<br />
# Publicly unrouteable IP addresses<br />
# Windows codenames<br />
# Variations on cool story bro<br />
# Windows security vulnerabilities<br />
# Virus names<br />
# US government-sponsored viruses<br />
# Ways to say dying<br />
# Euphemisms for genitalia<br />
# Ways to say pwnd<br />
# Roman battles<br />
# Massacres throughout history<br />
# Nuclear weapons testing codenames<br />
# Failed Russian space missions<br />
# Names of engineering disasters<br />
# Names of people allegedly abducted by aliens<br />
# Castles in Europe<br />
# Names of failing infrastructure in the US<br />
# Assassinated political leaders<br />
# Mob bosses<br />
# James bond love affairs<br />
# Common measurements of alcohol<br />
# Pigs<br />
# Elevator manufacturers (Otis, Dover, ThyssenKrupp, Montgomery, Kone, Southern, Schindler, Westinghouse, Mitsubishi, etc)<br />
# Shark species<br />
# Dinosaur species<br />
# Dictators<br />
# North Korean leaders, military technology, etc<br />
# Evil computers/networks (e.g. WOPR, GlaDOS, Skynet)<br />
# Soviet spacecraft<br />
# Elements<br />
# Planets<br />
# Types of alcohol<br />
# Famous chefs<br />
# Futurama characters<br />
# [[User:andreim|aam]] puns (e.g. aamazing, aamberalert)<br />
# Eastern block secret police agencies (e.g. KGB, Stasi, Securitate, etc.)<br />
# [https://web.archive.org/web/20180406094045/http://ageofshitlords.com/list-of-all-tumblr-genders-so-far/ Genders invented by tumblr]<br />
# Failed US presidential candidates<br />
# Herbs / spices<br />
# Fruits<br />
# US political scandals (watergate, teapotdome, benghazi, trump, ...)<br />
# Farm machinery (tractor, combine, baler, plow, ...)<br />
# Cults (telnoratti has some examples)<br />
# Ousted Trump administration members (bannon, spicer, comey, omarosa, flynn, priebus, price, scaramucci, ...)<br />
# People indicted by Robert Mueller<br />
# Icelandic volcanoes<br />
# Root vegetables<br />
# Obsolete electronics (vcr, teletype, telegraph, answering machine, fax, rotary dial, terminal, dotmatrix, floppy)<br />
# Characters from hacker movies<br />
# Gemstones<br />
# The nonsensical multi-word street names from drab suburban developments in your home town (lindenshade, rustlingoak, sunsetknoll, songsparrow, etc)<br />
# Feeder creeks of the New River (toms, stroubles, slatebranch, peak)<br />
# VTLUUG member callsigns<br />
# COVID variants<br />
# Nonoffensive fictional serial killers (williamafton, sweeneytodd, jasonvoorhees, ...)<br />
# Definitely offensive real serial killers (dylanklebold, ericharris, pattycannon, adamlanza, brentontarrant, ...)<br />
# Blacksburg drinking establishments (cellar, tots, sharkeys, hohouse, burg, milkparlor, macados)<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Needs restoration]]</div>Rskhttps://vtluug.org/w/index.php?title=Naming_schemes&diff=8267Naming schemes2026-02-15T02:36:28Z<p>Rsk: </p>
<hr />
<div>'''Naming schemes''' are used when dealing with a number of objects which need memorable names, e.g. servers. Choosing names that are all related helps ensure the names are not difficult to remember. The process of picking a naming scheme can be a slow and difficult process often delaying work, so below is a list of naming schemes to help make that process easier. Most of these were collected from [[Pound vtluug|#vtluug]] but others may have been added later.<br />
<br />
# People at work<br />
# Pokemon<br />
# LOTR<br />
# Norse gods<br />
# Latin words<br />
# Phonetic alphabet<br />
# Circuit components<br />
# Types of shoes<br />
# Radio scientists<br />
# Dumb hashtags (yolo, swag, nsfw)<br />
# Failed memes<br />
# VT football players<br />
# Small disease carrying rodents<br />
# Flavours of milk<br />
# Nicholas cage filmography<br />
# Things that look bad without spaces (pen island)<br />
# Racial slurs<br />
# Cheeses<br />
# Post it note knock off brand names<br />
# Jellies<br />
# Knock off cereals<br />
# Types of pasta<br />
# Body parts<br />
# Knock off brands of shoes<br />
# Knock off brands of gaming systems<br />
# Letters<br />
# Local radio stations<br />
# Mexican radio stations<br />
# Non-corresponding [[Linux]] distros<br />
# Shitty Christmas presents<br />
# [[User:Wallmani|wallmani]]'s alternate handles <br />
# Lesser known holidays<br />
# Pagan holidays<br />
# NSFW subreddits<br />
# Mental diseases<br />
# Popes<br />
# Soviet leaders<br />
# Religions<br />
# Pony names<br />
# Profanity in foreign languages<br />
# x86 mnemonic opcodes<br />
# "whore" in different languages<br />
# Alternate names for brothel<br />
# Innocuous words that are also stripper names (destiny, candy, unique)<br />
# Words that are euphemisms for child pornography<br />
# Slang for erections<br />
# Condom brands<br />
# Sexual innuendos<br />
# Owners of the rings of power<br />
# Penn state rape puns<br />
# Popular song titles<br />
# Different *sexuals (homosexual, heterosexual, metrosexual)<br />
# Different fetishes<br />
# Types of naming schemes (colours, norsegods)<br />
# Song lyrics<br />
# Bike manufacturers<br />
# Names of weird subcultures<br />
# Different types of video files<br />
# Text editors<br />
# Sith lords<br />
# Fandoms<br />
# Common vim key sequences<br />
# Dragon shouts<br />
# Marijuana strains<br />
# Drugs<br />
# Nucleotide bases<br />
# Take the IP address in quad dot notation and convert every number to the corresponding letter of the alphabet, and replace . with -<br />
# Every machine = 'lo' * last number in IP address<br />
# Chopstick manufacturers<br />
# Bender's catchphrases<br />
# Starship captains<br />
# Last octet of the IP address<br />
# Goa'ulds<br />
# Classes at VT<br />
# Linux kernel maintainers<br />
# Cthulu mythos<br />
# YouTube ids of Rickroll videos<br />
# The nth unique word from a Claude Shannon paper<br />
# Ant pheromones<br />
# Hashes of the 100 most used passwords<br />
# Last names of graduates from a VT department for a certain year<br />
# Names of people listed as graduates from VT on Wikipedia<br />
# Famous comedians<br />
# Different words to describe a bit that is 1 (up, high, on)<br />
# Pixar movies<br />
# Members of VTLUUG<br />
# Buzzwords<br />
# Dr. Who companions<br />
# Cryptography ciphers<br />
# Vulcans<br />
# Comic book fighting sounds<br />
# VT presidents<br />
# VT hall names<br />
# Dubstep sounds<br />
# Names of teen magazines<br />
# Names of tabloids<br />
# Publicly unrouteable IP addresses<br />
# Windows codenames<br />
# Variations on cool story bro<br />
# Windows security vulnerabilities<br />
# Virus names<br />
# US government-sponsored viruses<br />
# Ways to say dying<br />
# Euphemisms for genitalia<br />
# Ways to say pwnd<br />
# Roman battles<br />
# Massacres throughout history<br />
# Nuclear weapons testing codenames<br />
# Failed Russian space missions<br />
# Names of engineering disasters<br />
# Names of people allegedly abducted by aliens<br />
# Castles in Europe<br />
# Names of failing infrastructure in the US<br />
# Assassinated political leaders<br />
# Mob bosses<br />
# James bond love affairs<br />
# Common measurements of alcohol<br />
# Pigs<br />
# Elevator manufacturers (Otis, Dover, ThyssenKrupp, Montgomery, Kone, Southern, Schindler, Westinghouse, Mitsubishi, etc)<br />
# Shark species<br />
# Dinosaur species<br />
# Dictators<br />
# North Korean leaders, military technology, etc<br />
# Evil computers/networks (e.g. WOPR, GlaDOS, Skynet)<br />
# Soviet spacecraft<br />
# Elements<br />
# Planets<br />
# Types of alcohol<br />
# Famous chefs<br />
# Futurama characters<br />
# [[User:andreim|aam]] puns (e.g. aamazing, aamberalert)<br />
# Eastern block secret police agencies (e.g. KGB, Stasi, Securitate, etc.)<br />
# [http://ageofshitlords.com/list-of-all-tumblr-genders-so-far/ Genders invented by tumblr]<br />
# Failed US presidential candidates<br />
# Herbs / spices<br />
# Fruits<br />
# US political scandals (watergate, teapotdome, benghazi, trump, ...)<br />
# Farm machinery (tractor, combine, baler, plow, ...)<br />
# Cults (telnoratti has some examples)<br />
# Ousted Trump administration members (bannon, spicer, comey, omarosa, flynn, priebus, price, scaramucci, ...)<br />
# People indicted by Robert Mueller<br />
# Icelandic volcanoes<br />
# Root vegetables<br />
# Obsolete electronics (vcr, teletype, telegraph, answering machine, fax, rotary dial, terminal, dotmatrix, floppy)<br />
# Characters from hacker movies<br />
# Gemstones<br />
# The nonsensical multi-word street names from drab suburban developments in your home town (lindenshade, rustlingoak, sunsetknoll, songsparrow, etc)<br />
# Feeder creeks of the New River (toms, stroubles, slatebranch, peak)<br />
# VTLUUG member callsigns<br />
# COVID variants<br />
# Nonoffensive fictional serial killers (williamafton, sweeneytodd, jasonvoorhees, ...)<br />
# Definitely offensive real serial killers (dylanklebold, ericharris, pattycannon, adamlanza, brentontarrant, ...)<br />
# Blacksburg drinking establishments (cellar, tots, sharkeys, hohouse, burg, milkparlor, macados)<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Needs restoration]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Prospit&diff=8255Infrastructure:Prospit2026-01-17T06:12:18Z<p>Rsk: Created page with "Prospit<ref>https://homestuck.com/images/hspanels/actThree/01032.gif</ref> is a Dell Precision 5810(?) tower, donated by nate and named by clj. It..."</p>
<hr />
<div>Prospit<ref>https://homestuck.com/images/hspanels/actThree/01032.gif</ref> is a Dell Precision 5810(?) tower, donated by [[User:Nate|nate]] and named by [[User:Clj|clj]]. <br />
<br />
It is not doing anything, at the moment, and is configured to be disklessly netbooted as part of [[Infrastructure:Vesuvius|the cluster]].<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure&diff=8254Infrastructure2026-01-17T05:56:25Z<p>Rsk: </p>
<hr />
<div>This page documents VTLUUG's infrastructure post-[[CVL eviction]].<br />
<br />
== Physical Infrastructure ==<br />
=== NFS Hosts ===<br />
* [[Infrastructure:Dirtycow|dirtycow]] - Primary NFS server, 8x2TB raidz2 array<br />
<br />
=== VM Hosts ===<br />
* [[Infrastructure:Meltdown|meltdown]] - Primary VM/docker host<br />
* [[Infrastructure:Spectre|spectre]] - Secondary VM/docker host, for example user VMs<br />
* [[Infrastructure:Gibson|gibson]] - Secondary VM/docker host, Intel Arc A770, for GPU loads<br />
* [[Infrastructure:Prospit|prospit]] - Secondary VM/docker host, GTX 1080, for GPU loads<br />
=== Whit Cluster ===<br />
* [[Infrastructure:Vesuvius|vesuvius]] - SAN/control plane, 8x12TB raidz2 array<br />
* [[Infrastructure:Bastille|bastille (blades)]] - worker nodes<br />
<br />
=== Routers ===<br />
* [[Infrastructure:Shellshock|shellshock]] - Whit router, 3 disk RAID1 array<br />
* [[Infrastructure:Zerocool|zerocool]] - McBryde router<br />
<br />
All hosts are on our own 1 Gb/s port with [[Infrastructure:Shellshock|shellshock]], a gateway featuring ARP proxying, and full delegation of the 2607:b400:6:cc80/64 prefix.<br />
<br />
Virginia Tech has started blocking inbound ports 22 and 3389 and outbound port 25 at the campus border, in a move<br />
[[User:echarlie|echarlie]] is calling [[gp:Cyber Auschwitz|Cyber Auschwitz]]. Contact itso-g@vt.edu for firewall exceptions.<br />
When deploying new hosts, make ssh listen on both 2222 and 22. [[Infrastructure:Acidburn|Acidburn]] currently listens on 3128 as well.<br />
<br />
=== Other hosts ===<br />
* [[Infrastructure:Joey|joey]] used to be the router, but is no longer in use due to a failure of the single drive<br />
* [[Infrastructure:Wood|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.<br />
* [[Infrastructure:Cyberdelia|cyberdelia]] - OFF, 7x1TB raidz2 array, sitting on shelf instead of rack<br />
* [[Infrastructure:Sunway|sunway]] and a SuperMicro server were all transferred to WUVT. Older hosts have either been thrown out or given to members.<br />
<br />
See [[VTLUUG:Strategic_plan]] for things we plan to do in the future.<br />
<br />
== On the Network Architecture ==<br />
''Further Information: [[Infrastructure:Networking]] and [[Infrastructure:Network]]''<br />
<br />
[[File:Infra2019-network.png|thumb|500px|A simple network diagram by [[user:pew|pew]]. '''Update June 2021: Joey is dead, long live Joey. Shellshock is the new router. Cyberdelia is off.]]<br />
<br />
<br />
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.<br />
In the future, [[Infrastructure:IPsec|VPN]]/[[Iodine]] should be used.<br />
<br />
In theory, services can be provided via a hidden service such as [[w:Tor|Tor]], but that introduces other complications.<br />
Alternately, services can require use of the [[Infrastructure:IPsec|VPN]] on [[Infrastructure:Acidburn|acidburn]],<br />
[[Iodine]], or [[Secure Shell|ssh tunnelling]], although all of these limit usage to members with a shell account.<br />
All of these have the benefit of NAT transversal, however.<br />
<br />
== Services ==<br />
''Further information: [[:Category:Services]]''<br />
<br />
* [[Infrastructure:Acidburn|acidburn]]<br />
** Shell server<br />
** [[Email]]<br />
** [[Wadsworth]]<br />
** [[Iodine]]<br />
* [[Infrastructure:Chimera|chimera]]<br />
** FreeIPA<br />
* [[Infrastructure:Sczi|Sczi]]<br />
** Website<br />
*** [https://hokieprivacy.org hokieprivacy]<br />
*** [https://bash.vtluug.org vtbash]<br />
*** [https://vtluug.org Main Site]<br />
*** This wiki and [[gp:Main Page|Gobblerpedia]]<br />
*** dex, for authing with the wikis<br />
*** https://vtluug.org/users/~$user - User homepages<br />
*** [https://search.vtluug.org 4get] a metasearch engine<br />
*** [https://git.vtluug.org Gitea] a Github-esque git server with dex/LUUG OpenID auth<br />
*** [https://element.vtluug.org element], a Matrix client<br />
*** [https://soulseek.vtluug.org slskd]<br />
*** [https://seed.vtluug.org qbittorrent-nox]<br />
*** [https://bitwarden.vtluug.org bitwarden]<br />
* [[Infrastructure:Nikonwormhole|nikonwormhole]]<br />
** AdGuard DNS blackhole<br />
* [[Infrastructure:Dirtycow|dirtycow]]<br />
** Storage for all primary services<br />
** NFS - ZFS pool name is cistern<br />
* [[Infrastructure:Meltdown|meltdown]]<br />
** VM host for above services<br />
* [[Infrastructure:Scaryterry|scaryterry]]<br />
** [https://awm.vtluug.org AWM site]<br />
<br />
[[Infrastructure:Acidburn|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.<br />
<br />
== Website details ==<br />
=== Current Setup ===<br />
All vtluug websites are run on nginx on [[Infrastructure:Sczi|sczi]]. These sites are currently functional:<br />
* gobblerpedia.org<br />
* hokieprivacy.org<br />
* vtluug.org<br />
* wiki.vtluug.org (redirects to vtluug.org/wiki/)<br />
* bash.vtluug.org<br />
* vtluug.org/users/~$user<br />
<br />
All of these sites exclusively allow for the use of TLS connections. All services use automatically updated<br />
letsencrypt certs.<br />
<br />
==== Main Page ====<br />
The main VTLUUG page was scraped from the [[w:Internet Archive|Internet Archive]] and added created as a github page at<br />
[https://vtluug.github.io vtluug.github.io], and is reverse-proxied through [[Infrastructure:Sczi|sczi]].<br />
<br />
==== Wiki ====<br />
The wiki currently runs fully on MediaWiki hosted on nginx using a [https://github.com/vtluug/mediawiki-docker modified version of the official mediawiki docker image]. You can auth with the admin account, [[User:wiki-admin|wiki-admin]] or a Google account. See note on [[Main_page]] about why LDAP isn't working yet.<br />
<br />
===== Gobblerpedia =====<br />
Runs on the same Mediawiki instance as this wiki. Similarly to LUUGWiki, only Google accounts or the admin user are supported logins.<br />
<br />
=== Needs Restoration ===<br />
These are VTLUUG services that haven't yet been properly restored:<br />
* [https://github.com/mutantmonkey/foodforus foodfor.vtluug.org] - For [[Wadsworth]]'s .pickfood and .foodvote commands. This is [[User:Timelord|jpo's]] fault.<br />
* tahoe.vtluug.org - [[user:mjh|mhazinsk's]] Tahoe-LAFS grid<br />
* git.vtluug.org - git hosting; previously a redirect to gitweb with gitosis as the SSH backend<br />
* gitweb.vtluug.org - git hosting; previously gitweb<br />
* [https://github.com/vtluug/campusmap map.vtluug.org] - [[Openstreetmap|OSM]] based map of VT<br />
<br />
=== Historically ===<br />
<br />
See [[Dead_projects]] for historic information<br />
<br />
=== Goals ===<br />
See [[VTLUUG:Strategic_plan#Web_Services]] for future goals involving web services<br />
<br />
== Addressing ==<br />
VTLUUG currently has DNS with gandi.net. Message officers for access (please don't be scared :D).<br />
<br />
We currently hold the IPv6 prefix <code>2001:470:8:6d9::/64</code> from HE's allocation due to our tunnel.<br />
When CNS finally sets up prefix-delegation, we might be able to get something from <code>2607:b400::/32</code>,<br />
which is VT's largest allocation.<br />
<br />
{{:Infrastructure:Network}}<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:VTLUUG:Projects]]<br />
[[Category:Featured content]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure&diff=8253Infrastructure2026-01-17T05:53:34Z<p>Rsk: </p>
<hr />
<div>This page documents VTLUUG's infrastructure post-[[CVL eviction]].<br />
<br />
== Physical Infrastructure ==<br />
=== NFS Hosts ===<br />
* [[Infrastructure:Dirtycow|dirtycow]] - Primary NFS server, 8x2TB raidz2 array<br />
* [[Infrastructure:Cyberdelia|cyberdelia]] - OFF, 7x1TB raidz2 array, sitting on shelf instead of rack<br />
<br />
=== VM Hosts ===<br />
* [[Infrastructure:Meltdown|meltdown]] - Primary VM/docker host<br />
* [[Infrastructure:Spectre|spectre]] - Secondary VM/docker host, for example user VMs<br />
<br />
=== Whit Cluster ===<br />
* [[Infrastructure:Vesuvius|vesuvius]] - SAN/control plane<br />
* [[Infrastructure:Bastille|bastille (blades)]] - worker nodes<br />
<br />
=== Router ===<br />
* [[Infrastructure:Shellshock|shellshock]] - 3 disk RAID1 array<br />
<br />
All hosts are on our own 1 Gb/s port with [[Infrastructure:Shellshock|shellshock]], a gateway featuring ARP proxying, and full delegation of the 2607:b400:6:cc80/64 prefix.<br />
<br />
Virginia Tech has started blocking inbound ports 22 and 3389 and outbound port 25 at the campus border, in a move<br />
[[User:echarlie|echarlie]] is calling [[gp:Cyber Auschwitz|Cyber Auschwitz]]. Contact itso-g@vt.edu for firewall exceptions.<br />
When deploying new hosts, make ssh listen on both 2222 and 22. [[Infrastructure:Acidburn|Acidburn]] currently listens on 3128 as well.<br />
<br />
=== Other hosts ===<br />
* [[Infrastructure:Joey|joey]] used to be the router, but is no longer in use due to a failure of the single drive<br />
* [[Infrastructure:Wood|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.<br />
* [[Infrastructure:Sunway|sunway]] and a SuperMicro server were all transferred to WUVT. Older hosts have either been thrown out or given to members.<br />
* A mystery Proliant dl380 g7. Unnamed and unused at the moment.<br />
<br />
See [[VTLUUG:Strategic_plan]] for things we plan to do in the future.<br />
<br />
== On the Network Architecture ==<br />
''Further Information: [[Infrastructure:Networking]] and [[Infrastructure:Network]]''<br />
<br />
[[File:Infra2019-network.png|thumb|500px|A simple network diagram by [[user:pew|pew]]. '''Update June 2021: Joey is dead, long live Joey. Shellshock is the new router. Cyberdelia is off.]]<br />
<br />
<br />
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.<br />
In the future, [[Infrastructure:IPsec|VPN]]/[[Iodine]] should be used.<br />
<br />
In theory, services can be provided via a hidden service such as [[w:Tor|Tor]], but that introduces other complications.<br />
Alternately, services can require use of the [[Infrastructure:IPsec|VPN]] on [[Infrastructure:Acidburn|acidburn]],<br />
[[Iodine]], or [[Secure Shell|ssh tunnelling]], although all of these limit usage to members with a shell account.<br />
All of these have the benefit of NAT transversal, however.<br />
<br />
== Services ==<br />
''Further information: [[:Category:Services]]''<br />
<br />
* [[Infrastructure:Acidburn|acidburn]]<br />
** Shell server<br />
** [[Email]]<br />
** [[Wadsworth]]<br />
** [[Iodine]]<br />
* [[Infrastructure:Chimera|chimera]]<br />
** FreeIPA<br />
* [[Infrastructure:Sczi|Sczi]]<br />
** Website<br />
*** [https://hokieprivacy.org hokieprivacy]<br />
*** [https://bash.vtluug.org vtbash]<br />
*** [https://vtluug.org Main Site]<br />
*** This wiki and [[gp:Main Page|Gobblerpedia]]<br />
*** dex, for authing with the wikis<br />
*** https://vtluug.org/users/~$user - User homepages<br />
*** [https://search.vtluug.org 4get] a metasearch engine<br />
*** [https://git.vtluug.org Gitea] a Github-esque git server with dex/LUUG OpenID auth<br />
*** [https://element.vtluug.org element], a Matrix client<br />
*** [https://soulseek.vtluug.org slskd]<br />
*** [https://seed.vtluug.org qbittorrent-nox]<br />
*** [https://bitwarden.vtluug.org bitwarden]<br />
* [[Infrastructure:Nikonwormhole|nikonwormhole]]<br />
** AdGuard DNS blackhole<br />
* [[Infrastructure:Dirtycow|dirtycow]]<br />
** Storage for all primary services<br />
** NFS - ZFS pool name is cistern<br />
* [[Infrastructure:Meltdown|meltdown]]<br />
** VM host for above services<br />
* [[Infrastructure:Scaryterry|scaryterry]]<br />
** [https://awm.vtluug.org AWM site]<br />
<br />
[[Infrastructure:Acidburn|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.<br />
<br />
== Website details ==<br />
=== Current Setup ===<br />
All vtluug websites are run on nginx on [[Infrastructure:Sczi|sczi]]. These sites are currently functional:<br />
* gobblerpedia.org<br />
* hokieprivacy.org<br />
* vtluug.org<br />
* wiki.vtluug.org (redirects to vtluug.org/wiki/)<br />
* bash.vtluug.org<br />
* vtluug.org/users/~$user<br />
<br />
All of these sites exclusively allow for the use of TLS connections. All services use automatically updated<br />
letsencrypt certs.<br />
<br />
==== Main Page ====<br />
The main VTLUUG page was scraped from the [[w:Internet Archive|Internet Archive]] and added created as a github page at<br />
[https://vtluug.github.io vtluug.github.io], and is reverse-proxied through [[Infrastructure:Sczi|sczi]].<br />
<br />
==== Wiki ====<br />
The wiki currently runs fully on MediaWiki hosted on nginx using a [https://github.com/vtluug/mediawiki-docker modified version of the official mediawiki docker image]. You can auth with the admin account, [[User:wiki-admin|wiki-admin]] or a Google account. See note on [[Main_page]] about why LDAP isn't working yet.<br />
<br />
===== Gobblerpedia =====<br />
Runs on the same Mediawiki instance as this wiki. Similarly to LUUGWiki, only Google accounts or the admin user are supported logins.<br />
<br />
=== Needs Restoration ===<br />
These are VTLUUG services that haven't yet been properly restored:<br />
* [https://github.com/mutantmonkey/foodforus foodfor.vtluug.org] - For [[Wadsworth]]'s .pickfood and .foodvote commands. This is [[User:Timelord|jpo's]] fault.<br />
* tahoe.vtluug.org - [[user:mjh|mhazinsk's]] Tahoe-LAFS grid<br />
* git.vtluug.org - git hosting; previously a redirect to gitweb with gitosis as the SSH backend<br />
* gitweb.vtluug.org - git hosting; previously gitweb<br />
* [https://github.com/vtluug/campusmap map.vtluug.org] - [[Openstreetmap|OSM]] based map of VT<br />
<br />
=== Historically ===<br />
<br />
See [[Dead_projects]] for historic information<br />
<br />
=== Goals ===<br />
See [[VTLUUG:Strategic_plan#Web_Services]] for future goals involving web services<br />
<br />
== Addressing ==<br />
VTLUUG currently has DNS with gandi.net. Message officers for access (please don't be scared :D).<br />
<br />
We currently hold the IPv6 prefix <code>2001:470:8:6d9::/64</code> from HE's allocation due to our tunnel.<br />
When CNS finally sets up prefix-delegation, we might be able to get something from <code>2607:b400::/32</code>,<br />
which is VT's largest allocation.<br />
<br />
{{:Infrastructure:Network}}<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:VTLUUG:Projects]]<br />
[[Category:Featured content]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8252Infrastructure:Bastille2025-12-31T18:12:14Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs (Both connected), and one Intel X520 2x10G SFP+ (Unused)<br />
* notably, no peripheral ports other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from [[Infrastructure:Vesuvius]] as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)<br />
* tor relay (rsk)<br />
** both of the above possibly better as a slim nixos VM on something like spectre?<br />
* nix build server (clj)<br />
* build/parameter optimization rust compiler (clj)<br />
* folding@home (ap, eri)<br />
* port sczi over (mkl)<br />
** slskd/slskd:latest<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** luuul/4get:latest<br />
** linuxserver/qbittorrent:latest<br />
** qmcgaw/gluetun<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** mariadb:10.4.32<br />
** vtluug/mediawiki-vtluug:1.1<br />
** linuxserver/swag<br />
** vectorim/element-web:latest<br />
** quay.io/dexidp/dex:latest<br />
** vtluug/pyqdb<br />
** thelounge/thelounge:latest<br />
** vtluug-site-vtluug-site<br />
** vaultwarden/server:latest<br />
** gitea/gitea:nightly<br />
** t4skforce/syncthing-relay-discovery:latest<br />
* Tigerbeetle (clj, meme suggestion)<br />
* Something like Sagemath but in a way that doesn't give people free ACE (clj)<br />
* map stuff (mhazinsk)<br />
** OSM tile server<br />
** async LIDAR processing - laz2ept/[https://caves.science/ sinkholes], etc<br />
* [https://github.com/coder/coder coder] ephemeral dev environments for members (mhazinsk)<br />
* [https://aleph.occrp.org/ OCCRP Aleph] for VT FOIA requests as a hokieprivacy project (mhazinsk)<br />
* [https://ooni.org/install/cli OONI probe] (mhazinsk)<br />
* browsertrix (pew)<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Vesuvius&diff=8247Infrastructure:Vesuvius2025-12-05T04:40:19Z<p>Rsk: </p>
<hr />
<div>Vesuvius is VTLUUG's 4rd(?)<ref>superseding [[Infrastructure:Dirtycow]] (still in operation), which superseded [[Infrastructure:Cyberdelia]], which superseded some ancient CVL thing presumably. anything prior is lost to recorded memory</ref> generation NFS server donated by [[User:Timelord|jpo]]<ref>It is, along with [[Infrastructure:Bastille|Bastille]], originally from the VT surplus auction.</ref>. It aims to replace [[Infrastructure:Dirtycow|Dirtycow]] and host storage for most of our services. <br />
<br />
It is a Qumulo 4U-Capacity SAN, with 128GiB DDR4, 2x Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz.<br />
<br />
It is currently [https://github.com/vtluug/construct/tree/main/hosts/vesuvius installed as NixOS] on a 64GB SSD, netbooting [[Infrastructure:Bastille|the cluster]].<br />
<br />
It currently has one (manually created) RAID-Z2 pool mounted at /forge with 8 drives of 12 Tb each, for a total capacity of ~72TB. We have capacity for 48(!) drives, but still only paper (and tape) caddies.<br />
<br />
It resides in the ECE Server Closet in [[Whittemore]].<br />
<br />
== References ==<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Network&diff=8246Infrastructure:Network2025-12-05T04:35:53Z<p>Rsk: new stuff</p>
<hr />
<div>'''IF YOU CHANGE/ADD/REMOVE SOMETHING HERE CHANGE IT IN [[VTLUUG:Inventory|Inventory]] AND/OR [[Deprecated_Inventory]] TOO'''<br />
<br />
This page describes '''specifics''' about VTLUUG's '''current''' network. For an overview, see [[Infrastructure:Networking]]<br />
=== Addresses ===<br />
{| class="wikitable"<br />
!ECE DNS<br />
!VTLUUG DNS<br />
!IPv4<br />
!Private Internal IPv4<br />
!IPv6<br />
|-<br />
| luug.ece.vt.edu<br />
| [[Infrastructure:Sczi|sczi.vtluug.org]]<br />
| 128.173.88.78<br />
| 10.98.0.11<br />
| 2607:b400:6:cc80:0:aff:fe62:b<br />
|-<br />
| N/A<br />
| [[Infrastructure:Scaryterry|scaryterry.vtluug.org]]<br />
| 128.173.89.163<br />
| 10.98.0.22<br />
| 2607:b400:6:cc80:0:aff:fe62:f<br />
|-<br />
| luug0.ece.vt.edu<br />
| [[Infrastructure:Dirtycow|dirtycow.vtluug.org]]<br />
| 128.173.89.244<br />
| 10.98.0.7<br />
| 2607:b400:6:cc80:21e:c9ff:feef:13f8<br />
|-<br />
| luug1.ece.vt.edu<br />
| [[Infrastructure:Acidburn|acidburn.vtluug.org]]<br />
| 128.173.89.245<br />
| 10.98.0.12<br />
| 2607:b400:6:cc80:0:aff:fe62:c<br />
|-<br />
| luug2.ece.vt.edu<br />
| [[Infrastructure:Meltdown|meltdown.vtluug.org]]<br />
| 128.173.89.246<br />
| 10.98.0.3<br />
| 2607:b400:6:cc80:0:aff:fe62:3<br />
|-<br />
| N/A<br />
| [[Infrastructure:Gibson|gibson.vtluug.org]]<br />
| 128.173.90.53<br />
| 10.98.0.8<br />
| 2607:b400:6:cc80:4a4d:7eff:fef9:8be5<br />
|-<br />
| luug3.ece.vt.edu<br />
| [[Infrastructure:Chimera|chimera.vtluug.org]]<br />
| 128.173.89.247<br />
| 10.98.0.10<br />
| 2607:b400:6:cc80:0:aff:fe62:a<br />
|-<br />
| N/A<br />
| [[Infrastructure:Chimera|sphinx.vtluug.org]]<br />
| 128.173.88.255<br />
| 10.98.0.20<br />
| 2607:b400:6:cc80:0:aff:fe62:d<br />
|-<br />
| luug4.ece.vt.edu<br />
| [[User:mjh|mjh.ece.vt.edu]]<br />
| 128.173.88.104<br />
| 10.98.0.254<br />
| 2607:b400:0006:cc80:0230:48ff:fe7e:28da<br />
|-<br />
| luug5.ece.vt.edu<br />
| [[Infrastructure:Shellshock|router.vtluug.org]]<br />
| 128.173.88.191<br />
| 10.98.0.1<br />
| 2001:468:c80:6103:211:43ff:fe30:a72<br />
|-<br />
| N/A<br />
| [[Infrastructure:Nikonwormhole|nikonwormhole.vtluug.org]]<br />
| 128.173.88.135<br />
| 10.98.0.21<br />
| 2607:b400:6:cc80:0:aff:fe62:e<br />
|-<br />
| mirror.ece.vt.edu<br />
| N/A *Not sure if we can actually use this IP*<br />
| 128.173.88.82<br />
| N/A<br />
| N/A<br />
|-<br />
| N/A<br />
| [[Infrastructure:Switch|switch.private.vtluug.org]] (Internal v4 only)<br />
| N/A<br />
| 10.98.0.2<br />
| N/A<br />
|-<br />
| N/A<br />
| [[Infrastructure:Spectre|spectre.vtluug.org]]<br />
| N/A<br />
| 10.98.0.4<br />
| 2607:b400:6:cc80:0:aff:fe62:4<br />
|-<br />
| N/A<br />
| [[Infrastructure:Cyberdelia|cyberdelia.vtluug.org]]<br />
| N/A<br />
| 10.98.0.6<br />
| 2607:b400:0006:cc80:0215:17ff:fe12:7670<br />
|-<br />
| luug0.math.vt.edu<br />
| [[Infrastructure:Zerocool|zerocool.vtluug.org]]<br />
| 198.82.185.170<br />
| 10.98.4.1<br />
| 2001:468:c80:6119:82c1:6eff:fe21:2b88<br />
|}<br />
<br />
See [[Deprecated_Network]] for historical information.<br />
<br />
=== VTLUUG ===<br />
==== Addresses ====<br />
===== IPv6 =====<br />
* Whit<br />
** SLAAC on 2607:b400:0006:cc80::/64<br />
* McB<br />
** SLAAC on ???::/64<br />
<br />
===== IPv4 =====<br />
* Whit<br />
** 10.98.0.0/22: internal NAT<br />
*** Static IPs: 10.98.0.0/24<br />
*** DHCP: 10.98.1.0/24<br />
*** Reserved: 10.98.2.0/24<br />
*** [[Infrastructure:Bastille|Cluster]]: 10.98.3.0/24<br />
*** Iodine: 10.98.10.0/24<br />
**** we should renumber this to .2.0/24, probably, to stay within the new IPAM<br />
** 128.173.88.1/22: publicly accessible hosts<br />
<br />
* McBryde<br />
** 10.98.4.0/22: internal NAT<br />
** Static IPs: 10.98.4.0/25<br />
*** IPMI: 10.98.4.128/25<br />
** DHCP: 10.98.5.0/25<br />
*** IPMI: 10.98.5.128/25<br />
** Reserved: 10.98.6.0/23<br />
** 198.82.185.129/22: publicly accessible hosts<br />
<br />
All hosts have an internal address (static or DHCP) and some hosts also have a globally accessible address.<br />
<br />
==== DNS ====<br />
[[Infrastructure:Shellshock|Shellshock]] and [[Infrastructure:Zerocool|Zerocool]] also function as DNS servesr for their respective sites<br />
* Whit<br />
** 10.98.0.1<br />
** 2607:b400:0006:cc80::1<br />
* McB<br />
** 10.98.4.1<br />
<br />
=== VT's DNS ===<br />
CNS maintains a few DNS servers on campus<br />
* yardbird.cns.vt.edu, 2001:468:c80:2101:0:100:0:22, 198.82.247.34<br />
* jeru.cns.vt.edu, 2001:468:c80:4101:0:100:0:42, 198.82.247.66<br />
* milo.cns.vt.edu, 2001:468:c80:6101:0:100:0:62, 198.82.247.98<br />
<br />
=== See Also ===<br />
* <s>Contact [mailto:rbrand7@vt.edu Brandon Russell] to get authoritative DNS entries added for *.ece.vt.edu</s><br />
** Brandon has left ECE -- the primary contact is [mailto:bbuskill@vt.edu Bruce Buskill], who may be less receptive to making DNS changes<br />
* Contact [mailto:breilly@vt.edu Bill Reilly] to get authoritative DNS entries assed for *.ece.vt.edu<br />
* [http://groupw.cns.vt.edu/~benchoff/cgi-bin/ipr-dump-wrapper.cgi?style=wwr network liasions]<br />
<br />
[[Category:Infrastructure]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Vesuvius&diff=8244Infrastructure:Vesuvius2025-11-17T07:25:53Z<p>Rsk: </p>
<hr />
<div>Vesuvius is VTLUUG's 4rd(?)<ref>superseding [[Infrastructure:Dirtycow]] (still in operation), which superseded [[Infrastructure:Cyberdelia]], which superseded some ancient CVL thing presumably. anything prior is lost to recorded memory</ref> generation NFS server donated by [[User:Timelord|jpo]]<ref>It is, along with [[Infrastructure:Bastille|Bastille]], originally from the VT surplus auction.</ref>. It aims to replace [[Infrastructure:Dirtycow|Dirtycow]] and host storage for most of our services. <br />
<br />
It is a Qumulo 4U-Capacity SAN, with 128GiB DDR4, 2x Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz.<br />
<br />
It is currently [https://github.com/vtluug/construct/tree/main/hosts/vesuvius installed as NixOS] on a 64GB SSD, netbooting [[Infrastructure:Bastille|the cluster]].<br />
<br />
It currently has one (manually created) RAID-Z2 pool mounted at /forge with 8 drives of 12 Tb each, for a total capacity of ~72TB. We have capacity for 48(!) drives, but still only paper (and tape) caddies.<br />
<br />
== References ==<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Main_page&diff=8243Main page2025-11-17T07:08:46Z<p>Rsk: </p>
<hr />
<div>The [[gp:Linux and Unix Users Group Wiki|Linux and Unix Users Group at Virginia Tech Wiki]] is a [[gp:free information|free reference]]. Its purpose is to document how to make the most of Virginia Tech and other resources by utilizing *nix operating systems.<br />
<br />
'''Note: Select 'VTLUUG SSO' on the Login page for VTLUUG AND Google Auth<br />
<br />
Please read [[Contributing]].<br />
<br />
If you want to engage with VTLUUG, the best thing to do is [https://vtluug.org/irc.html join our chatroom] and show up to a meeting on the calendar below.<br />
<br />
== [[Calendar]] ==<br />
{{:Calendar}}<br />
<br />
== [[VTLUUG:The_Docket|The Docket]] ==<br />
{{:VTLUUG:The_Docket}}<br />
<br />
<br />
== Awesome New & Modified Pages (Hip With The Kids !!) ==<br />
* [[Infrastructure:Bastille]]<br />
* [[Infrastructure:Vesuvius]]<br />
* [[Proxies_and_VPN]]<br />
<br />
== Featured Material ==<br />
<categorytree | mode=pages>Featured content</categorytree><br />
<br />
==Browse Wiki by Category==<br />
<categorytree | mode=pages>Root</categorytree><br />
<br />
<br />
==About this wiki==<br />
This wiki was intended to support *nix usage on campus. Here are suggested items for this wiki:<br />
* Anything related to Linux usage, such as tutorials and other documentation, especially related to that at VT<br />
* Anything related to VTLUUG (meeting minutes, infrastructure, projects, history, etc)<br />
* Technical projects that VTLUUG members (individually or collectively) have done<br />
* General geekery that doesn't fit anywhere else, related to interests of one or more VTLUUG members (e.g. audio gear, coffee, amateur radio, etc.)<br />
* Opinionated content that may not reflect the interests of the entire Virginia Tech or Blacksburg community<br />
<br />
Some items are more suited for [[gp:Main page|Gobblerpedia]], our sister wiki. These include:<br />
* General content about Blacksburg or Virginia Tech that is ''non-technical'' in nature. Please categorize these with [[:Category:Move to Gobblerpedia|Move to Gobblerpedia]] so we can later migrate them in bulk.</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Vesuvius&diff=8242Infrastructure:Vesuvius2025-11-17T07:08:15Z<p>Rsk: </p>
<hr />
<div>Vesuvius is VTLUUG's 4rd(?)<ref>superseding [[Infrastructure:Dirtycow]] (still in operation), which superseded [[Infrastructure:Cyberdelia]], which superseded some ancient CVL thing presumably. anything prior is lost to recorded memory</ref> generation NFS server donated by [[User:Timelord|jpo]]<ref>It is, along with [[Infrastructure:Bastille|Bastille]], originally from the VT surplus auction.</ref>. It aims to replace [[Infrastructure:Dirtycow|Dirtycow]] and host storage for most of our services. <br />
<br />
It is a Qumulo 4U-Capacity SAN, with 128GiB DDR4, 2x Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz.<br />
<br />
It is currently [https://github.com/vtluug/construct/tree/main/hosts/vesuvius installed as NixOS] on a 64GB SSD, netbooting [[Infrastructure:Bastille|the cluster]].<br />
<br />
It currently has one (manually created) RAID-Z2 pool mounted at /forge with 8 drives of 12 Tb each, for a total capacity of ~88TB. We have capacity for 48(!) drives, but still only paper (and tape) caddies.<br />
<br />
== References ==<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Vesuvius&diff=8241Infrastructure:Vesuvius2025-11-17T06:53:16Z<p>Rsk: </p>
<hr />
<div>Vesuvius is VTLUUG's 4rd(?)<ref>superseding [[Infrastructure:Dirtycow]] (still in operation), which superseded [[Infrastructure:Cyberdelia]], which superseded some ancient CVL thing presumably. anything prior is lost to recorded memory</ref> generation NFS server donated by [[User:Timelord|jpo]]<ref>It is, along with [[Infrastructure:Bastille|Bastille]], originally from the VT surplus auction.</ref>. It aims to replace [[Infrastructure:Dirtycow|Dirtycow]] and host storage for most of our services. <br />
<br />
It is a Qumulo 4U-Capacity SAN, with 128GiB DDR4, 2x Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz.<br />
<br />
It is currently [https://github.com/vtluug/construct/tree/main/hosts/vesuvius installed as NixOS], on a 64GB SSD, netbooting [[Infrastructure:Bastille|the cluster]].<br />
<br />
It currently one (manually created) RAID-Z2 pool mounted at /forge with 8 drives of 12 Tb each, for a total capacity of ~88TB. We have capacity for 48(!) drives, but still only paper (and tape) caddies.<br />
<br />
== References ==<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Vesuvius&diff=8240Infrastructure:Vesuvius2025-11-17T06:51:09Z<p>Rsk: </p>
<hr />
<div>Vesuvius is VTLUUG's 4rd(?)<ref>superseding [[Infrastructure:Dirtycow]] (still in operation), which superseded [[Infrastructure:Cyberdelia]], which superseded some ancient CVL thing presumably. anything prior is lost to recorded memory</ref> generation NFS server donated by [[User:Timelord|jpo]]. It aims to replace [[Infrastructure:Dirtycow|Dirtycow]] and host storage for most of our services. <br />
<br />
It is a Qumulo 4U-Capacity SAN, with 128GiB DDR4, 2x Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz, and 36 bays total.<br />
<br />
It is currently [https://github.com/vtluug/construct/tree/main/hosts/vesuvius installed as NixOS], on a 64GB SSD, netbooting [[Infrastructure:Bastille|the cluster]].<br />
<br />
It currently one (manually created) RAID-Z2 pool mounted at /forge with 8 drives of 12 Tb each. We have capacity for 48(!) drives, but still only paper (and tape) caddies.<br />
<br />
== References ==<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Cyberdelia&diff=8239Infrastructure:Cyberdelia2025-11-17T06:38:37Z<p>Rsk: she ain't dead yet.</p>
<hr />
<div>Cyberdelia, [[Infrastructure:Cyberdelia_(VM_Host)|formerly VTLUUG's second-generation VM server]], was rebuilt as an Ubuntu 24 LTS machine mirroring [[Infrastructure:Dirtycow]]'s setup in late-2024 early-2025, with 2x2TB RAID1 root, and 8x1TB ZFS RAIDZ2.<br />
<br />
It currently sits retired in this state, waiting for a reason to be used.<br />
<br />
Dmesg indicates it is a Dell PowerEdge 2900 III with board model of 0NX642<ref>http://www.dell.com/downloads/global/products/pedge/en/pe_2900_III_spec_sheet.pdf</ref>.<br />
<br />
It has 2 4-core Intel Xeon X5450 CPUs @ 3.00GHz, with 48 GiB DDR2 RAM clocked at 667MHz and 4 Gigabit NICs.<br />
<br />
It resides in the ECE Server Closet in [[gp:Whittemore|Whittemore]], and notably cannot be moved from there as an ECE-inventoried (VT asset tagged) item.<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Cyberdelia_(VM_Host)&diff=8238Infrastructure:Cyberdelia (VM Host)2025-11-17T06:33:08Z<p>Rsk: </p>
<hr />
<div>Cyberdelia was VTLUUG's second-generation VM server. It has been replaced entirely by [[Infrastructure:Meltdown|meltdown]]. It aimed to replace [[Infrastructure:Wood|Wood]] in the medium-term as a host for our more critical services. It was running CentOS 6.7.<br />
<br />
Dmesg indicates it is a Dell PowerEdge 2900 III with board model of 0NX642<ref>http://www.dell.com/downloads/global/products/pedge/en/pe_2900_III_spec_sheet.pdf</ref>.<br />
<br />
It has 2 4-core Intel Xeon X5450 @ 3.00GHz<ref>http://ark.intel.com/products/34446/Intel-Xeon-Processor-X5450-12M-Cache-3_00-GHz-1333-MHz-FSB</ref><ref>https://www.cpubenchmark.net/cpu.php?cpu=Intel+Xeon+X5450+%40+3.00GHz&cpuCount=2</ref>, with 48 GiB DDR2 RAM clocked at 667MHz, which are Samsung M395T5160CZ4-CE65 4GiB sticks.<br />
For reference: the processor currently (2016 March) goes for about $20 on ebay <ref>http://www.ebay.com/sch/items/?_nkw=intel+xeon+x5450&_sacat=&_ex_kw=&_mPrRngCbx=1&_udlo=&_udhi=&_sop=12&_fpos=&_fspt=1&_sadis=&LH_CAds=&rmvSB=true</ref><br />
<br />
It has 4 NICs, support for up to 48GiB RAM, and up to 8 hot-swap SCSI (SAS?) hard drives. The disks are<br />
configured with 7 931GiB drives, one 278.9GiB drive, and one 67.8GiB drive. The 7 identical drives are<br />
mounted in a ZFS-raid array, the smallest drive has an lvm setup on it, and a boot partition.<br />
<br />
The current pool is RAID-Z2, and has a total capacity of 6.31TiB, of which 4.06TiB (64.3%) are allocated (as of 2016 March)<br />
<br />
It resides in the <s>[[gp:CVL|CVL]]</s> ECE Server Closet in [[gp:Whittemore|Whittemore]].<br />
<br />
== VMs hosted ==<br />
Cyberdelia has the following:<br />
* [[Infrastructure:Cerealkiller|cerealkiller]] - a Tor relay (Deprecated)<br />
* [[Infrastructure:Crashoverride|crashoverride]] - a [[Tahoe-LAFS]] introducer (Deprecated)<br />
* [[Infrastructure:Sczi|sczi]] - a mail server (not yet deployed/configured) (Repurposed)<br />
* [[Infrastructure:Acidburn|Rebuilt Acidburn]] - Shell server<br />
* [[Infrastructure:Milton|Milton]] - Old webserver<br />
<br />
== Storage ==<br />
The following datasets are configured:<br />
* /tank/nfs/home - user home directories, available over NFS to VTLUUG machines<br />
* /tank/nfs/scratch - Temporary unimportant storage. Permissions are 777. No snapshots or backups.<br />
* /tank/nfs/share - For sharing media between users. <br />
* /tank/nfs/files - vtluug.org/files<br />
* /tank/libvirt - VM storage<br />
* /tank/tahoe - Tahoe-LAFS grid<br />
<br />
= Deprecation (1/19/2025) =<br />
<br />
Cyberdelia was rebuilt as an ubuntu machine mirroring [[Infrastructure:Dirtycow]]'s setup in late-2024 early-2025, with <s>8x12TB</s> 2x2TB RAID1 root, and 8x1TB ZFS RAIDZ2. Information about this incarnation will be found at [[Infrastructure:Cyberdelia]].<br />
<br />
== /tank ==<br />
the following list notes which files/dirs were exfiltrated to [[Infrastructure:Dirtycow|cistern]]. everything that was not already on cistern was copied in some capacity.<br />
<br />
* /tank/nfs/private/ -> /cistern/backup/private.7z<br />
* /tank/nfs/home<br />
** all homedirs presumed to be copied already, during [[Project_Bringing_Sexy_Back|the migration]].<br />
* /tank/nfs/scratch<br />
** /tank/nfs/scratch -> /cistern/backups/tank/nfs/scratch<br />
* /tank/nfs/share<br />
** /tank/nfs/share/media/music/mhazinsk/README -> /cistern/backups/tank/nfs/share/media/music/mhazinsk/README<br />
* /tank/nfs/files<br />
** /tank/nfs/files/pxedisk.qed -> /cistern/backups/tank/nfs/files/pxedisk.qed<br />
** /tank/nfs/files/2012/piespy/-> /cistern/backups/tank/nfs/files/2012/piespy.7z<br />
* /tank/nfs/milton_srv -> /cistern/backups/tank/nfs/milton_srv<br />
* /tank/libvirt -> /cistern/backups/tank/libvirt<br />
* /tank/tahoe -> /cistern/backups/tank/tahoe<br />
<br />
== / ==<br />
<br />
this stuff is almost certainly useless. copied anyway, because it feels unjust to rm it -- some fun could be had poking through it, maybe.<br />
<br />
* /home assumed to be copied to /tank/nfs/home, assumed to be copied to /nfs/cistern/home<br />
* /root -> /cistern/backup/cyberdelia-old/root<br />
* /opt -> /cistern/backup/cyberdelia-old/opt<br />
* /var/log -> /cistern/backup/cyberdelia-old/var/log<br />
<br />
if there was anything else, it's gone now. c'est la vie.<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]<br />
[[Category:Deprecated]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8237Infrastructure:Bastille2025-11-17T06:03:20Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs (Both connected), and one Intel X520 2x10G SFP+ (Unused)<br />
* notably, no peripheral ports other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from [[Infrastructure:Vesuvius]] as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)<br />
* tor relay (rsk)<br />
** both of the above possibly better as a slim nixos VM on something like spectre?<br />
* nix build server (clj)<br />
* build/parameter optimization rust compiler (clj)<br />
* folding@home (ap, eri)<br />
* port sczi over (mkl)<br />
** slskd/slskd:latest<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** luuul/4get:latest<br />
** linuxserver/qbittorrent:latest<br />
** qmcgaw/gluetun<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** mariadb:10.4.32<br />
** vtluug/mediawiki-vtluug:1.1<br />
** linuxserver/swag<br />
** vectorim/element-web:latest<br />
** quay.io/dexidp/dex:latest<br />
** vtluug/pyqdb<br />
** thelounge/thelounge:latest<br />
** vtluug-site-vtluug-site<br />
** vaultwarden/server:latest<br />
** gitea/gitea:nightly<br />
** t4skforce/syncthing-relay-discovery:latest<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8236Infrastructure:Bastille2025-11-17T06:02:51Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs (Both connected), and one Intel X520 2x10G SFP+ (Unused)<br />
* notably, no peripheral ports other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from Vesuvius as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)<br />
* tor relay (rsk)<br />
** both of the above possibly better as a slim nixos VM on something like spectre?<br />
* nix build server (clj)<br />
* build/parameter optimization rust compiler (clj)<br />
* folding@home (ap, eri)<br />
* port sczi over (mkl)<br />
** slskd/slskd:latest<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** luuul/4get:latest<br />
** linuxserver/qbittorrent:latest<br />
** qmcgaw/gluetun<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** mariadb:10.4.32<br />
** vtluug/mediawiki-vtluug:1.1<br />
** linuxserver/swag<br />
** vectorim/element-web:latest<br />
** quay.io/dexidp/dex:latest<br />
** vtluug/pyqdb<br />
** thelounge/thelounge:latest<br />
** vtluug-site-vtluug-site<br />
** vaultwarden/server:latest<br />
** gitea/gitea:nightly<br />
** t4skforce/syncthing-relay-discovery:latest<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8234Infrastructure:Bastille2025-11-13T04:41:33Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs (Both connected), and one Intel X520 2x10G SFP+ (Unused)<br />
* notably, no peripheral parts other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from Vesuvius as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)<br />
* tor relay (rsk)<br />
** both of the above possibly better as a slim nixos VM on something like spectre?<br />
* nix build server (clj)<br />
* build/parameter optimization rust compiler (clj)<br />
* folding@home (ap, eri)<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Main_page&diff=8230Main page2025-11-13T04:29:08Z<p>Rsk: </p>
<hr />
<div>The [[gp:Linux and Unix Users Group Wiki|Linux and Unix Users Group at Virginia Tech Wiki]] is a [[gp:free information|free reference]]. Its purpose is to document how to make the most of Virginia Tech and other resources by utilizing *nix operating systems.<br />
<br />
'''Note: Select 'VTLUUG SSO' on the Login page for VTLUUG AND Google Auth<br />
<br />
Please read [[Contributing]].<br />
<br />
If you want to engage with VTLUUG, the best thing to do is [https://vtluug.org/irc.html join our chatroom] and show up to a meeting on the calendar below.<br />
<br />
== [[Calendar]] ==<br />
{{:Calendar}}<br />
<br />
== [[VTLUUG:The_Docket|The Docket]] ==<br />
{{:VTLUUG:The_Docket}}<br />
<br />
<br />
== Awesome New & Modified Pages (Hip With The Kids !!) ==<br />
* [[Infrastructure:Bastille]]<br />
* [[Proxies_and_VPN]]<br />
<br />
== Featured Material ==<br />
<categorytree | mode=pages>Featured content</categorytree><br />
<br />
==Browse Wiki by Category==<br />
<categorytree | mode=pages>Root</categorytree><br />
<br />
<br />
==About this wiki==<br />
This wiki was intended to support *nix usage on campus. Here are suggested items for this wiki:<br />
* Anything related to Linux usage, such as tutorials and other documentation, especially related to that at VT<br />
* Anything related to VTLUUG (meeting minutes, infrastructure, projects, history, etc)<br />
* Technical projects that VTLUUG members (individually or collectively) have done<br />
* General geekery that doesn't fit anywhere else, related to interests of one or more VTLUUG members (e.g. audio gear, coffee, amateur radio, etc.)<br />
* Opinionated content that may not reflect the interests of the entire Virginia Tech or Blacksburg community<br />
<br />
Some items are more suited for [[gp:Main page|Gobblerpedia]], our sister wiki. These include:<br />
* General content about Blacksburg or Virginia Tech that is ''non-technical'' in nature. Please categorize these with [[:Category:Move to Gobblerpedia|Move to Gobblerpedia]] so we can later migrate them in bulk.</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8229Infrastructure:Bastille2025-11-13T04:27:19Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs, and one 10G SFP+<br />
* notably, no peripheral parts other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from Vesuvius as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)<br />
<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8228Infrastructure:Bastille2025-11-13T04:27:01Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs, and one 10G SFP+<br />
* notably, no peripheral parts other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from Vesuvius as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8227Infrastructure:Bastille2025-11-13T04:26:41Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs, and one 10G SFP+<br />
* notably, no peripheral parts other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from Vesuvius as NixOS k3s nodes.<br />
<br />
== Things To Host On All This ==<br />
<br />
* hentai at home (rsk)</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8226Infrastructure:Bastille2025-11-13T04:26:07Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs, and one 10G SFP+<br />
* notably, no peripheral parts other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from Vesuvius as NixOS k3s nodes.<br />
<br />
== Things To Host On All This <br />
<br />
* hentai at home (rsk)</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8225Infrastructure:Bastille2025-11-13T04:25:08Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs, and one 10G SFP+<br />
* notably, no peripheral parts other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre></div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8224Infrastructure:Bastille2025-11-13T03:15:45Z<p>Rsk: </p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades':<br />
<br />
<pre><br />
[papatux@excalibur:~]$ fastfetch -l none<br />
papatux@excalibur<br />
-----------------<br />
OS: NixOS 25.11 (Xantusia) x86_64<br />
Host: Lenovo NeXtScale nx360 M5: -[5465AC1]- (06)<br />
Kernel: Linux 6.12.45<br />
Uptime: 1 day, 20 hours, 6 mins<br />
Packages: 391 (nix-system)<br />
Shell: bash 5.3.3<br />
Display (VGA-1): 1024x768 [External]<br />
Terminal: /dev/pts/0<br />
CPU: 2 x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz<br />
GPU: Matrox Electronics Systems Ltd. G200eR2<br />
Memory: 3.88 GiB / 251.19 GiB (2%)<br />
Swap: Disabled<br />
Disk (/): 329.43 MiB / 125.59 GiB (0%) - tmpfs<br />
Local IP (eno1): 10.98.1.36/16<br />
Locale: en_US.UTF-8<br />
[papatux@excalibur:~]$<br />
</pre></div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8223Infrastructure:Bastille2025-11-13T02:57:40Z<p>Rsk: Created page with "Bastille is our Lenovo Nextscale chassis donated by jpo from his VT Surplus spoils."</p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.</div>Rskhttps://vtluug.org/w/index.php?title=VTLUUG:History&diff=8221VTLUUG:History2025-11-05T18:32:23Z<p>Rsk: </p>
<hr />
<div>The Linux and Unix Users Group was founded in October of 1997 as the Virginia Tech Linux Users Group (VTLUG). After realizing the name clash with the Vermont Linux Users Group, the organization changed its name to the Virginia Tech Linux and Unix Users Group (VTLUUG). In the fall of 2009, the name was again changed, this time to comply with registered student organization regulations. Virginia Tech was moved to the end of the organization's full name, but the acronym has been kept, in part because changing domain names would be a hassle. <br />
<br />
== Fall 1997 ==<br />
* Founded in October 1997 as the Linux Users Group of Virginia Tech<br />
* Eventually became L/UUG to encompass Unix<br />
<br />
== Fall 1998 ==<br />
* Rob Nelson<br />
* Clemmitt Sigler<br />
* [http://search.luky.org/cola.1998/msg01361.html Announcement of first meeting]<br />
* [http://www.debian.org/events/1998/1205-vatech-installfest Installfest] held<br />
<br />
== Spring 1999 ==<br />
* [http://web.archive.org/web/19990219122456/http://corvette.me.vt.edu/~vtlug/ Old website]<br />
* Server was corvette.me.vt.edu, a Pentium 133 which hosted the LUUG website, as well as Linux distributions over FTP and NFS<br />
* Early February, 1999: Members of the L/UUG at VT officially begin planning a [[VTLUUG:Beowulf Cluster|Beowulf Cluster]] project.<br />
<br />
== Fall 1999 ==<br />
* Beowulf cluster completed?<br />
<br />
== Spring 2001 ==<br />
;President :H. Lally Singh<br />
;Vice President :Josh Baugher<br />
;Treasurer :George Morgan <br />
;Secretary :Wes Kurdziolek<br />
;Steering Committee<br />
: Clemmitt Sigler<br />
: Josh Baugher<br />
: Bucky LaDieu<br />
: H. Lally Singh<br />
: Nick Maniscalco<br />
;Worker Peons<br />
: Clemmitt Sigler (sysadmin)<br />
: Rob Nelson (sysadmin)<br />
: Logan Hanks (webmaster)<br />
: Rob Hunter (webmaster)<br />
;Donors<br />
: Vincent Rivellino<br />
: Adam Kendall<br />
: Lyle Evans<br />
: Kermit Duncan<br />
: Austin Graves<br />
: Ethan James<br />
<br />
== Fall 2001 ==<br />
;President :Wes Kurdziolek<br />
;VP of IT :Rob Hunter<br />
;Treasurer :Joseph Goodman<br />
<br />
== Spring 2002 ==<br />
;President :Wes Kurdziolek<br />
;VP of IT :Rob Hunter<br />
;Treasurer :Joseph Goodman<br />
<br />
== Fall 2002 ==<br />
;President :Wes Kurdziolek<br />
;VP of IT :Rob Hunter<br />
;Treasurer :Joseph Goodman<br />
<br />
== Spring 2003 ==<br />
;President :Wes Kurdziolek<br />
;VP of IT :Rob Hunter<br />
;Treasurer :Joseph Goodman<br />
<br />
== Fall 2003 ==<br />
;President :Wes Kurdziolek<br />
;VP of IT :Rob Hunter<br />
;Treasurer :Joseph Goodman<br />
<br />
== Spring 2004 ==<br />
Club did not exist<br />
<br />
== Fall 2004 ==<br />
;President :H. Lally Singh<br />
;Vice President :Jerome Holman<br />
<br />
== Spring 2005 ==<br />
;President :Ben Hilburn<br />
<br />
* Installfests started<br />
* Crash courses started<br />
* BoFs restarted<br />
<br />
== Fall 2005 ==<br />
;President :Ben Hilburn<br />
;Vice President :Sean Elble<br />
<br />
== Spring 2006 ==<br />
;President :Ben Hilburn<br />
;Vice President :Sean Elble<br />
* Registered as non-profit with IRS in June<br />
<br />
== Fall 2006 ==<br />
;President :Ben Hilburn<br />
;Vice President :Sean Elble<br />
;Treasurer :Dan Caughran<br />
<br />
== Spring 2007 ==<br />
;President :Ben Hilburn<br />
;Vice President :Sean Elble<br />
;Treasurer :Dan Caughran<br />
<br />
== Fall 2007 ==<br />
;President :Sean Elble<br />
;Vice-President :Dan Caughran<br />
;Treasurer :Dan Cohn<br />
;Secretary :Ben Hilburn<br />
;Programs Manager :Casey Link<br />
;Systems Administrator :Dave Vogt<br />
;Graduate Liaison :Chris Lasher<br />
<br />
== Spring 2008 ==<br />
;President :Sean Elble<br />
;Vice President :Dan Caughran<br />
;Secretary :Ben Hilburn<br />
<br />
== Fall 2008 ==<br />
;President :Casey Link<br />
;Activities Coordinator :[[User:Cov|Christopher Covington]]<br />
<br />
== Spring 2009 ==<br />
;Benevolent Dictator :Christopher Covington<br />
;Graduate Liaison :Chris Lasher<br />
<br />
== Fall 2009 ==<br />
;President :Christopher Covington<br />
;Vice President :Paul Galiatsatos<br />
<br />
== Spring 2010 ==<br />
;President :Christopher Covington<br />
<br />
* [[Cyber Security Competition]]<br />
<br />
== Fall 2010 ==<br />
;President :[[User:Mutantmonkey|James Schwinabart]]<br />
;Vice President :Stephen Tanner<br />
;Treasurer :Christopher Covington<br />
<br />
* [[Infrastructure:Wood|Wood]] was built with hardware selected by the [[Hardware Selection Task Force]]<br />
<br />
== Spring 2011 ==<br />
;President :[[User:Mutantmonkey|James Schwinabart]]<br />
;Vice President :[[User:Ram|Reese Moore]]<br />
;Treasurer :Christopher Covington<br />
<br />
* The LUUG participated in the [[Collegiate Cyber Defense Competition]] for the first time<br />
* [[gp:Gobblerpedia|Gobblerpedia]] launched on February 11, 2011<br />
* [[u:Uniluug|Uniluug]] launched<br />
* Participated in e-week for [[gp:Students Engineers' Council|SEC]] and ran an arcade booth with GNU/Linux games<br />
<br />
== Fall 2011 ==<br />
;President :[[User:Mutantmonkey|James Schwinabart]]<br />
;Vice President :Reese Moore<br />
;Treasurer :Erich Alderfer<br />
<br />
== Spring 2012 ==<br />
;President :[[User:Mutantmonkey|James Schwinabart]]<br />
;Vice President :Reese Moore<br />
;Treasurer :Lukas Lozovski<br />
<br />
==Fall 2012==<br />
;President :Calvin Winkowski [[User:Telnoratti]]<br />
;Vice President :Lukas Lozovski<br />
;Treasurer :James Gross<br />
;Sysadmin :[[User:Mutantmonkey|James Schwinabart]]<br />
;Outreach Coordinator :Reese Moore<br />
* October 2012 is the [[15th Anniversary]] of VTLUUG!<br />
* [[Infrastructure:Blade|Blade]] added for central authentication using Kerberos and LDAP<br />
<br />
==Spring 2013==<br />
;President :[[User:Mjh|Matt Hazinski]]<br />
;Treasurer :James Gross<br />
;Sysadmin :[[User:Mutantmonkey|James Schwinabart]]<br />
;Graduate Liason :Reese Moore<br />
* [[Infrastructure:Sunway|Sunway]] cluster created<br />
<br />
==Fall 2013==<br />
;President :Matt Hazinski<br />
;Vice President :[[User:Andreim|Andrei Marcu]]<br />
;Treasurer :Jacob Melton<br />
;Activies Coordinator :Noah Luther<br />
;Sysadmin :Calvin Winkowski [[User:Telnoratti]]<br />
* [[Infrastructure:Cyberdelia|Cyberdelia]] acquired for [[EL Migration Project]]<br />
<br />
==Spring 2014==<br />
;President :[[User:Mjh|Matt Hazinski]]<br />
;Vice President :[[User:Andreim|Andrei Marcu]]<br />
;Treasurer :Jacob Melton<br />
;Sysadmin :Calvin Winkowski [[User:Telnoratti]]<br />
* Start of [[EL Migration Project]]<br />
* [[Super-secret Cluster Project]] on [[Infrastructure:Sunway|Sunway]]<br />
<br />
==Fall 2014==<br />
;President :[[User:Andreim|Andrei Marcu]]<br />
;Vice President :[[User:Mjh|Matt Hazinski]]<br />
;Treasurer :Ben Weinstein-Raun<br />
;Sysadmin :Nathan McCloskey<br />
;Sysadmin Emeritus :Calvin Winkowski [[User:Telnoratti]]<br />
<br />
==Spring 2015==<br />
;President :[[User:Andreim|Andrei Marcu]]<br />
;Vice President :[[User:Mjh|Matt Hazinski]]<br />
;Treasurer :Ben Weinstein-Raun<br />
;Sysadmin Emeritus :Calvin Winkowski [[User:Telnoratti]]<br />
<br />
== Fall 2015 ==<br />
;President :[[User:Ackthet|Wade Duvall]]<br />
;Vice President :[[User:Uncurlhalo|Jacob Melton]]<br />
;Treasurer :Daniel Setareh<br />
;Sysadmin :John Volk<br />
;Sysadmin Emeritus :Calvin Winkowski [[User:Telnoratti]]<br />
<br />
* [[CVL eviction]]<br />
<br />
==<span class="mw-headline" id="current">Spring 2016</span>==<br />
;President :[[User:Ackthet|Wade Duvall]]<br />
;Vice President :[[User:Uncurlhalo|Jacob Melton]]<br />
;Treasurer :[[User:dsetareh|Daniel Setareh]]<br />
;Sysadmin :[[User:johnv|John Volk]]<br />
<br />
==<span class="mw-headline" id="current">Fall 2017</span>==<br />
;President :[[User:uncurlhalo|Jacob Melton]]<br />
;Vice President :[[User:marcus|Marcus Wanners]]<br />
;Treasurer :[[User:johnv|John Volk]]<br />
;Sysadmin :[[User:echarlie|VACANT]]<br />
<br />
==<span class="mw-headline" id="current">Spring 2017</span>==<br />
;President :[[User:marcus|Marcus Wanners]]<br />
;Vice President :[[User:echarlie|E. C. Landgraf]]<br />
;Treasurer :[[User:johnv|John Volk]]<br />
;Sysadmin :[[User:pew|VACANT]]<br />
<br />
== Fall 2017 ==<br />
;President :[[User:marcus|Marcus Wanners]]<br />
;Vice President :[[User:echarlie|E. C. Landgraf]]<br />
;Treasurer :[[User:bgregos|Brendan Gregos]]<br />
;Sysadmin :[[User:pew|Paul Walko]]<br />
<br />
* October marks the 20th anniversary of the LUUG<br />
<br />
== Spring 2018 ==<br />
;President :[[User:marcus|Marcus Wanners]]<br />
;Vice President :[[User:echarlie|E. C. Landgraf]]<br />
;Treasurer :[[User:bgregos|Brendan Gregos]]<br />
;Sysadmin :[[User:pew|Paul Walko]]<br />
<br />
== Fall 2018 ==<br />
;President :[[user:bgregos|Brendan Gregos]]<br />
;VP :[[user:pew|Paul Walko]]<br />
;Treasurer :[[user:toocrazzzzy|Aaron Brown]]<br />
;Sysadmin :[[user:pconte|Philip Conte]]<br />
;Social Media Director :[[user:h4des|Joseph Ha]]<br />
;Minority Event Coordinator :[[user:dankcvives|Cristian Vives]]<br />
;Graduate Coordinator :[[user:axlit|axlit]]<br />
<br />
== Spring 2019 ==<br />
;President :[[user:bgregos|Brendan Gregos]]<br />
;VP :[[user:pew|Paul Walko]]<br />
;Treasurer :[[user:toocrazzzzy|Aaron Brown]]<br />
;Sysadmin :[[user:pconte|Philip Conte]]<br />
;Social Media Director :[[user:h4des|Joseph Ha]]<br />
;Minority Event Coordinator :[[user:dankcvives|Cristian Vives]]<br />
;Graduate Coordinator :[[user:axlit|axlit]]<br />
<br />
== Fall 2019 ==<br />
;President :Philip Conte<br />
;VP :Chandler Cain<br />
;Treasurer :Grant Batdorff<br />
;Sysadmin :Josh Kirkham<br />
;Social Media Director :Joseph Ha<br />
;Sanitation Engineer :Aaron Brown<br />
<br />
== Spring 2020 ==<br />
;President :Philip Conte<br />
;VP :Chandler Cain<br />
;Treasurer :Grant Batdorff<br />
;Sysadmin :Josh Kirkham<br />
;Social Media Director :Joseph Ha<br />
;Sanitation Engineer :Aaron Brown<br />
<br />
== Fall 2020 ==<br />
<br />
;President :Ryan Gniadek<br />
;Vice President :Joshua Detwiler<br />
;Treasurer :Grant Batdorff<br />
;Sysadmin :Josh Kirkham<br />
;Outreach Chair :Ben Bernstein<br />
;Emacs and Arch Evangelist :Daniel Guagliardo <br />
<br />
== Fall 2021 ==<br />
;Ryan Gniadek :President<br />
;Jared Beller :Vice President and BSD Evangelist<br />
;Hao Xiang Liew :Sysadmin<br />
;Benjamin :Treasurer<br />
;Daniel Guagliardo :Emacs and Arch Evangelist<br />
<br />
== Spring 2022==<br />
;Ryan Gniadek :President<br />
;Jared Beller :Vice President and BSD Evangelist<br />
;Hao Xiang Liew :Sysadmin<br />
;Benjamin :Treasurer<br />
;Daniel Guagliardo :Emacs and Arch Evangelist<br />
<br />
== Fall 2024 ==<br />
;President :Milo Craun<br />
;Treasurer :Rishi Krishna<br />
<br />
<br />
== Spring 2025 ==<br />
;President :[[User:Rsk|Rishi Krishna]]<br />
;VP: [[User:Crazyspike|Brendan Roeting]]<br />
;Treasurer/Sysadmin :[[User:Daddykeystroke|Xavier Henschel]]<br />
;Supreme internet leader of the airgap nation: [[User:Botjoe|Sam Squier]]<br />
;Graduate Advisor: [[User:Coolcuber|Ross George]]<br />
<br />
== Fall 2025 ==<br />
;President :[[User:Enzoisotton]]<br />
;VP: [[User:Clj]]<br />
;Treasurer: [[User:Mikhail]]<br />
;Deposed: [[User:Rsk]]<br />
<br />
[[Category:VTLUUG:Administration]]</div>Rskhttps://vtluug.org/w/index.php?title=VTLUUG:The_Docket&diff=8201VTLUUG:The Docket2025-08-23T02:01:23Z<p>Rsk: </p>
<hr />
<div>The Holy Docket, a.k.a. Shit What Needs To Get Done<br />
<br />
last updated <b>08/22/25</b><br />
<br />
* .owes for Wadsworth<br />
** for tracking waffle house buys, blood oaths, etc.<br />
* brainstorm fun services to host on our ample [[Infrastructure]]<br />
** e.g. [https://github.com/iv-org/invidious invidious (yt frontend)], [https://github.com/sekai-soft/guide-nitter-self-hosting/ nitter (twitter frontend)], [[Mirrors|distro package mirrors]], game servers, etc.<br />
* do some severe spring cleaning on the wiki, especially regarding conflicting information re: Infrastructure<br />
** e.g. the page on [[Infrastructure:Cyberdelia]] should be updated to reflect the information that it is not running<br />
[[Category:Roadmap]]</div>Rskhttps://vtluug.org/w/index.php?title=VTLUUG:The_Docket&diff=8200VTLUUG:The Docket2025-08-23T02:01:08Z<p>Rsk: </p>
<hr />
<div>The Holy Docket, a.k.a. Shit What Needs To Get Done<br />
<br />
last updated <b>05/09/25</b><br />
<br />
* .owes for Wadsworth<br />
** for tracking waffle house buys, blood oaths, etc.<br />
* brainstorm fun services to host on our ample [[Infrastructure]]<br />
** e.g. [https://github.com/iv-org/invidious invidious (yt frontend)], [https://github.com/sekai-soft/guide-nitter-self-hosting/ nitter (twitter frontend)], [[Mirrors|distro package mirrors]], game servers, etc.<br />
* do some severe spring cleaning on the wiki, especially regarding conflicting information re: Infrastructure<br />
** e.g. the page on [[Infrastructure:Cyberdelia]] should be updated to reflect the information that it is not running<br />
[[Category:Roadmap]]</div>Rskhttps://vtluug.org/w/index.php?title=VTLUUG:The_Docket&diff=8190VTLUUG:The Docket2025-05-09T21:24:39Z<p>Rsk: </p>
<hr />
<div>The Holy Docket, a.k.a. Shit What Needs To Get Done<br />
<br />
last updated <b>05/09/25</b><br />
<br />
* re-make Wadsworth<br />
* brainstorm fun services to host on our ample [[Infrastructure]]<br />
** e.g. [https://github.com/iv-org/invidious invidious (yt frontend)], [https://github.com/sekai-soft/guide-nitter-self-hosting/ nitter (twitter frontend)], [[Mirrors|distro package mirrors]], game servers, etc.<br />
* do some severe spring cleaning on the wiki, especially regarding conflicting information re: Infrastructure<br />
** e.g. the page on [[Infrastructure:Cyberdelia]] should be updated to reflect the information that it is not running<br />
[[Category:Roadmap]]</div>Rskhttps://vtluug.org/w/index.php?title=Respondus_LockDown_Browser&diff=8154Respondus LockDown Browser2025-03-18T16:19:11Z<p>Rsk: basic installer reversing</p>
<hr />
<div>Respondus LockDown Browser is a piece of proprietary online testing software developed by Respondus, Inc, and used by departments, including the Department<br />
of Engineering Education. Success in running under [[w:Wine (software)|Wine]] varies from version to version, and may involve complex installation procedures, and the software<br />
actively prevents itself from running in a<br />
[http://support.respondus.com/support/index.php?/Knowledgebase/Article/View/201/25/students-see-the-warning-the-browser-cant-be-used-in-virtual-machine-software-such-as-virtual-pc-vmware-and-parallels virtual machine].<br />
<br />
== Official Description ==<br />
<br />
From the [http://respondus.com/products/lockdown-browser/index.shtml Product page]:<br />
<br />
<em>LockDown Browser® is a custom browser that locks down the testing environment within Blackboard, ANGEL, Brightspace by D2L, Canvas, Moodle, and Sakai. When students use LockDown Browser they are unable to print, copy, go to another URL, or access other applications. When an assessment is started, students are locked into it until they submit it for grading. Available for Windows, Mac and iOS [sic].</em><br />
<br />
=== <s> Features </s> Bugs ===<br />
<br />
* Integrates with Blackboard, ANGEL, Brightspace by D2L, Canvas, Moodle, and Sakai<br />
* Assessments are displayed full-screen and cannot be minimized<br />
* Assessments cannot be exited until submitted by users for grading<br />
<br />
* Task switching or access to other applications is prevented<br />
* Print, Print Screen and capturing functions are disabled<br />
* Copying and pasting anything to and from an assessment is prohibited<br />
* Screen capture, messaging, screen-sharing, virtual machine, and network monitoring applications are blocked from running<br />
* Right-click menu options and function keys are disabled<br />
* Browser menu and toolbar options are disabled, except for Back, Forward, Refresh and Stop<br />
<br />
* Source code for the HTML page cannot be viewed<br />
* The browser automatically starts at the login page for the institution’s learning management system<br />
* URLs cannot be typed by the user<br />
* External links don’t compromise the locked testing environment<br />
* Pages from the assessment are not stored on the computer after exiting<br />
<br />
* Assessments that are set up for use with LockDown Browser cannot be accessed with other browsers<br />
* Localized for multiple languages, including English, Spanish, French, German, Italian, and Portuguese<br />
* Available for both Windows and Mac computers, as well as iPad<br />
<br />
===Malware===<br />
LockDown requires administrative privileges to run, and cannot be run as an unprivileged user.<br />
Features of the browser could be construed to violate [http://www.vt.edu/about/acceptable-use.html Virginia Tech Acceptable Use Policy]<br />
by <em>engag[ing] in any activity that might be purposefully harmful to systems or to any information stored thereon...</em>, however<br />
its use is not widespread enough for this to gain any note.<br />
<br />
There is a further extension to Respondus LockDown, called Respondus Monitor<br />
<ref>http://respondus.com/products/monitor/</ref> that allows the proctor to spy on users through their webcam.<br />
<br />
==Running the Software==<br />
=== Download ===<br />
LockDown Browser's download website shows the download option based on your OS. Since it does not support Linux, it does not let you download it. So, to download this <s>shitty</s> browser, you need to change the OS in your User Agent to Windows.<br />
<br />
The file name must include the school's 9-digit ID code (for VT: 776344933). This must be immediately preceded by a '-' hyphen. If there are multiple numeric sequences '''exactly''' 9-digits long and preceded by a hyphen, the first one is interpreted as the ID code.<br />
<br />
The following file names would work:<br />
<br />
<code>LockDownBrowser-2-1-3-00-776344933.exe</code><br><br />
<code>LockDown-776344933-March-03-2025.exe</code><br><br />
<code>LD-03032025-776344933.exe</code><br><br />
<code>999999999-776344933-999999999.exe</code><br><br />
<code>LDB-0000000000-776344933-999999999.exe</code><br><br />
Note: the ID id is '''always''' the first 9 digit number with a hyphen in front. The .exe is optional.<br />
<br />
Likewise, the following file name would '''NOT''' work:<br />
<br />
<code>LockDownBrowser776344933.exe</code> This does not have a hyphen before the 9-digit code.<br><br />
<code>LockDown-030320251-776344933.exe</code>This has multiple 9-digit sequences, but the ID code is not first.<br><br />
<code>776344933.exe</code>The ID code is not preceded by a hyphen<br><br />
<code>Lockdown.exe</code>The ID code simply isn't in the file name<br><br />
<br />
To pull down VT's executable with the default name, try<br />
<code><br />
curl -LO $(curl -L "https://download.respondus.com/lockdown/$(curl -L "https://download.respondus.com/lockdown/download.php?ID=776344933" -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.3" 2>/dev/null | grep -ioE "download[0-9].php\?id=[0-9]*")" 2>/dev/null| grep -ioE "https.*.exe" | uniq)<br />
</code><br />
<br />
<br />
===Wine===<br />
There are multiple tutorials available by a quick web search which claim to get this working in Wine, <s>however, to date, no member of<br />
VTLUUG has succeeded in doing so and existing information indicates it varies by version of the browser.</s><br />
There is a solution for running LockDown browser with Wine, provided by [[User:caleb|caleb]] adapted from [https://www.reddit.com/r/UTEP/comments/1bkslgy/tutorial_running_lockdown_browser_on_linux/ this] Reddit post.<br />
<br />
This solution requires [https://github.com/Winetricks/winetricks winetricks]<br />
<br />
====IMPORTANT NOTE====<br />
While we here at VTLUUG promote the use of free software, many people at the university '''DO NOT'''. Follow these steps at your own risk, and '''ALWAYS''', ask your professor before using LockDown Browser in this ''unsupported'' configuration on an actual exam. Additionally, abusing flaws in Wine's compatibility in order to cheat or otherwise obtain an unfair advantage on exams is '''against the honor code'''. If cheating is your primary goal, there are certainly better ways if you do some research. If one person is caught abusing Wine to cheat on an exam, professors will not allow '''anyone''' to use it anymore, requiring '''everyone''' to use the non-free Windows operating system. If you are tempted to cheat on an exam, consider reaching out to your professor or TA and setting up office hours to discuss the exam.<br />
<br />
Additionally, if this method ever fails to work, ensure you have some kind of backup. Whether that is a Windows live-USB you can boot from on the day of the test, a second partition, or an entirely different device, '''bring it with you'''. Many courses provide test exams, which you can use to verify this still works a few hours in advance of the exam. The Chemistry department has a good one, and it is accessible as long as you have taken the course in a previous semester or are currently taking the course.<br />
<br />
====Step 1: Setup====<br />
First, install the following packages from your distributions package manager (names may differ):<br />
<br />
<code><br />
wine winetricks gnutls<br />
</code><br />
<br />
for Debian, the command is<br />
<br />
<pre><br />
# apt install wine gnutls-bin winetricks<br />
</pre><br />
Note that winetricks is only available in the <code>contrib</code> repository on vanilla Debian. Winetricks can be downloaded from their github as a bash script if enabling the contrib repository is not desired.<br />
<br />
====Step 2: Winetricks====<br />
Using winetricks, we can install all of the (non-free) fonts and msftedit, which is related to rich text edit controls.<ref>https://learn.microsoft.com/en-us/windows/win32/controls/about-rich-edit-controls</ref><br />
<br />
<pre><br />
$ winetricks msftedit allfonts<br />
</pre><br />
<br />
====Step 3: Install====<br />
Now simply run:<br />
<br />
<pre><br />
$ wine filename<br />
</pre><br />
<br />
replacing <code>filename</code> with the exact filename of the executable. If an error about the filename missing the 9-digit ID-code appears, ensure the file is [[#Download | properly named]]. After the program is installed, a .desktop file should automatically be created. Launching that file will load the LockDown Browser. Many features work on Gnome, such as detecting when switching desktops using a gesture or attempting to switch to another application. Other desktop environments and window managers have not been tested (yet).<br />
<br />
===Virtual Machine (KVM)===<br />
This refuses to run in a Virtual Machine. It may be possible to add the <code>-cpu kvm=off</code> flag to Qemu to prevent it from detecting a virtualized<br />
environment, but this has not been tested to date. It may also be necessary to disable Virtio drivers and devices.<br />
<br />
===Natively (Windows or OS X)===<br />
To run on Windows, the software requires administrative privileges. Previous versions were shown to have used Internet Explorer with certain modifications<br />
executed on the fly, to add the "Lock Down" features, however it currently appears to be a stand-alone browser with some resemblance to Google's Chrome. On both OS X and Windows, it is based off of the open-source Chromium<br />
<ref>http://respondus.com/products/lockdown-browser/requirements.shtml</ref>, although previous OS X versions are<br />
believed to have piggybacked off of Safari features. On Windows, the running user must have administrative privileges to run the student edition, however administrative privileges are not necessary to run the browser on OS X.<br />
<br />
A version for iOS (iPad-only) is also available, as well as a version for centrally managed Chromebooks for education (k-12).<br />
<br />
== Analysis ==<br />
The initially downloaded .exe is an InstallShield self-extracting installer. The 9-digit ID is not checked by this installer during the extraction process whatsoever -- it is simply copied from the filename into a temporary file in the extraction working directory (on Wine, <code>c/users/hokietux/AppData/Local/Temp/ldz<some string>/id.txt</code>, though this is dynamically generated using winapi's <code>GetTempPathA</code> then <code>GetTempFileNameA</code>).<br />
<br />
Only cursory analysis has been done thus far, as the author of this article doesn't have a native windows box to run Respondus on. It appears that on launch, it first connects to an unencrypted http server running in AWS, presumably to check if the version is current, then it checks if it is in a virtualized environment.<br />
<br />
==Other Notes==<br />
===Actual Bugs===<br />
* No support for U2F -- requires second (expensive) device for other [[gp:2FA|2 Factor Authentication]] methods<br />
* Easily circumvented<br />
** Most students have second computer (i.e. Smartphone), which can be used for cheating (i.e. Google searching)<br />
** Circumvention methods disadvantage students of lower income, who do not have second device.<br />
* No Linux version, disadvantaging students promoting the use of <b>free software</b><br />
* Does not prevent collaboration in out-of-class testing<br />
* Superfluous for in-class testing, where students are visually monitored anyway<br />
** At most just promotes lazy proctoring of exams<br />
* Cannot take multiple tests within a single session<br />
* Requires administrative privileges which may not be available on multi-user machines<br />
* Hostile to users of password managers<br />
<br />
=== Open questions on debugging ===<br />
* Is a TLS cert chain bundled, or can it be MITMed?<br />
* What kind of protocol does it use to authenticate that it is respondus<br />
** A Kerberos-like protocol would be optimal, but I'd be surprised if they did it<br />
* Does the binary do any integrity checks?<br />
* Does qemu-only emulated devices adequately obfuscate that it runs in a VM? Doesn't seem to<br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Software]]</div>Rskhttps://vtluug.org/w/index.php?title=Emacs&diff=8147Emacs2025-03-04T22:28:38Z<p>Rsk: how do i delete a page plzhalp</p>
<hr />
<div>Emacs is an extensible text editor "family", the most well-known instance being GNU Emacs, released by the GNU foundation and originally developed by Richard Stallman.<br />
<br />
Most currently developed <code>emacs</code> implementations share its characteristic extensibility, acting more as a software platform for Elisp ([[Emacs]] [[Lisp]]) modules. Aside from being a text editor, it can be used to connect to IRC, check mail, run autohotkey-esque scripts, and play simple games.<br />
<br />
[[Category:Software]]</div>Rskhttps://vtluug.org/w/index.php?title=Vim&diff=8146Vim2025-03-04T22:23:45Z<p>Rsk: this really isnt big enough to be a page but i don't know how to delete mediawiki pages lol</p>
<hr />
<div>Vim (Vi Improved) is a mode-ular text editor developed by Bram Moolenaar based off of the [[Vi]] text editor by Bill Joy. It is released under its own license, which encourages people to donate to children in Uganda. <br />
<br />
The <code>vi</code> family of editors are notable for their keyboard-centric approach to editing, with extensive support for macros.<br />
<br />
[[Category:Software]]</div>Rskhttps://vtluug.org/w/index.php?title=Vim&diff=8145Vim2025-03-04T22:21:43Z<p>Rsk: </p>
<hr />
<div>Vim (Vi Improved) is a text editor developed by Bram Moolenaar based off of the [[Vi]] text editor by Bill Joy. It is licensed under its own license, which encourages people to donate to children in Uganda. <br />
It is popular among VTLUUG members.</div>Rskhttps://vtluug.org/w/index.php?title=User:Giggybyte&diff=8144User:Giggybyte2025-03-04T22:09:24Z<p>Rsk: </p>
<hr />
<div>== About ==<br />
Dustin. Joined VTLUUG freshman year Fall 2017. Jack of no trades and master of none. Talks too much in IRC. Current duck champion in #vtluug.<br />
== Quotes ==<br />
"god dammit dustin" -- echarlie<br />
<br />
"faggot" -- pew<br />
== Contact ==<br />
giggybyte on irc.oftc.net <br />
<br />
dws@vt.edu (not afraid of web crawlers) <br />
<br />
If you see a giggybyte on some website, it's probably Dustin.<br />
<br />
[[Category:Home]]</div>Rskhttps://vtluug.org/w/index.php?title=Respondus_LockDown_Browser&diff=8143Respondus LockDown Browser2025-03-04T21:02:46Z<p>Rsk: </p>
<hr />
<div>Respondus LockDown Browser is a piece of proprietary online testing software developed by Respondus, Inc, and used by departments, including the Department<br />
of Engineering Education. Success in running under [[w:Wine (software)|Wine]] varies from version to version, and may involve complex installation procedures, and the software<br />
actively prevents itself from running in a<br />
[http://support.respondus.com/support/index.php?/Knowledgebase/Article/View/201/25/students-see-the-warning-the-browser-cant-be-used-in-virtual-machine-software-such-as-virtual-pc-vmware-and-parallels virtual machine].<br />
<br />
== Official Description ==<br />
<br />
From the [http://respondus.com/products/lockdown-browser/index.shtml Product page]:<br />
<br />
<em>LockDown Browser® is a custom browser that locks down the testing environment within Blackboard, ANGEL, Brightspace by D2L, Canvas, Moodle, and Sakai. When students use LockDown Browser they are unable to print, copy, go to another URL, or access other applications. When an assessment is started, students are locked into it until they submit it for grading. Available for Windows, Mac and iOS [sic].</em><br />
<br />
=== <s> Features </s> Bugs ===<br />
<br />
* Integrates with Blackboard, ANGEL, Brightspace by D2L, Canvas, Moodle, and Sakai<br />
* Assessments are displayed full-screen and cannot be minimized<br />
* Assessments cannot be exited until submitted by users for grading<br />
<br />
* Task switching or access to other applications is prevented<br />
* Print, Print Screen and capturing functions are disabled<br />
* Copying and pasting anything to and from an assessment is prohibited<br />
* Screen capture, messaging, screen-sharing, virtual machine, and network monitoring applications are blocked from running<br />
* Right-click menu options and function keys are disabled<br />
* Browser menu and toolbar options are disabled, except for Back, Forward, Refresh and Stop<br />
<br />
* Source code for the HTML page cannot be viewed<br />
* The browser automatically starts at the login page for the institution’s learning management system<br />
* URLs cannot be typed by the user<br />
* External links don’t compromise the locked testing environment<br />
* Pages from the assessment are not stored on the computer after exiting<br />
<br />
* Assessments that are set up for use with LockDown Browser cannot be accessed with other browsers<br />
* Localized for multiple languages, including English, Spanish, French, German, Italian, and Portuguese<br />
* Available for both Windows and Mac computers, as well as iPad<br />
<br />
===Malware===<br />
LockDown requires administrative privileges to run, and cannot be run as an unprivileged user.<br />
Features of the browser could be construed to violate [http://www.vt.edu/about/acceptable-use.html Virginia Tech Acceptable Use Policy]<br />
by <em>engag[ing] in any activity that might be purposefully harmful to systems or to any information stored thereon...</em>, however<br />
its use is not widespread enough for this to gain any note.<br />
<br />
There is a further extension to Respondus LockDown, called Respondus Monitor<br />
<ref>http://respondus.com/products/monitor/</ref> that allows the proctor to spy on users through their webcam.<br />
<br />
==Running the Software==<br />
=== Download ===<br />
LockDown Browser's download website shows the download option based on your OS. Since it does not support Linux, it does not let you download it. So, to download this <s>shitty</s> browser, you need to change the OS in your User Agent to Windows.<br />
<br />
The file name must include the school's 9-digit ID code (for VT: 776344933). This must be immediately preceded by a '-' hyphen. If there are multiple numeric sequences '''exactly''' 9-digits long and preceded by a hyphen, the first one is interpreted as the ID code.<br />
<br />
The following file names would work:<br />
<br />
<code>LockDownBrowser-2-1-3-00-776344933.exe</code><br><br />
<code>LockDown-776344933-March-03-2025.exe</code><br><br />
<code>LD-03032025-776344933.exe</code><br><br />
<code>999999999-776344933-999999999.exe</code><br><br />
<code>LDB-0000000000-776344933-999999999.exe</code><br><br />
Note: the ID id is '''always''' the first 9 digit number with a hyphen in front. The .exe is optional.<br />
<br />
Likewise, the following file name would '''NOT''' work:<br />
<br />
<code>LockDownBrowser776344933.exe</code> This does not have a hyphen before the 9-digit code.<br><br />
<code>LockDown-030320251-776344933.exe</code>This has multiple 9-digit sequences, but the ID code is not first.<br><br />
<code>776344933.exe</code>The ID code is not preceded by a hyphen<br><br />
<code>Lockdown.exe</code>The ID code simply isn't in the file name<br><br />
<br />
To pull down VT's executable with the default name, try<br />
<code><br />
curl -LO $(curl -L "https://download.respondus.com/lockdown/$(curl -L "https://download.respondus.com/lockdown/download.php?ID=776344933" -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.3" 2>/dev/null | grep -ioE "download[0-9].php\?id=[0-9]*")" 2>/dev/null| grep -ioE "https.*.exe" | uniq)<br />
</code><br />
<br />
<br />
===Wine===<br />
There are multiple tutorials available by a quick web search which claim to get this working in Wine, <s>however, to date, no member of<br />
VTLUUG has succeeded in doing so and existing information indicates it varies by version of the browser.</s><br />
There is a solution for running LockDown browser with Wine, provided by [[User:caleb|caleb]] adapted from [https://www.reddit.com/r/UTEP/comments/1bkslgy/tutorial_running_lockdown_browser_on_linux/ this] Reddit post.<br />
<br />
This solution requires [https://github.com/Winetricks/winetricks winetricks]<br />
<br />
====IMPORTANT NOTE====<br />
While we here at VTLUUG promote the use of free software, many people at the university '''DO NOT'''. Follow these steps at your own risk, and '''ALWAYS''', ask your professor before using LockDown Browser in this ''unsupported'' configuration on an actual exam. Additionally, abusing flaws in Wine's compatibility in order to cheat or otherwise obtain an unfair advantage on exams is '''against the honor code'''. If cheating is your primary goal, there are certainly better ways if you do some research. If one person is caught abusing Wine to cheat on an exam, professors will not allow '''anyone''' to use it anymore, requiring '''everyone''' to use the non-free Windows operating system. If you are tempted to cheat on an exam, consider reaching out to your professor or TA and setting up office hours to discuss the exam.<br />
<br />
Additionally, if this method ever fails to work, ensure you have some kind of backup. Whether that is a Windows live-USB you can boot from on the day of the test, a second partition, or an entirely different device, '''bring it with you'''. Many courses provide test exams, which you can use to verify this still works a few hours in advance of the exam. The Chemistry department has a good one, and it is accessible as long as you have taken the course in a previous semester or are currently taking the course.<br />
<br />
====Step 1: Setup====<br />
First, install the following packages from your distributions package manager (names may differ):<br />
<br />
<code><br />
wine winetricks gnutls<br />
</code><br />
<br />
for Debian, the command is<br />
<br />
<pre><br />
# apt install wine gnutls-bin winetricks<br />
</pre><br />
Note that winetricks is only available in the <code>contrib</code> repository on vanilla Debian. Winetricks can be downloaded from their github as a bash script if enabling the contrib repository is not desired.<br />
<br />
====Step 2: Winetricks====<br />
Using winetricks, we can install all of the (non-free) fonts and msftedit, which is related to rich text edit controls.<ref>https://learn.microsoft.com/en-us/windows/win32/controls/about-rich-edit-controls</ref><br />
<br />
<pre><br />
$ winetricks msftedit allfonts<br />
</pre><br />
<br />
====Step 3: Install====<br />
Now simply run:<br />
<br />
<pre><br />
$ wine filename<br />
</pre><br />
<br />
replacing <code>filename</code> with the exact filename of the executable. If an error about the filename missing the 9-digit ID-code appears, ensure the file is [[#Download | properly named]]. After the program is installed, a .desktop file should automatically be created. Launching that file will load the LockDown Browser. Many features work on Gnome, such as detecting when switching desktops using a gesture or attempting to switch to another application. Other desktop environments and window managers have not been tested (yet).<br />
<br />
===Virtual Machine (KVM)===<br />
This refuses to run in a Virtual Machine. It may be possible to add the <code>-cpu kvm=off</code> flag to Qemu to prevent it from detecting a virtualized<br />
environment, but this has not been tested to date. It may also be necessary to disable Virtio drivers and devices.<br />
<br />
===Natively (Windows or OS X)===<br />
To run on Windows, the software requires administrative privileges. Previous versions were shown to have used Internet Explorer with certain modifications<br />
executed on the fly, to add the "Lock Down" features, however it currently appears to be a stand-alone browser with some resemblance to Google's Chrome. On both OS X and Windows, it is based off of the open-source Chromium<br />
<ref>http://respondus.com/products/lockdown-browser/requirements.shtml</ref>, although previous OS X versions are<br />
believed to have piggybacked off of Safari features. On Windows, the running user must have administrative privileges to run the student edition, however administrative privileges are not necessary to run the browser on OS X.<br />
<br />
A version for iOS (iPad-only) is also available, as well as a version for centrally managed Chromebooks for education (k-12).<br />
<br />
== Analysis ==<br />
Only cursory analysis has been done thus far, as the author of this article doesn't have a native windows box to run Respondus on. It appears that on launch, it first connects to an unencrypted http server running in AWS, presumably to check if the version is current, then it checks if it is in a virtualized environment.<br />
<br />
==Other Notes==<br />
===Actual Bugs===<br />
* No support for U2F -- requires second (expensive) device for other [[gp:2FA|2 Factor Authentication]] methods<br />
* Easily circumvented<br />
** Most students have second computer (i.e. Smartphone), which can be used for cheating (i.e. Google searching)<br />
** Circumvention methods disadvantage students of lower income, who do not have second device.<br />
* No Linux version, disadvantaging students promoting the use of <b>free software</b><br />
* Does not prevent collaboration in out-of-class testing<br />
* Superfluous for in-class testing, where students are visually monitored anyway<br />
** At most just promotes lazy proctoring of exams<br />
* Cannot take multiple tests within a single session<br />
* Requires administrative privileges which may not be available on multi-user machines<br />
* Hostile to users of password managers<br />
<br />
=== Open questions on debugging ===<br />
* Is a TLS cert chain bundled, or can it be MITMed?<br />
* What kind of protocol does it use to authenticate that it is respondus<br />
** A Kerberos-like protocol would be optimal, but I'd be surprised if they did it<br />
* Does the binary do any integrity checks?<br />
* Does qemu-only emulated devices adequately obfuscate that it runs in a VM? Doesn't seem to<br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Software]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Network&diff=8138Infrastructure:Network2025-03-02T02:29:06Z<p>Rsk: +scaryterry</p>
<hr />
<div>'''IF YOU CHANGE/ADD/REMOVE SOMETHING HERE CHANGE IT IN [[VTLUUG:Inventory|Inventory]] AND/OR [[Deprecated_Inventory]] TOO'''<br />
<br />
This page describes '''specifics''' about VTLUUG's '''current''' network. For an overview, see [[Infrastructure:Networking]]<br />
=== Addresses ===<br />
{| class="wikitable"<br />
!ECE DNS<br />
!VTLUUG DNS<br />
!IPv4<br />
!Private Internal IPv4<br />
!IPv6<br />
|-<br />
| luug.ece.vt.edu<br />
| [[Infrastructure:Sczi|sczi.vtluug.org]]<br />
| 128.173.88.78<br />
| 10.98.0.11<br />
| 2607:b400:6:cc80:0:aff:fe62:b<br />
|-<br />
| N/A<br />
| [[Infrastructure:Scaryterry|scaryterry.vtluug.org]]<br />
| 128.173.89.163<br />
| 10.98.0.22<br />
| 2607:b400:6:cc80:0:aff:fe62:f<br />
|-<br />
| luug0.ece.vt.edu<br />
| [[Infrastructure:Dirtycow|dirtycow.vtluug.org]]<br />
| 128.173.89.244<br />
| 10.98.0.7<br />
| 2607:b400:6:cc80:21e:c9ff:feef:13f8<br />
|-<br />
| luug1.ece.vt.edu<br />
| [[Infrastructure:Acidburn|acidburn.vtluug.org]]<br />
| 128.173.89.245 <br />
| 10.98.0.12<br />
| 2607:b400:6:cc80:0:aff:fe62:c<br />
|-<br />
| luug2.ece.vt.edu<br />
| [[Infrastructure:Meltdown|meltdown.vtluug.org]]<br />
| 128.173.89.246<br />
| 10.98.0.3<br />
| 2607:b400:6:cc80:0:aff:fe62:3<br />
|-<br />
| N/A<br />
| [[Infrastructure:Gibson|gibson.vtluug.org]]<br />
| 128.173.90.53<br />
| 10.98.0.8<br />
| 2607:b400:6:cc80:4a4d:7eff:fef9:8be5<br />
|-<br />
| luug3.ece.vt.edu<br />
| [[Infrastructure:Chimera|chimera.vtluug.org]]<br />
| 128.173.89.247<br />
| 10.98.0.10<br />
| 2607:b400:6:cc80:0:aff:fe62:a<br />
|-<br />
| N/A<br />
| [[Infrastructure:Chimera|sphinx.vtluug.org]]<br />
| 128.173.88.255<br />
| 10.98.0.20<br />
| 2607:b400:6:cc80:0:aff:fe62:d<br />
|-<br />
| luug4.ece.vt.edu<br />
| [[User:mjh|mjh.ece.vt.edu]]<br />
| 128.173.88.104<br />
| 10.98.0.254<br />
| 2607:b400:0006:cc80:0230:48ff:fe7e:28da<br />
|-<br />
| luug5.ece.vt.edu<br />
| [[Infrastructure:Shellshock|router.vtluug.org]]<br />
| 128.173.88.191<br />
| 10.98.0.1<br />
| 2001:468:c80:6103:211:43ff:fe30:a72<br />
|-<br />
| N/A<br />
| [[Infrastructure:Nikonwormhole|nikonwormhole.vtluug.org]]<br />
| 128.173.88.135<br />
| 10.98.0.21<br />
| 2607:b400:6:cc80:0:aff:fe62:e<br />
|-<br />
| mirror.ece.vt.edu<br />
| N/A *Not sure if we can actually use this IP*<br />
| 128.173.88.82<br />
| N/A<br />
| N/A<br />
|-<br />
| N/A<br />
| [[Infrastructure:Switch|switch.private.vtluug.org]] (Internal v4 only)<br />
| N/A<br />
| 10.98.0.2<br />
| N/A<br />
|-<br />
| N/A<br />
| [[Infrastructure:Spectre|spectre.vtluug.org]]<br />
| N/A<br />
| 10.98.0.4<br />
| 2607:b400:6:cc80:0:aff:fe62:4<br />
|-<br />
| N/A<br />
| [[Infrastructure:Cyberdelia|cyberdelia.vtluug.org]]<br />
| N/A<br />
| 10.98.0.6<br />
| 2607:b400:0006:cc80:0215:17ff:fe12:7670<br />
|}<br />
<br />
See [[Deprecated_Network]] for historical information.<br />
<br />
=== VTLUUG ===<br />
==== Addresses ====<br />
===== IPv6 =====<br />
* SLAAC on 2607:b400:0006:cc80::/64<br />
<br />
===== IPv4 =====<br />
* 10.98.0.0/16: internal NAT<br />
** Static IPs: 10.98.0.0/24<br />
** DHCP: 10.98.1.0 - 10.98.1.150<br />
** Iodine: 10.98.10.0/24<br />
* 128.173.88.1/22: publicly accessible hosts<br />
<br />
All hosts have an internal address (static or DHCP) and some hosts also have a globally accessible address.<br />
<br />
==== DNS ====<br />
[[Infrastructure:Shellshock|Shellshock]] also functions as DNS server for internal hosts<br />
* 10.99.0.1<br />
* 2607:b400:0006:cc80::1<br />
<br />
=== VT's DNS ===<br />
CNS maintains a few DNS servers on campus<br />
* yardbird.cns.vt.edu, 2001:468:c80:2101:0:100:0:22, 198.82.247.34<br />
* jeru.cns.vt.edu, 2001:468:c80:4101:0:100:0:42, 198.82.247.66<br />
* milo.cns.vt.edu, 2001:468:c80:6101:0:100:0:62, 198.82.247.98<br />
<br />
=== See Also ===<br />
* Contact [mailto:rbrand7@vt.edu Brandon Russell] to get authoritative DNS entries added for *.ece.vt.edu<br />
* [http://groupw.cns.vt.edu/~benchoff/cgi-bin/ipr-dump-wrapper.cgi?style=wwr network liasions]<br />
<br />
[[Category:Infrastructure]]</div>Rskhttps://vtluug.org/w/index.php?title=LockDown_Browser&diff=8137LockDown Browser2025-03-01T08:35:12Z<p>Rsk: Redirected page to Respondus LockDown Browser</p>
<hr />
<div>#REDIRECT [[Respondus_LockDown_Browser]]</div>Rskhttps://vtluug.org/w/index.php?title=Respondus_LockDown_Browser&diff=8136Respondus LockDown Browser2025-03-01T08:34:48Z<p>Rsk: </p>
<hr />
<div>Respondus LockDown Browser is a piece of proprietary online testing software developed by Respondus, Inc, and used by departments, including the Department<br />
of Engineering Education. Success in running under [[w:Wine (software)|Wine]] varies from version to version, and may involve complex installation procedures, and the software<br />
actively prevents itself from running in a<br />
[http://support.respondus.com/support/index.php?/Knowledgebase/Article/View/201/25/students-see-the-warning-the-browser-cant-be-used-in-virtual-machine-software-such-as-virtual-pc-vmware-and-parallels virtual machine].<br />
<br />
== Official Description ==<br />
<br />
From the [http://respondus.com/products/lockdown-browser/index.shtml Product page]:<br />
<br />
<em>LockDown Browser® is a custom browser that locks down the testing environment within Blackboard, ANGEL, Brightspace by D2L, Canvas, Moodle, and Sakai. When students use LockDown Browser they are unable to print, copy, go to another URL, or access other applications. When an assessment is started, students are locked into it until they submit it for grading. Available for Windows, Mac and iOS [sic].</em><br />
<br />
=== <s> Features </s> Bugs ===<br />
<br />
* Integrates with Blackboard, ANGEL, Brightspace by D2L, Canvas, Moodle, and Sakai<br />
* Assessments are displayed full-screen and cannot be minimized<br />
* Assessments cannot be exited until submitted by users for grading<br />
<br />
* Task switching or access to other applications is prevented<br />
* Print, Print Screen and capturing functions are disabled<br />
* Copying and pasting anything to and from an assessment is prohibited<br />
* Screen capture, messaging, screen-sharing, virtual machine, and network monitoring applications are blocked from running<br />
* Right-click menu options and function keys are disabled<br />
* Browser menu and toolbar options are disabled, except for Back, Forward, Refresh and Stop<br />
<br />
* Source code for the HTML page cannot be viewed<br />
* The browser automatically starts at the login page for the institution’s learning management system<br />
* URLs cannot be typed by the user<br />
* External links don’t compromise the locked testing environment<br />
* Pages from the assessment are not stored on the computer after exiting<br />
<br />
* Assessments that are set up for use with LockDown Browser cannot be accessed with other browsers<br />
* Localized for multiple languages, including English, Spanish, French, German, Italian, and Portuguese<br />
* Available for both Windows and Mac computers, as well as iPad<br />
<br />
===Malware===<br />
LockDown requires administrative privileges to run, and cannot be run as an unprivileged user.<br />
Features of the browser could be construed to violate [http://www.vt.edu/about/acceptable-use.html Virginia Tech Acceptable Use Policy]<br />
by <em>engag[ing] in any activity that might be purposefully harmful to systems or to any information stored thereon...</em>, however<br />
its use is not widespread enough for this to gain any note.<br />
<br />
There is a further extension to Respondus LockDown, called Respondus Monitor<br />
<ref>http://respondus.com/products/monitor/</ref> that allows the proctor to spy on users through their webcam.<br />
<br />
==Running the Software==<br />
=== Download ===<br />
LockDown Browser's download website shows the download option based on your OS. Since it does not support Linux, it does not let you download it. So, to download this <s>shitty</s> browser, you need to change the OS in your User Agent to Windows.<br />
<br />
After you download it, DO NOT change the name of the file. LockDown Browser uses the file as an ID for the browser. It will not work <br />
if you change it to a non-valid ID.<br />
<br />
===Wine===<br />
There are multiple tutorials available by a quick web search which claim to get this working in Wine, <s>however, to date, no member of<br />
VTLUUG has succeeded in doing so and existing information indicates it varies by version of the browser.</s><br />
This is a solution for running LockDown browser with Wine, provided by [[User:caleb|caleb]].<br />
<br />
This solution requires [https://github.com/Winetricks/winetricks winetricks]<br />
<pre><br />
winetricks msftedit allfonts<br />
</pre><br />
<br />
<br />
===Virtual Machine (KVM)===<br />
This refuses to run in a Virtual Machine. It may be possible to add the <code>-cpu kvm=off</code> flag to Qemu to prevent it from detecting a virtualized<br />
environment, but this has not been tested to date. It may also be necessary to disable Virtio drivers and devices.<br />
<br />
===Natively (Windows or OS X)===<br />
To run on Windows, the software requires administrative privileges. Previous versions were shown to have used Internet Explorer with certain modifications<br />
executed on the fly, to add the "Lock Down" features, however it currently appears to be a stand-alone browser with some resemblance to Google's Chrome. On both OS X and Windows, it is based off of the open-source Chromium<br />
<ref>http://respondus.com/products/lockdown-browser/requirements.shtml</ref>, although previous OS X versions are<br />
believed to have piggybacked off of Safari features. On Windows, the running user must have administrative privileges to run the student edition, however administrative privileges are not necessary to run the browser on OS X.<br />
<br />
A version for iOS (iPad-only) is also available, as well as a version for centrally managed Chromebooks for education (k-12).<br />
<br />
== Analysis ==<br />
Only cursory analysis has been done thus far, as the author of this article doesn't have a native windows box to run Respondus on. It appears that on launch, it first connects to an unencrypted http server running in AWS, presumably to check if the version is current, then it checks if it is in a virtualized environment.<br />
<br />
==Other Notes==<br />
===Actual Bugs===<br />
* No support for U2F -- requires second (expensive) device for other [[gp:2FA|2 Factor Authentication]] methods<br />
* Easily circumvented<br />
** Most students have second computer (i.e. Smartphone), which can be used for cheating (i.e. Google searching)<br />
** Circumvention methods disadvantage students of lower income, who do not have second device.<br />
* No Linux version, disadvantaging students promoting the use of <b>free software</b><br />
* Does not prevent collaboration in out-of-class testing<br />
* Superfluous for in-class testing, where students are visually monitored anyway<br />
** At most just promotes lazy proctoring of exams<br />
* Cannot take multiple tests within a single session<br />
* Requires administrative privileges which may not be available on multi-user machines<br />
* Hostile to users of password managers<br />
<br />
=== Open questions on debugging ===<br />
* Is a TLS cert chain bundled, or can it be MITMed?<br />
* What kind of protocol does it use to authenticate that it is respondus<br />
** A Kerberos-like protocol would be optimal, but I'd be surprised if they did it<br />
* Does the binary do any integrity checks?<br />
* Does qemu-only emulated devices adequately obfuscate that it runs in a VM? Doesn't seem to<br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Software]]</div>Rskhttps://vtluug.org/w/index.php?title=Skid_invasion&diff=8135Skid invasion2025-03-01T08:32:06Z<p>Rsk: Redirected page to Minecraft#Skid Invasion</p>
<hr />
<div>#REDIRECT [[Minecraft#Skid_Invasion]]</div>Rskhttps://vtluug.org/w/index.php?title=Vtluugsmp&diff=8134Vtluugsmp2025-03-01T08:31:31Z<p>Rsk: Redirected page to Minecraft</p>
<hr />
<div>#REDIRECT [[Minecraft]]</div>Rskhttps://vtluug.org/w/index.php?title=Minecraft&diff=8133Minecraft2025-03-01T08:31:21Z<p>Rsk: Created page with "Minecraft is a block game beloved by many. It is neither open-source nor libre, but due to the easily-decompiled nature of java bytecode (and leaked debug symbols), its commun..."</p>
<hr />
<div>Minecraft is a block game beloved by many. It is neither open-source nor libre, but due to the easily-decompiled nature of java bytecode (and leaked debug symbols), its community treats it as if it were source-available.<br />
<br />
<br />
VTLUUG hosts a minecraft server courtesy of [[User:Localhunter]], under the name 'VTLUUGsmp'.<br />
<br />
<br />
= VTLUUGsmp =<br />
VTLUUGsmp is a Minecraft server hosted by VTLUUG, at minecraft.vtluug.org -- 'SMP' stands for survival multiplayer. It is whitelist only, with a whitelist managed by [[user:localhunter|localhunter]]: email him if you want on the whitelist. <br />
<br />
== Rules ==<br />
1. No hacked clients (shit like optifine & sodium is fine) <br><br />
2. No griefing people you aren't at war with <br><br />
3. If you want to start a war with someone, everyone in every group involved has to agree to start a war.<br><br />
4. When you want to stop a war, every group involved has to be in favor of it. If your enemy surrenders, you have to negotiate on terms of surrender together and both agree on<br />
them. Violating terms of surrender is grounds to start a second war.<br><br />
5. No lag machines or shit that bans other players, shit like that<br><br />
6. No doxxing<br><br />
7. No stealing from people you aren't at war with<br><br />
8. No windows apologists <br><br />
<br />
== Skid Invasion ==<br />
<br />
The Skid Invasion of '25 was an incident when a [https://en.wikipedia.org/wiki/Script_kiddie skid] "invaded" the [[vtluugsmp]] and did very minor damage. The whitelist was shortly implemented after the invasion.<br />
<br />
=== Statistics ===<br />
Duration of invasion: 4 minutes<br />
Causes: not having a whitelist<br />
Participants: [[user:localhunter|localhunter]], the skids.<br />
Casualties: A Wither, Hunter's time.<br />
<br />
=== Aftermath ===<br />
The vtluugsmp enabled a whitelist, and Hunter lost some armor<br />
<br />
<br />
[[Category:VTLUUG:Projects]]<br />
[[Category:Services]]<br />
[[Category:Software]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Sysadmin_Handbook&diff=8102Infrastructure:Sysadmin Handbook2025-02-17T17:59:54Z<p>Rsk: </p>
<hr />
<div>This page describes how to manage the infra. See [https://vtluug.github.io/rtfm.txt rtfm.txt] for a guide to build it from scratch.<br />
<br />
This covers setup of a VM on [[Infrastructure:Meltdown|meltdown]] or [[Infrastructure:Spectre|spectre]] depending on if the service is critical or not.<br />
<br />
== Infodump (i will clean this up later, promise) ==<br />
<br />
LUUG infrastructure runs on, essentially, four key components:<br />
* Hosts<br />
* NFS<br />
* Auth<br />
and<br />
* out-of-band Ansible & Docker manifests<br />
<br />
Almost all of our services are hosted in Docker containers across various hosts: on [[Infrastructure:Gibson]], the LLM server, on [[Infrastructure:Sczi]] the web content. 100% of these docker containers have their configuration detailed [https://github.com/vtluug/docker-manifests here].<br />
<br />
The entire repository is cloned to /nfs/cistern/docker/apps, and the docker-compose.yml files for each service are ran with the command 'docker compose up -d' while in the service folder.<br />
<br />
Note the path: /nfs/cistern/docker/apps. Looking at the docker-compose folders & configs, you will notice that the *data* for the container is **never** stored alongside the compose files themselves. Instead, they are stored at /nfs/cistern/docker/data/<insert-service-name>/<etc>. This is an NFS (Network File System) mounted path: it exists physically on our NFS server, [[Infrastructure:Dirtycow]] and is mounted over the local network.<br />
<br />
The implications of this should be clear: *the host install does not actually matter*. If the operating system for e.g. [[Infrastructure:Sczi]] blew up, all one would need to do to bring everything back up is re-create it, install docker, mount the cistern NFS directory (with the date files still intact), set up auth, and start all the containers again. No data is ever lost, because nothing is stored on the host itself: it's all on the NFS share.<br />
<br />
How do you easily set all that stuff back up again? [https://github.com/vtluug/ansible Ansible]. you can think of ansible as a language designed for defining deployed servers. It uses YAML (.yml), and "roles" are specified for each server. in roles/<server role>/tasks, there exists a list of things needed to set up the server, and in /hosts.cfg there exists a list of servers and which roles they all have. All you need to do to set a server up is run ansible -- it will take care of the rest. You can run it twice, or a million times, to no ill effect: it's designed to be idempotent.<br />
<br />
Knowing this much, you can re-create [[Infrastructure:Sczi]] and [[Infrastructure:Gibson]], but there are a few remaining things: VM hosts ([[Infrastructure:Meltdown]], [[Infrastructure:Spectre]]), and the router ([[Infrastructure:Shellshock]]). Deploying the router is described in [https://vtluug.org/rtfm.txt rtfm.txt], but VM deployment is entirely automated via ansible, which is *sick as fuck*. It only works for ubuntu server and redhat enterprise (alma, rocky, centos) distros, but for those it works brilliantly -- add a VM to [https://github.com/vtluug/ansible/blob/master/roles/deploy-vms/defaults/main.yml this file] and run the ansible playbook -- the new VM will automagically create.<br />
<br />
Web traffic!<br />
We run DNS through Gandi. Ask an officer to add you to the VTLUUG org on that website ([[User:Rsk]] has access, if you're reading this in the far future and need it).<br />
Each host gets a direct A record pointing at it's IP address, and web content *all* points to [[Infrastructure:Sczi]] via CNAME records. Sczi's docker config has an nginx container that handles certificates and reverse proxying.<br />
<br />
Acidburn is our singular "traditionally managed" server. It runs many services, mail among them, and all are running as services on the VM itself, not a container in sight (sans the IRC <-> Matrix bridge, which is there for IP whitelisting reasons. You can redeploy it from ansible, but it won't have the same soul. Try not to break it.<br />
<br />
Auth<br />
We run two Authentication servers, [[Infrastructure:Chimera]] and [[Infrastructure:Sphinx]]. They're both on the same FreeIPA network and can be deployed via ansible.<br />
<br />
FreeIPA is a full-stack authentication provider. Part of our ansible playbook for LUUG hosts runs ipa-client-install, which sets up the hosts as "clients" to this FreeIPA network, and allows users with FreeIPA accounts to log in via ssh, reflecting usergroups over on to the system.<br />
<br />
[[Infrastructure:Spectre]] notably is *not* a FreeIPA client, because it's intended for use by non-LUUG entities (whether that be personal member VMs or ones loaned out to other student orgs).<br />
<br />
The root account password is in the [https://git.vtluug.org/officers/vtluug-admin vtluug-admin] private repository. Ask someone to be added to the officers group.<br />
<br />
<br />
== Networks ==<br />
''Further information: [[Infrastructure:Network|Network]]<br />
<br />
We ''should'' have the following networks in place:<br />
<br />
* [[Infrastructure:Meltdown|meltdown]] and [[Infrastructure:Spectre|spectre]] br0 on eno1 <--> enp4s0 on [[Infrastructure:Joey|joey]]. This is the main LUUG network.<br />
** 10.98.0.0/16 for VTLUUG NAT<br />
** IPv6 via prefix delegation on 607:b400:6:cc80/64<br />
** Global IPv4s via ARP proxying (See https://github.com/vtluug/scripts). Gateway is 128.173.88.1/22.<br />
* Static hosts are on 10.98.0.0/24, and DHCP is enabled on 10.98.1.0/24. This is mainly just useful for organization and quickly finding new hosts or other hosts on the network.<br />
** Static host IPs are assigned via static DHCP leases for IPv4.<br />
** Since we can't do this with IPv6, physical host IPs are determined upon first boot and VMs are assigned a specific MAC to pre-determine the SLAAC IP.<br />
* "Internet" (a CNS portal) <--> enp2s0 on [[Infrastructure:Joey|joey]]. LUUG only has one of these, and port security is probably enabled.<br />
<br />
'''DNS/DHCP:'''<br />
* All DNS entries for services run by VTLUUG are hosted on [https://gandi.net Gandi]. Ask an officer if you want to change something.<br />
* jkh and Roddy own ece.vt.edu. DNS updates don't happen. echarlie can add IPv6-only records if needed to wuvt.vt.edu so we have PTRs.<br />
* [[Infrastructure:Joey|joey]] runs DHCP via dnsmasq on enp4s0 (that is, 10.98.0.0/16). To change anything, modify it on https://github.com/vtluug/scripts first then pull that into root's homedir on [[Infrastructure:Joey|joey]]. Please don't just update it on a machine without pushing your updates.<br />
* By default, hosts are accessible via SSH on ports 22 and 2222.<br />
<br />
== Adding a VTLUUG Service VM ==<br />
''VMs in this category are deployed to [[Infrastructure:Meltdown|meltdown]]''<br />
<br />
Prerequisites:<br />
* Clone <code>https://github.com/vtluug/scripts</code>. This is referred to as 'SCRIPTS' in this guide.<br />
* Clone <code>https://github.com/vtluug/ansible</code> and install ansible. This repo is referred to as 'ANSIBLE' in this guide.<br />
* Have access to [https://git.vtluug.org/officers/vtluug-admin officers/vtluug-admin] on [https://git.vtluug.org gitea].<br />
* Understand the [[Infrastructure:Network|Network]] and [[Infrastructure]].<br />
* Put your SSH key on [[Infrastructure:Meltdown|meltdown]]<br />
<br />
=== Configure the network ===<br />
* Decide on a MAC address for the host and add it to <code>SCRIPTS/router/lan/local_hosts</code><br />
* Add an entry to <code>SCRIPTS/router/lan/dnsmasq.conf</code> for static DHCP leases.<br />
* If a new IP in 128.173.88.1/22 is being added, also add it to <code>SCRIPTS/router/proxy/arp_proxy.sh</code><br />
<br />
'''Note:''' It is '''not''' recommended that you do the following steps if nobody is on campus in case something breaks.<br />
<br />
Pull the latest changes to <code>/root/scripts</code>, update the configuration files, and restart the services:<br />
* Dnsmasq configuration is at <code>/etc/dnsmasq.conf</code><br />
* ARP Proxy configuration is in <code>/usr/local/bin</code><br />
<br />
=== Add the VM configuration to ansible ===<br />
Edit <code>ANSIBLE_PATH/roles/deploy-vms/defaults/main.yml</code> and add a new entry, following the existing format.<br />
<br />
'''Note:''' if there are any entries in this file that are '''not''' present on the VM host, they will also be created. Comment out entries that shouldn't be created. Existing hosts are skipped.<br />
<br />
Run <code>ansible-playbook -v deploy.yml -i hosts.cfg -u papatux -k -K -e @VTLUUG_ADMIN_REPO/accounts.yml</code>, using the correct vtluug-admin repo path.<br />
<br />
=== Testing ===<br />
The new host should be accessible by papatux on via SSH port 2222 (and 22) over IPv6 and IPv4 from the internal network. Check 10.98.1.0/24 to see if it had any issues getting a static DHCP lease and if the MAC is correct.<br />
<br />
== Adding a User VM ==<br />
''VMs in this category are deployed to [[Infrastructure:Spectre|spectre]]''<br />
<br />
Prerequisites:<br />
* Clone <code>https://github.com/vtluug/scripts</code>. This is referred to as 'SCRIPTS' in this guide.<br />
* Clone <code>https://github.com/vtluug/ansible</code> and install ansible. This repo is referred to as 'ANSIBLE' in this guide.<br />
* Understand the [[Infrastructure:Network|Network]] and [[Infrastructure]].<br />
* Have root on [[Infrastructure:Spectre|spectre]]<br />
* Put your SSH key on [[Infrastructure:Spectre|spectre]]<br />
<br />
=== Configure the network ===<br />
* Decide on a MAC address for the host and add it to <code>SCRIPTS/router/lan/local_hosts</code><br />
* Add an entry to <code>SCRIPTS/router/lan/dnsmasq.conf</code> for static DHCP leases. (If applicable; you might not care for a test/temp VM).<br />
<br />
'''Note:''' It is '''not''' recommended that you do the following steps if nobody is on campus in case something breaks.<br />
<br />
Pull the latest changes to <code>/root/scripts</code>, update the configuration files, and restart the services:<br />
* Dnsmasq configuration is at <code>/etc/dnsmasq.conf</code><br />
<br />
=== Add the VM configuration to ansible ===<br />
Edit <code>ANSIBLE_PATH/roles/deploy-vms/defaults/main.yml</code> and add a new entry under <code>new_vms_spectre</code>, following the existing format.<br />
<br />
'''Note:''' if there are any entries in this file that are '''not''' present on the VM host, they will also be created. Comment out entries that shouldn't be created. Existing hosts are skipped.<br />
<br />
Run <code>ansible-playbook -v deploy.yml -i hosts.cfg -u papatux -k -K</code>, using the correct vtluug-admin repo path.<br />
<br />
'''Important:''' A random root password is set during VM creation and printed to stdout. Record this!<br />
<br />
=== Testing ===<br />
The new host should be accessible by root on via SSH port 2222 (and 22) over IPv6 and IPv4 from the internal network. Check 10.98.1.0/24 to see if it had any issues getting a static DHCP lease and if the MAC is correct.<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Howtos]]<br />
[[Category:Needs restoration]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Sysadmin_Handbook&diff=8100Infrastructure:Sysadmin Handbook2025-02-17T17:54:22Z<p>Rsk: </p>
<hr />
<div>This page describes how to manage the infra. See [https://vtluug.github.io/rtfm.txt rtfm.txt] for a guide to build it from scratch.<br />
<br />
This covers setup of a VM on [[Infrastructure:Meltdown|meltdown]] or [[Infrastructure:Spectre|spectre]] depending on if the service is critical or not.<br />
<br />
== Infodump (i will clean this up later, promise ==<br />
<br />
LUUG infrastructure runs on, essentially, four key components:<br />
* Hosts<br />
* NFS<br />
* Auth<br />
and<br />
* out-of-band Ansible & Docker manifests<br />
<br />
Almost all of our services are hosted in Docker containers across various hosts: on [[Infrastructure:Gibson]], the LLM server, on [[Infrastructure:Sczi]] the web content. 100% of these docker containers have their configuration detailed [https://github.com/vtluug/docker-manifests here].<br />
<br />
The entire repository is cloned to /nfs/cistern/docker/apps, and the docker-compose.yml files for each service are ran with the command 'docker compose up -d' while in the service folder.<br />
<br />
Note the path: /nfs/cistern/docker/apps. Looking at the docker-compose folders & configs, you will notice that the *data* for the container is **never** stored alongside the compose files themselves. Instead, they are stored at /nfs/cistern/docker/data/<insert-service-name>/<etc>. This is an NFS (Network File System) mounted path: it exists physically on our NFS server, [[Infrastructure:Dirtycow]] and is mounted over the local network.<br />
<br />
The implications of this should be clear: *the host install does not actually matter*. If the operating system for e.g. [[Infrastructure:Sczi]] blew up, all one would need to do to bring everything back up is re-create it, install docker, mount the cistern NFS directory (with the date files still intact), set up auth, and start all the containers again. No data is ever lost, because nothing is stored on the host itself: it's all on the NFS share.<br />
<br />
How do you easily set all that stuff back up again? [https://github.com/vtluug/ansible Ansible]. you can think of ansible as a language designed for defining deployed servers. It uses YAML (.yml), and "roles" are specified for each server. in roles/<server role>/tasks, there exists a list of things needed to set up the server, and in /hosts.cfg there exists a list of servers and which roles they all have. All you need to do to set a server up is run ansible -- it will take care of the rest. You can run it twice, or a million times, to no ill effect: it's designed to be idempotent.<br />
<br />
Knowing this much, you can re-create [[Infrastructure:Sczi]] and [[Infrastructure:Gibson]], but there are a few remaining things: VM hosts ([[Infrastructure:Meltdown]], [[Infrastructure:Spectre]]), and the router ([[Infrastructure:Shellshock]]). Deploying the router is described in [https://vtluug.org/rtfm.txt rtfm.txt], but VM deployment is entirely automated via ansible, which is *sick as fuck*. It only works for ubuntu server and redhat enterprise (alma, rocky, centos) distros, but for those it works brilliantly -- add a VM to [https://github.com/vtluug/ansible/blob/master/roles/deploy-vms/defaults/main.yml this file] and run the ansible playbook -- the new VM will automagically create.<br />
<br />
Web traffic!<br />
We run DNS through Gandi. Ask an officer to add you to the VTLUUG org on that website ([[User:Rsk]] has access, if you're reading this in the far future and need it).<br />
Each host gets a direct A record pointing at it's IP address, and web content *all* points to [[Infrastructure:Sczi]] via CNAME records. Sczi's docker config has an nginx container that handles certificates and reverse proxying.<br />
<br />
Acidburn is our singular "traditionally managed" server. It runs many services, mail among them, and all are running as services on the VM itself, not a container in sight (sans the IRC <-> Matrix bridge, which is there for IP whitelisting reasons. You can redeploy it from ansible, but it won't have the same soul. Try not to break it.<br />
<br />
Auth<br />
We run two Authentication servers, [[Infrastructure:Chimera]] and [[Infrastructure:Sphinx]]. They're both on the same FreeIPA network and can be deployed via ansible.<br />
<br />
FreeIPA is a full-stack authentication provider. Part of our ansible playbook for LUUG hosts runs ipa-client-install, which sets up the hosts as "clients" to this FreeIPA network, and allows users with FreeIPA accounts to log in via ssh, reflecting usergroups over on to the system.<br />
<br />
[[Infrastructure:Spectre]] notably is *not* a FreeIPA client, because it's intended for use by non-LUUG entities (whether that be personal member VMs or ones loaned out to other student orgs).<br />
<br />
<br />
== Networks ==<br />
''Further information: [[Infrastructure:Network|Network]]<br />
<br />
We ''should'' have the following networks in place:<br />
<br />
* [[Infrastructure:Meltdown|meltdown]] and [[Infrastructure:Spectre|spectre]] br0 on eno1 <--> enp4s0 on [[Infrastructure:Joey|joey]]. This is the main LUUG network.<br />
** 10.98.0.0/16 for VTLUUG NAT<br />
** IPv6 via prefix delegation on 607:b400:6:cc80/64<br />
** Global IPv4s via ARP proxying (See https://github.com/vtluug/scripts). Gateway is 128.173.88.1/22.<br />
* Static hosts are on 10.98.0.0/24, and DHCP is enabled on 10.98.1.0/24. This is mainly just useful for organization and quickly finding new hosts or other hosts on the network.<br />
** Static host IPs are assigned via static DHCP leases for IPv4.<br />
** Since we can't do this with IPv6, physical host IPs are determined upon first boot and VMs are assigned a specific MAC to pre-determine the SLAAC IP.<br />
* "Internet" (a CNS portal) <--> enp2s0 on [[Infrastructure:Joey|joey]]. LUUG only has one of these, and port security is probably enabled.<br />
<br />
'''DNS/DHCP:'''<br />
* All DNS entries for services run by VTLUUG are hosted on [https://gandi.net Gandi]. Ask an officer if you want to change something.<br />
* jkh and Roddy own ece.vt.edu. DNS updates don't happen. echarlie can add IPv6-only records if needed to wuvt.vt.edu so we have PTRs.<br />
* [[Infrastructure:Joey|joey]] runs DHCP via dnsmasq on enp4s0 (that is, 10.98.0.0/16). To change anything, modify it on https://github.com/vtluug/scripts first then pull that into root's homedir on [[Infrastructure:Joey|joey]]. Please don't just update it on a machine without pushing your updates.<br />
* By default, hosts are accessible via SSH on ports 22 and 2222.<br />
<br />
== Adding a VTLUUG Service VM ==<br />
''VMs in this category are deployed to [[Infrastructure:Meltdown|meltdown]]''<br />
<br />
Prerequisites:<br />
* Clone <code>https://github.com/vtluug/scripts</code>. This is referred to as 'SCRIPTS' in this guide.<br />
* Clone <code>https://github.com/vtluug/ansible</code> and install ansible. This repo is referred to as 'ANSIBLE' in this guide.<br />
* Have access to [https://git.vtluug.org/officers/vtluug-admin officers/vtluug-admin] on [https://git.vtluug.org gitea].<br />
* Understand the [[Infrastructure:Network|Network]] and [[Infrastructure]].<br />
* Put your SSH key on [[Infrastructure:Meltdown|meltdown]]<br />
<br />
=== Configure the network ===<br />
* Decide on a MAC address for the host and add it to <code>SCRIPTS/router/lan/local_hosts</code><br />
* Add an entry to <code>SCRIPTS/router/lan/dnsmasq.conf</code> for static DHCP leases.<br />
* If a new IP in 128.173.88.1/22 is being added, also add it to <code>SCRIPTS/router/proxy/arp_proxy.sh</code><br />
<br />
'''Note:''' It is '''not''' recommended that you do the following steps if nobody is on campus in case something breaks.<br />
<br />
Pull the latest changes to <code>/root/scripts</code>, update the configuration files, and restart the services:<br />
* Dnsmasq configuration is at <code>/etc/dnsmasq.conf</code><br />
* ARP Proxy configuration is in <code>/usr/local/bin</code><br />
<br />
=== Add the VM configuration to ansible ===<br />
Edit <code>ANSIBLE_PATH/roles/deploy-vms/defaults/main.yml</code> and add a new entry, following the existing format.<br />
<br />
'''Note:''' if there are any entries in this file that are '''not''' present on the VM host, they will also be created. Comment out entries that shouldn't be created. Existing hosts are skipped.<br />
<br />
Run <code>ansible-playbook -v deploy.yml -i hosts.cfg -u papatux -k -K -e @VTLUUG_ADMIN_REPO/accounts.yml</code>, using the correct vtluug-admin repo path.<br />
<br />
=== Testing ===<br />
The new host should be accessible by papatux on via SSH port 2222 (and 22) over IPv6 and IPv4 from the internal network. Check 10.98.1.0/24 to see if it had any issues getting a static DHCP lease and if the MAC is correct.<br />
<br />
== Adding a User VM ==<br />
''VMs in this category are deployed to [[Infrastructure:Spectre|spectre]]''<br />
<br />
Prerequisites:<br />
* Clone <code>https://github.com/vtluug/scripts</code>. This is referred to as 'SCRIPTS' in this guide.<br />
* Clone <code>https://github.com/vtluug/ansible</code> and install ansible. This repo is referred to as 'ANSIBLE' in this guide.<br />
* Understand the [[Infrastructure:Network|Network]] and [[Infrastructure]].<br />
* Have root on [[Infrastructure:Spectre|spectre]]<br />
* Put your SSH key on [[Infrastructure:Spectre|spectre]]<br />
<br />
=== Configure the network ===<br />
* Decide on a MAC address for the host and add it to <code>SCRIPTS/router/lan/local_hosts</code><br />
* Add an entry to <code>SCRIPTS/router/lan/dnsmasq.conf</code> for static DHCP leases. (If applicable; you might not care for a test/temp VM).<br />
<br />
'''Note:''' It is '''not''' recommended that you do the following steps if nobody is on campus in case something breaks.<br />
<br />
Pull the latest changes to <code>/root/scripts</code>, update the configuration files, and restart the services:<br />
* Dnsmasq configuration is at <code>/etc/dnsmasq.conf</code><br />
<br />
=== Add the VM configuration to ansible ===<br />
Edit <code>ANSIBLE_PATH/roles/deploy-vms/defaults/main.yml</code> and add a new entry under <code>new_vms_spectre</code>, following the existing format.<br />
<br />
'''Note:''' if there are any entries in this file that are '''not''' present on the VM host, they will also be created. Comment out entries that shouldn't be created. Existing hosts are skipped.<br />
<br />
Run <code>ansible-playbook -v deploy.yml -i hosts.cfg -u papatux -k -K</code>, using the correct vtluug-admin repo path.<br />
<br />
'''Important:''' A random root password is set during VM creation and printed to stdout. Record this!<br />
<br />
=== Testing ===<br />
The new host should be accessible by root on via SSH port 2222 (and 22) over IPv6 and IPv4 from the internal network. Check 10.98.1.0/24 to see if it had any issues getting a static DHCP lease and if the MAC is correct.<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Howtos]]<br />
[[Category:Needs restoration]]</div>Rskhttps://vtluug.org/w/index.php?title=Infrastructure:Sysadmin_Handbook&diff=8099Infrastructure:Sysadmin Handbook2025-02-17T17:50:18Z<p>Rsk: infodump</p>
<hr />
<div>This page describes how to manage the infra. See [https://vtluug.github.io/rtfm.txt rtfm.txt] for a guide to build it from scratch.<br />
<br />
This covers setup of a VM on [[Infrastructure:Meltdown|meltdown]] or [[Infrastructure:Spectre|spectre]] depending on if the service is critical or not.<br />
<br />
== Infodump (i will clean this up later, promise ==<br />
<br />
LUUG infrastructure runs on, essentially, four key components:<br />
* Hosts<br />
* NFS<br />
* Auth<br />
and<br />
* out-of-band Ansible & Docker manifests<br />
<br />
Almost all of our services are hosted in Docker containers across various hosts: on [[Infrastructure:Gibson]], the LLM server, on [[Infrastructure:Sczi]] the web content. 100% of these docker containers have their configuration detailed [https://github.com/vtluug/docker-manifests here].<br />
<br />
The entire repository is cloned to /nfs/cistern/docker/apps, and the docker-compose.yml files for each service are ran with the command 'docker compose up -d' while in the service folder.<br />
<br />
Note the path: /nfs/cistern/docker/apps. Looking at the docker-compose folders & configs, you will notice that the *data* for the container is **never** stored alongside the compose files themselves. Instead, they are stored at /nfs/cistern/docker/data/<insert-service-name>/<etc>. This is an NFS (Network File System) mounted path: it exists physically on our NFS server, [[Infrastructure:Dirtycow]] and is mounted over the local network.<br />
<br />
The implications of this should be clear: *the host install does not actually matter*. If the operating system for e.g. [[Infrastructure:Sczi]] blew up, all one would need to do to bring everything back up is re-create it, install docker, mount the cistern NFS directory (with the date files still intact), set up auth, and start all the containers again. No data is ever lost, because nothing is stored on the host itself: it's all on the NFS share.<br />
<br />
How do you easily set all that stuff back up again? [https://github.com/vtluug/ansible Ansible]. you can think of ansible as a language designed for defining deployed servers. It uses YAML (.yml), and "roles" are specified for each server. in roles/<server role>/tasks, there exists a list of things needed to set up the server, and in /hosts.cfg there exists a list of servers and which roles they all have. All you need to do to set a server up is run ansible -- it will take care of the rest. You can run it twice, or a million times, to no ill effect: it's designed to be idempotent.<br />
<br />
Knowing this much, you can re-create [[Infrastructure:Sczi]] and [[Infrastructure:Gibson]], but there are a few remaining things: VM hosts ([[Infrastructure:Meltdown]], [[Infrastructure:Spectre]]), and the router ([[Infrastructure:Shellshock]]). Deploying the router is described in [https://vtluug.org/rtfm.txt rtfm.txt], but VM deployment is entirely automated via ansible, which is *sick as fuck*. It only works for ubuntu server and redhat enterprise (alma, rocky, centos) distros, but for those it works brilliantly -- add a VM to [https://github.com/vtluug/ansible/blob/master/roles/deploy-vms/defaults/main.yml this file] and run the ansible playbook -- the new VM will automagically create.<br />
<br />
Web traffic!<br />
We run DNS through Gandi. Ask an officer to add you to the VTLUUG org on that website ([[User:Rsk]] has access, if you're reading this in the far future and need it).<br />
Each host gets a direct A record pointing at it's IP address, and web content *all* points to [[Infrastructure:Sczi]] via CNAME records. Sczi's docker config has an nginx container that handles certificates and reverse proxying.<br />
<br />
Acidburn is our singular "traditionally managed" server. It runs many services, mail among them, and all are running as services on the VM itself, not a container in sight (sans the IRC <-> Matrix bridge, which is there for IP whitelisting reasons. You can redeploy it from ansible, but it won't have the same soul. Try not to break it.<br />
<br />
<br />
== Networks ==<br />
''Further information: [[Infrastructure:Network|Network]]<br />
<br />
We ''should'' have the following networks in place:<br />
<br />
* [[Infrastructure:Meltdown|meltdown]] and [[Infrastructure:Spectre|spectre]] br0 on eno1 <--> enp4s0 on [[Infrastructure:Joey|joey]]. This is the main LUUG network.<br />
** 10.98.0.0/16 for VTLUUG NAT<br />
** IPv6 via prefix delegation on 607:b400:6:cc80/64<br />
** Global IPv4s via ARP proxying (See https://github.com/vtluug/scripts). Gateway is 128.173.88.1/22.<br />
* Static hosts are on 10.98.0.0/24, and DHCP is enabled on 10.98.1.0/24. This is mainly just useful for organization and quickly finding new hosts or other hosts on the network.<br />
** Static host IPs are assigned via static DHCP leases for IPv4.<br />
** Since we can't do this with IPv6, physical host IPs are determined upon first boot and VMs are assigned a specific MAC to pre-determine the SLAAC IP.<br />
* "Internet" (a CNS portal) <--> enp2s0 on [[Infrastructure:Joey|joey]]. LUUG only has one of these, and port security is probably enabled.<br />
<br />
'''DNS/DHCP:'''<br />
* All DNS entries for services run by VTLUUG are hosted on [https://gandi.net Gandi]. Ask an officer if you want to change something.<br />
* jkh and Roddy own ece.vt.edu. DNS updates don't happen. echarlie can add IPv6-only records if needed to wuvt.vt.edu so we have PTRs.<br />
* [[Infrastructure:Joey|joey]] runs DHCP via dnsmasq on enp4s0 (that is, 10.98.0.0/16). To change anything, modify it on https://github.com/vtluug/scripts first then pull that into root's homedir on [[Infrastructure:Joey|joey]]. Please don't just update it on a machine without pushing your updates.<br />
* By default, hosts are accessible via SSH on ports 22 and 2222.<br />
<br />
== Adding a VTLUUG Service VM ==<br />
''VMs in this category are deployed to [[Infrastructure:Meltdown|meltdown]]''<br />
<br />
Prerequisites:<br />
* Clone <code>https://github.com/vtluug/scripts</code>. This is referred to as 'SCRIPTS' in this guide.<br />
* Clone <code>https://github.com/vtluug/ansible</code> and install ansible. This repo is referred to as 'ANSIBLE' in this guide.<br />
* Have access to [https://git.vtluug.org/officers/vtluug-admin officers/vtluug-admin] on [https://git.vtluug.org gitea].<br />
* Understand the [[Infrastructure:Network|Network]] and [[Infrastructure]].<br />
* Put your SSH key on [[Infrastructure:Meltdown|meltdown]]<br />
<br />
=== Configure the network ===<br />
* Decide on a MAC address for the host and add it to <code>SCRIPTS/router/lan/local_hosts</code><br />
* Add an entry to <code>SCRIPTS/router/lan/dnsmasq.conf</code> for static DHCP leases.<br />
* If a new IP in 128.173.88.1/22 is being added, also add it to <code>SCRIPTS/router/proxy/arp_proxy.sh</code><br />
<br />
'''Note:''' It is '''not''' recommended that you do the following steps if nobody is on campus in case something breaks.<br />
<br />
Pull the latest changes to <code>/root/scripts</code>, update the configuration files, and restart the services:<br />
* Dnsmasq configuration is at <code>/etc/dnsmasq.conf</code><br />
* ARP Proxy configuration is in <code>/usr/local/bin</code><br />
<br />
=== Add the VM configuration to ansible ===<br />
Edit <code>ANSIBLE_PATH/roles/deploy-vms/defaults/main.yml</code> and add a new entry, following the existing format.<br />
<br />
'''Note:''' if there are any entries in this file that are '''not''' present on the VM host, they will also be created. Comment out entries that shouldn't be created. Existing hosts are skipped.<br />
<br />
Run <code>ansible-playbook -v deploy.yml -i hosts.cfg -u papatux -k -K -e @VTLUUG_ADMIN_REPO/accounts.yml</code>, using the correct vtluug-admin repo path.<br />
<br />
=== Testing ===<br />
The new host should be accessible by papatux on via SSH port 2222 (and 22) over IPv6 and IPv4 from the internal network. Check 10.98.1.0/24 to see if it had any issues getting a static DHCP lease and if the MAC is correct.<br />
<br />
== Adding a User VM ==<br />
''VMs in this category are deployed to [[Infrastructure:Spectre|spectre]]''<br />
<br />
Prerequisites:<br />
* Clone <code>https://github.com/vtluug/scripts</code>. This is referred to as 'SCRIPTS' in this guide.<br />
* Clone <code>https://github.com/vtluug/ansible</code> and install ansible. This repo is referred to as 'ANSIBLE' in this guide.<br />
* Understand the [[Infrastructure:Network|Network]] and [[Infrastructure]].<br />
* Have root on [[Infrastructure:Spectre|spectre]]<br />
* Put your SSH key on [[Infrastructure:Spectre|spectre]]<br />
<br />
=== Configure the network ===<br />
* Decide on a MAC address for the host and add it to <code>SCRIPTS/router/lan/local_hosts</code><br />
* Add an entry to <code>SCRIPTS/router/lan/dnsmasq.conf</code> for static DHCP leases. (If applicable; you might not care for a test/temp VM).<br />
<br />
'''Note:''' It is '''not''' recommended that you do the following steps if nobody is on campus in case something breaks.<br />
<br />
Pull the latest changes to <code>/root/scripts</code>, update the configuration files, and restart the services:<br />
* Dnsmasq configuration is at <code>/etc/dnsmasq.conf</code><br />
<br />
=== Add the VM configuration to ansible ===<br />
Edit <code>ANSIBLE_PATH/roles/deploy-vms/defaults/main.yml</code> and add a new entry under <code>new_vms_spectre</code>, following the existing format.<br />
<br />
'''Note:''' if there are any entries in this file that are '''not''' present on the VM host, they will also be created. Comment out entries that shouldn't be created. Existing hosts are skipped.<br />
<br />
Run <code>ansible-playbook -v deploy.yml -i hosts.cfg -u papatux -k -K</code>, using the correct vtluug-admin repo path.<br />
<br />
'''Important:''' A random root password is set during VM creation and printed to stdout. Record this!<br />
<br />
=== Testing ===<br />
The new host should be accessible by root on via SSH port 2222 (and 22) over IPv6 and IPv4 from the internal network. Check 10.98.1.0/24 to see if it had any issues getting a static DHCP lease and if the MAC is correct.<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Howtos]]<br />
[[Category:Needs restoration]]</div>Rskhttps://vtluug.org/w/index.php?title=Surplus_Feb_25&diff=8097Surplus Feb 252025-02-14T16:57:34Z<p>Rsk: </p>
<hr />
<div>'''AUCTION CLOSES 7PM FEB 13th'''<br />
<br />
<br />
= Strategy =<br />
<br />
Several members will pitch funds into the pool, and portions of the total pool can be allocated to making "maximum acceptable bids" on items we are interested in. At no point will we bid more than the maximum amount deemed acceptable, nor more than is available in the pool.<br />
<br />
If we get outbid on an item higher than our maximum acceptable bid, we can re-allocate those funds to another listing's max bid.<br />
<br />
<br />
== Desired Items ==<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273051-1-pallet-of-servers-hd-removed PALLET OF SERVERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273635-1-pallet-of-computers-hd-removed PALLET OF 2010s COMPUTERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273633-1-pallet-of-computers-hd-removed PALLET OF 2000s COMPUTERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273249-2-dell-precision 2x DELL PRECISION TOWER 5810 (there are many of these listings)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273283-2-dell-precision 2x DELL PRECISION TOWER 3620 (there are many of these listings)]<br />
<br />
== Group buy funds per-member ==<br />
* [[User:Rsk]] $100<br />
* [[User:Enzoisotton]] $100<br />
* [[User:Caleb]] $100<br />
* [[User:Daddykeystroke]] $60<br />
* [[User:Botjoe]] $100<br />
* [[User:Nate]] $50<br />
<br />
== Max acceptable bid for each item ==<br />
* Server pile: ???? hard to judge without seeing model numbers<br />
* Optiplex (2010s) pile: ~$5 per however many boxes there are?<br />
* Old shit (2000s) pile: $50<br />
* 2x Precision t3XXX: $30 ($15 per)<br />
* 2x Precision t5XXX: $40 ($20 per)<br />
<br />
== Results == <br />
<br />
The club couldn't get anything -- the rackmount servers went for $700, the decent-pile for $330, an the shit-pile for $875. We are mystified as to that last one.<br />
<br />
[[User:Nate]] got a couple lots, [[User:Lyle]] got some precision 5820s, both for their personal use.<br />
<br />
[[User:Botjoe]] got two pallets of miscellaneous RF equipment for ~$110.<br />
<br />
<br />
[[Category:VTLUUG:Events]] [[Category:VTLUUG:2025]]</div>Rskhttps://vtluug.org/w/index.php?title=Surplus_Feb_25&diff=8096Surplus Feb 252025-02-14T16:57:03Z<p>Rsk: </p>
<hr />
<div>'''AUCTION CLOSES 7PM FEB 13th'''<br />
<br />
<br />
= Strategy =<br />
<br />
Several members will pitch funds into the pool, and portions of the total pool can be allocated to making "maximum acceptable bids" on items we are interested in. At no point will we bid more than the maximum amount deemed acceptable, nor more than is available in the pool.<br />
<br />
If we get outbid on an item higher than our maximum acceptable bid, we can re-allocate those funds to another listing's max bid.<br />
<br />
<br />
== Desired Items ==<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273051-1-pallet-of-servers-hd-removed PALLET OF SERVERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273635-1-pallet-of-computers-hd-removed PALLET OF 2010s COMPUTERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273633-1-pallet-of-computers-hd-removed PALLET OF 2000s COMPUTERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273249-2-dell-precision 2x DELL PRECISION TOWER 5810 (there are many of these listings)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273283-2-dell-precision 2x DELL PRECISION TOWER 3620 (there are many of these listings)]<br />
<br />
== Group buy funds per-member ==<br />
* [[User:Rsk]] $100<br />
* [[User:Enzoisotton]] $100<br />
* [[User:Caleb]] $100<br />
* [[User:Daddykeystroke]] $60<br />
* [[User:Botjoe]] $100<br />
* [[User:Nate]] $50<br />
<br />
== Max acceptable bid for each item ==<br />
* Server pile: ???? hard to judge without seeing model numbers<br />
* Optiplex (2010s) pile: ~$5 per however many boxes there are?<br />
* Old shit (2000s) pile: $50<br />
* 2x Precision t3XXX: $30 ($15 per)<br />
* 2x Precision t5XXX: $40 ($20 per)<br />
<br />
== Results == <br />
<br />
The club couldn't get anything -- the rackmount servers went for $700, the decent-pile for $330, an the shit-pile for $875. We are mystified as to that last one.<br />
<br />
[[User:Nate]] got a couple lots, [[User:Lyle]] got some precision 5820s, both for their personal use.<br />
<br />
<br />
[[Category:VTLUUG:Events]] [[Category:VTLUUG:2025]]</div>Rskhttps://vtluug.org/w/index.php?title=Surplus_Feb_25&diff=8095Surplus Feb 252025-02-13T05:13:31Z<p>Rsk: </p>
<hr />
<div>'''AUCTION CLOSES 7PM FEB 13th'''<br />
<br />
<br />
= Strategy =<br />
<br />
Several members will pitch funds into the pool, and portions of the total pool can be allocated to making "maximum acceptable bids" on items we are interested in. At no point will we bid more than the maximum amount deemed acceptable, nor more than is available in the pool.<br />
<br />
If we get outbid on an item higher than our maximum acceptable bid, we can re-allocate those funds to another listing's max bid.<br />
<br />
<br />
== Desired Items ==<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273051-1-pallet-of-servers-hd-removed PALLET OF SERVERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273635-1-pallet-of-computers-hd-removed PALLET OF 2010s COMPUTERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273633-1-pallet-of-computers-hd-removed PALLET OF 2000s COMPUTERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273249-2-dell-precision 2x DELL PRECISION TOWER 5810 (there are many of these listings)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273283-2-dell-precision 2x DELL PRECISION TOWER 3620 (there are many of these listings)]<br />
<br />
== Group buy funds per-member ==<br />
* [[User:Rsk]] $100<br />
* [[User:Enzoisotton]] $100<br />
* [[User:Caleb]] $100<br />
<br />
== Max acceptable bid for each item ==<br />
* Server pile: ???? hard to judge without seeing model numbers<br />
* Optiplex (2010s) pile: ~$5 per however many boxes there are?<br />
* Old shit (2000s) pile: $50<br />
* 2x Precision t3XXX: $30 ($15 per)<br />
* 2x Precision t5XXX: $40 ($20 per)<br />
<br />
<br />
[[Category:VTLUUG:Events]] [[Category:VTLUUG:2025]]</div>Rskhttps://vtluug.org/w/index.php?title=Surplus_Feb_25&diff=8094Surplus Feb 252025-02-13T05:09:18Z<p>Rsk: </p>
<hr />
<div>'''AUCTION CLOSES 7PM FEB 13th'''<br />
<br />
<br />
= Strategy =<br />
<br />
Several members will pitch funds into the pool, and portions of the total pool can be allocated to making "maximum acceptable bids" on items we are interested in. At no point will we bid more than the maximum amount deemed acceptable, nor more than is available in the pool.<br />
<br />
If we get outbid on an item higher than our maximum acceptable bid, we can re-allocate those funds to another listing's max bid.<br />
<br />
<br />
== Desired Items ==<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273051-1-pallet-of-servers-hd-removed PALLET OF SERVERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273635-1-pallet-of-computers-hd-removed PALLET OF 2010s COMPUTERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273633-1-pallet-of-computers-hd-removed PALLET OF 2000s COMPUTERS (HD REMOVED)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273249-2-dell-precision 2x DELL PRECISION TOWER 5810 (there are many of these listings)]<br />
* [https://www.matthewsauctioneers.com/auctions/29564/lot/273283-2-dell-precision 2x DELL PRECISION TOWER 3620 (there are many of these listings)]<br />
<br />
== Group buy funds per-member ==<br />
* [[User:Rsk]] $100<br />
* [[User:Enzoisotton]] $100<br />
<br />
== Max acceptable bid for each item ==<br />
* Server pile: ???? hard to judge without seeing model numbers<br />
* Optiplex (2010s) pile: ~$5 per however many boxes there are?<br />
* Old shit (2000s) pile: $50<br />
* 2x Precision t3XXX: $30 ($15 per)<br />
* 2x Precision t5XXX: $40 ($20 per)<br />
<br />
<br />
[[Category:VTLUUG:Events]] [[Category:VTLUUG:2025]]</div>Rsk