Difference between revisions of "Network Testing Network (Das Unternet)"
Jump to navigation
Jump to search
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{migrated}} | ||
| + | [https://docs.google.com/a/freegeek.org/document/d/17Hz9zWzKDsjpC8CCoswJrJYsFYXGMegqiNDCbESmNO8/edit?usp=sharing New Page] | ||
==Advanced Testing Network Testing Network, or, Das Unternet== | ==Advanced Testing Network Testing Network, or, Das Unternet== | ||
Latest revision as of 13:47, 4 April 2014
 This page has been migrated to a document on Free Geek's Google Drive. Information remaining behind may no longer be relevant. MIGRATOR: When you have tagged this page as migrated, (Link to new page immediately below.) |
Advanced Testing Network Testing Network, or, Das Unternet
- In order to securely test network devices in Advanced Testing, we've set up a secure network with minimal services to verify that devices such as switches, wireless access points, and routers work without exposing our main network to untrusted devices.
- Services on Das Unternet are provided by the virtual machine "drydock," and the network is 10.4.4.0/24. The services provided are DHCP and an httpd server on 10.4.4.1 ("drydock")/
- To troubleshoot, plug a laptop with a known working ethernet port into the Das Unternet jack in Advanced testing. make sure you obtain a DHCP lease in the 10.4.4.0/24 network, then navigate to http://10.4.4.1/ and look for the "It Works!" page. If these steps work, then the fault does not lie with Das Unternet, but rather with whatever device is being tested.
- Possible points of failure:
- the cable from Advanced Testing is plugged into the wrong network
- drydock's host machine is plugged into the wrong network (ask a Technocrat)
- drydock's host machine has a bad network card (ask a Technocrat)
- drydock is offline (ask a Technocrat)
- the web server may not be running (ask a Technocrat, and remind them that drydock is running nginx if they get frustrated)