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

Minor config notes changes.

Browse Source
This commit is contained in:
Bob Lantz
2010-03-14 00:18:24 -08:00
parent 0e2a7240c3
commit bca38c997e
1 changed files with 3 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
INSTALL
+3 -10
View File
@@ -10,19 +10,12 @@ Preliminary Mininet Installation/Configuration Notes
This places the mininet package in /usr/lib/python-2.5/site-packages/, This places the mininet package in /usr/lib/python-2.5/site-packages/,
so that 'import mininet' will work. so that 'import mininet' will work.
- A functional netns binary is required to run mininet, but currently you - Installation is simplest with a distribution that includes a kernel
have to compile it and install it yourself from the included .c file:
to make it: make netns (or cc -o netns netns.c)
to test it: ./netns /sbin/ifconfig -a
to 'install' a link to it, you could do something like:
sudo ln -s /home/openflow/mininet/netns /usr/local/bin/netns
Installation is simplest with a distribution that includes a kernel
which supports the CLONE_NETNS unshare flag by default. Debian 5.0+ does which supports the CLONE_NETNS unshare flag by default. Debian 5.0+ does
(e.g. current debian-testing release); Ubuntu doesn't. If your kernel (e.g. current debian-testing release); Ubuntu doesn't. If your kernel
doesn't support it, you will need to build and install a kernel that doesn't support it, you will need to build and install a kernel that
does! does! If you are using OpenVSwitch, 2.6.33 works best. For the reference
kernel switch, 2.6.30 is compatible.
- Mininet should probably be run either on a machine with - Mininet should probably be run either on a machine with
no other important processes, or on a virtual machine. no other important processes, or on a virtual machine.