timy/EduNetworkBuilder
timy
/
EduNetworkBuilder
0
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Page: Create_NetTests
Pages
Create_NetTests Create_Options Create_edit MakingAPuzzle NetDevices Stu_GenericInstructions Teach_Homework Teach_MakingStudentFile Teach_MakingTeacherFile Teach_Overview Teach_StudentImport Teach_Students Teach_Troubleshooting Teach_Tutorial WorkingWithClasses home teacherdoc
5 Create_NetTests
Tim Young edited this page 2017-08-11 18:43:17 +02:00

Net Tests

On the network options, you get to specify the Net Tests which apply. As the user does things, we run these tests. If a new test is completed, EduNetworkBuilder rewards them with a small ding. If all the tests are completed, the puzzle is "complete."

Double-click the test box to add one, or right-click in the box.

These "tests" will usually keep something from being changed, deleted, or something like that. For example, if PC0 has a test that its IP address needs to be local to Router0, then it will lock PC0 so you cannot delete it. It will also lock the nic, so you cannot delete the nic. Some of the tests will only lock something. It makes it harder for someone to goof up things you do not want them to mess with.

The tests are:

  • NeedsLocalIPTo - The device needs to have an IP address that is local (made local by the subnet mask) to another device. Often you will also lock the target device, so they cannot solve the puzzle by changing the router instead of the PC. For example: PC0 needs to have an IP that is local to Router0 for this test to be marked as complete.

  • NeedsDefaultGW - The device needs a default gateway, and you also specify which device needs to be the gateway. For example: PC0 needs to have Router0 be the default gateway for this test to be marked complete.

  • NeedsLinkToDevice - The device needs a link (network wire / wireless connection) to another device. For example: PC0 needs a link to switch0 for the test to be marked as complete.

  • NeedsRouteToNet - The device needs a static route built for it. For example: Router0 needs a static route to 192.168.5.0 for this test to be marked as complete.

  • NeedsUntaggedVLAN - The device (switch / server) needs a vlan set up on it, and a specific port marked as "untagged" on a specific vlan. For example: Switch0 needs port 1 untagged on VLAN1 for this test to be marked as complete.

  • NeedsTaggedVLAN - The device (switch / server) needs a vlan set up on it, and a specific port marked as "Tagged" on a specific vlan. For example: Switch0 needs port 1 Taggedon VLAN1 for this test to be marked as complete.

  • NeedsForbiddenVLAN- The device (switch / server) needs a vlan set up on it, and a specific port marked as "forbidden" on a specific vlan. For example: Switch0 needs port 1 forbiddenon VLAN1 for this test to be marked as complete.

  • SuccessfullyPings - You need to successfully do a ping from one device to another. This ensures that the network routing between the devices is all set up and functional. This is probably the most-used test. For example: PC0 needs to successfully ping PC1 for this test to be marked as complete

  • SuccessfullyPingsAgain - This was mainly added for the "network loop" test, showing how switches learned the mac address of the device at the far end and learned a "path" to it (when using spanning tree protocol). The second ping goes along the path without a spray of packets taking down the network. You may have other uses for this, but it will not happen much. Example: PC0 sucessfully pings again PC1 for this test to be complete.

  • SuccessfullyArps - Arp is not used much in this. Initially, EduNetworkBuilder actually used ARP to find the MAC address of local machines. While it was true to life, it was very confusing to people. So ARP is currently relegated to the background. But, the test is still here. You can right-click and do an ARP test on something if you want. And, this test will be successful when you successfully do it. Example: PC0 successfully does an ARP request for PC1.

  • SuccessfullyDHCPs - This test succeeds when a computer successfully gets a DHCP IP address from the specified server, firewall, etc.

  • HelpRequest - This was mainly added so you can teach someone to use the built-in help system. You specify the help level they have to choose for it to be marked complete.

  • ReadContextHelp - If you have a Tag on your puzzle (say, DHCP), it puts a button to open up the context help on DHCP. If they click that button, then the test is marked as complete.

  • FailedPing - Use this carefully. If a ping from one machine to another fails for any reason, then the test is marked as complete. You are supposed to use it for things like making a firewall rule to keep VLAN1 from accessing VLAN2. But, someone could yank a cable between the computer and the switch, and make the ping fail. You may need to lock a lot of things to make an indestructible test. Or, if your students are submitting the homework to you, you get to see if they yanked a wire or made the firewall rule.

  • DHCPServerEnabled - This test succeeds if they click the DHCP server enabled checkmark on a server / firewall. You may want to have a PC that is set up to receive DHCP, which has a test that it gets an IP that is local to another PC on the network. That way the DHCP server needs to actually serve out good IP addresses.

  • SuccessfullyTraceroutes - If you are trying to show traceroute, this test makes sure that someone successfully does a traceroute to another computer. It means that the network routing between the two is working.

  • LockAll - Lock everything on the device that can be locked down. Do not let people delete it, or change it. Do this for things that are critical to the functioning of the test.

  • LockIP - Do not let the IP address on the specified network card be changed.

  • LockRoute - Do not let the specified route be altered. It is amazing how creative people can be. Lock this route down, just in case.

  • LockNic - Do not let the network card be changed (MAC address, IP address, multiple interfaces, etc)

  • LockDHCP - Lock the DHCP settings on the server / router.

  • LockGateway - Lock the gateway on this device.

  • LockVLANsOnHost - Lock all the VLANs on this host.

  • LockNicVLAN - Lock the VLANS on the one network card

  • LockInterfaceVLAN - Lock the VLANs on the one network card interface

  • LockVLANNames - Lock the VLAN names