lab/mininet
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Minor comment changes.

Browse Source
This commit is contained in:
Bob Lantz
2010-04-11 01:42:58 -07:00
parent fce4d59dc1
commit bbe5f8a389
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mininet/net.py
+4 -1
View File
@@ -35,7 +35,7 @@ controller via the loopback interface.
In user datapath mode, the controller and switches can be full-service In user datapath mode, the controller and switches can be full-service
nodes that live in their own network namespaces and have management nodes that live in their own network namespaces and have management
interfaces and IP addresses on a control network (e.g. 10.0.123.1, interfaces and IP addresses on a control network (e.g. 192.168.123.1,
currently routed although it could be bridged.) currently routed although it could be bridged.)
In addition to a management interface, user mode switches also have In addition to a management interface, user mode switches also have
@@ -61,6 +61,9 @@ of 10.x.y.z/8 where x.y.z is the base-256 representation of N for
hN. This mapping allows easy determination of a node's IP hN. This mapping allows easy determination of a node's IP
address from its name, e.g. h1 -> 10.0.0.1, h257 -> 10.0.1.1. address from its name, e.g. h1 -> 10.0.0.1, h257 -> 10.0.1.1.
Note also that 10.0.0.1 can often be written as 10.1 for short, e.g.
"ping 10.1" is equivalent to "ping 10.0.0.1".
Currently we wrap the entire network in a 'mininet' object, which Currently we wrap the entire network in a 'mininet' object, which
constructs a simulated network based on a network topology created constructs a simulated network based on a network topology created
using a topology object (e.g. LinearTopo) from mininet.topo or using a topology object (e.g. LinearTopo) from mininet.topo or