From bbe5f8a389276c4f66e998e69e928e708bb521cd Mon Sep 17 00:00:00 2001 From: Bob Lantz Date: Sun, 11 Apr 2010 01:42:58 -0700 Subject: [PATCH] Minor comment changes. --- mininet/net.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/mininet/net.py b/mininet/net.py index 6e9e2b5..928812d 100755 --- a/mininet/net.py +++ b/mininet/net.py @@ -35,7 +35,7 @@ controller via the loopback interface. In user datapath mode, the controller and switches can be full-service 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.) 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 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 constructs a simulated network based on a network topology created using a topology object (e.g. LinearTopo) from mininet.topo or