Changes between Version 3 and Version 4 of UserGuidelines
- Timestamp:
- Oct 11, 2013 2:39:15 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UserGuidelines
v3 v4 3 3 * DO If you are a student, read the [https://education.deterlab.net/DETERintro/DETERintro.html Student Introduction to DeterLab] 4 4 * DON'T use control network unless absolutely necessary. This means: 5 * DON'T use full node names such as ping node1.YourExperiment.YourProject - DO use short names such as ping node1. This ensures that traffic goes over experimental network. 6 * DON'T generate traffic to 192.168.x.x network - DO use addresses of experimental interfaces. These can be from any IPv4 address range, depending on your NS file, but are often from 10.10.x.x. 5 * DON'T use full node names such as ping node1.YourExperiment.YourProject 6 * DO use short names such as ping node1. This ensures that traffic goes over experimental network. 7 * DON'T generate traffic to 192.168.x.x network 8 * DO use addresses of experimental interfaces. These can be from any IPv4 address range, depending on your NS file, but are often from 10.10.x.x address range. 7 9 8 10 Each DETER node has several network interfaces. One of those is always connected to the "control net" and used to send reboot signals, OS load and similar control info to the node. The other interfaces are for experimental use. These are connected in the topology you specified when you created the experiment. You should only use control network when absolutely necessary, i.e. there is no other way to achieve the effect you desire. Using it more often will create load for everyone on the testbed and will result in wrong results in many exercises.