| Branch: | Tag: | Revision:

mininet @ 312ed1a4

Name Size Revision Age Author Comment
  bin 68ae67dc over 5 years Bob Lantz Support custom links in custom file
  custom dec1f402 almost 8 years Brandon Heller custom topo: remove author name No need for th...
  debian f66e9af5 about 7 years Bob Lantz Update for 2.1.0 final packaging
  doc c04ef88e almost 8 years Bob Lantz Add note regarding removing old OVS junk.
  examples d5d66f12 about 5 years Roan Huang Fixed `whoami` output problem in Re...
  mininet 0298e9be almost 5 years Rahman Pujianto addNAT always use first switch addNAT always u...
  util 312ed1a4 over 4 years Bob Lantz Use our github forks of openflow, oflops for no...
.gitattributes 17 Bytes 29884297 about 8 years Bob Lantz show method names in git diff output
.gitignore 106 Bytes 4f33cad0 about 8 years Bob Lantz Ignore more stuff, notably generated docs and m...
.pylint 9.02 KB e341526f almost 6 years Bob Lantz Raise line limit to 4000 for (see n...
CONTRIBUTORS 941 Bytes 66e9845f over 5 years Bob Lantz Add babisk
INSTALL 5.28 KB ce2458c1 over 5 years M S Vishwanath Bhat INSTALL: Another trivial path fix S...
LICENSE 1.66 KB ab8c4e91 over 5 years Bob Lantz 2.2.1rc1 -> 2.2.1
Makefile 1.76 KB cdbbb5b7 about 5 years Tomasz Buchert don't generate .pyc files on some makefile targets 4.36 KB ab8c4e91 over 5 years Bob Lantz 2.2.1rc1 -> 2.2.1
mnexec.c 5.88 KB 96ea5367 almost 5 years Tomasz Buchert mnexec: properly setup the mount namespace Sys... 1.19 KB 896c4cbc about 7 years Bob Lantz Edits for 2.1.0

Latest revisions

# Date Author Comment
312ed1a4 01/12/2016 01:24 AM Bob Lantz

Use our github forks of openflow, oflops for now

This enables us to test our changes for Ubuntu 15 (new gcc/c99)
before pushing upstream if desired.

ce5738b4 01/12/2016 12:58 AM lantz

Merge pull request #533 from pichuang/node

Check for ovs-testcontroller in OVSController

447db4c7 01/12/2016 12:56 AM lantz

Merge pull request #526 from msvbhat/master

Fixing the in INSTALL file

b47aa5da 12/01/2015 12:09 AM lantz

Merge pull request #558 from bregman-arie/master

Update to support RedHat distrubtion

af0215fb 11/23/2015 11:40 PM lantz

Merge pull request #536 from jonohart/buildcpu

Add parameter for number of CPU cores to use in VM builds

2791333c 11/23/2015 11:33 PM lantz

Merge pull request #566 from moz/master

addNAT always use first switch

96ea5367 11/18/2015 07:47 PM Tomasz Buchert

mnexec: properly setup the mount namespace

Systemd's default is to mark the root mount as shared and it is
inherited as such by the new mount namespace. This means that any
mounts performed inthe new namespace will be visible by the rest of
the system, breaking privateDirs....

0298e9be 11/09/2015 04:48 AM Rahman Pujianto

addNAT always use first switch

addNAT always use first switch even though another switch specified

7c6d645a 10/22/2015 11:34 PM Bob Lantz

Workaround for cgdelete deleting cgroup but returning error

fixes #513

0c2fbaf1 10/18/2015 07:40 AM Arie Bregman

Update to support RedHat distrubtion

Mininet installation will also work on RedHat distribution

View all revisions | View revisions


Mininet: Rapid Prototyping for Software Defined Networks

The best way to emulate almost any network on your laptop!

Mininet 2.2.1

What is Mininet?

Mininet emulates a complete network of hosts, links, and switches on a single machine. To create a sample two-host, one-switch network, just run:

sudo mn

Mininet is useful for interactive development, testing, and demos, especially those using OpenFlow and SDN. OpenFlow-based network controllers prototyped in Mininet can usually be transferred to hardware with minimal changes for full line-rate execution.

How does it work?

Mininet creates virtual networks using process-based virtualization and network namespaces - features that are available in recent Linux kernels. In Mininet, hosts are emulated as bash processes running in a network namespace, so any code that would normally run on a Linux server (like a web server or client program) should run just fine within a Mininet "Host". The Mininet "Host" will have its own private network interface and can only see its own processes. Switches in Mininet are software-based switches like Open vSwitch or the OpenFlow reference switch. Links are virtual ethernet pairs, which live in the Linux kernel and connect our emulated switches to emulated hosts (processes).


Mininet includes:

  • A command-line launcher (mn) to instantiate networks.

  • A handy Python API for creating networks of varying sizes and topologies.

  • Examples (in the examples/ directory) to help you get started.

  • Full API documentation via Python help() docstrings, as well as the ability to generate PDF/HTML documentation with make doc.

  • Parametrized topologies (Topo subclasses) using the Mininet object. For example, a tree network may be created with the command:

    mn --topo tree,depth=2,fanout=3

  • A command-line interface (CLI class) which provides useful diagnostic commands (like iperf and ping), as well as the ability to run a command to a node. For example,

    mininet> h11 ifconfig -a

    tells host h11 to run the command ifconfig -a

  • A "cleanup" command to get rid of junk (interfaces, processes, files in /tmp, etc.) which might be left around by Mininet or Linux. Try this if things stop working!

    mn -c

New features in this release

This is primarily a performance improvement and bug fix release.

  • Batch startup has been implemented for Open vSwitch, improving startup performance.

  • OVS patch links have been implemented via OVSLink and --link ovs

    Warning! These links have serious limitations compared to virtual Ethernet pairs: they are not attached to real Linux interfaces so you cannot use tcpdump or wireshark with them; they also cannot be used in long chains - we don't recommend more than 64 OVSLinks, for example --linear,64. However, they can offer significantly better performance than veth pairs, for certain configurations.

  • You can now easily install Mininet on a Raspberry Pi ;-)

  • Additional information for this release and previous releases may be found in the release notes on


See INSTALL for installation instructions and details.


In addition to the API documentation (make doc), much useful information, including a Mininet walkthrough and an introduction to the Python API, is available on the Mininet Web Site. There is also a wiki which you are encouraged to read and to contribute to, particularly the Frequently Asked Questions (FAQ.)


Mininet is community-supported. We encourage you to join the Mininet mailing list, mininet-discuss at:

Join Us

Thanks again to all of the Mininet contributors!

Mininet is an open source project and is currently hosted at You are encouraged to download the code, examine it, modify it, and submit bug reports, bug fixes, feature requests, new features and other issues and pull requests. Thanks to everyone who has contributed code to the Mininet project (see CONTRIBUTORS for more info!) It is because of everyone's hard work that Mininet continues to grow and improve.

Enjoy Mininet

Best wishes, and we look forward to seeing what you can do with Mininet to change the networking world!

Bob Lantz Mininet Core Team

Also available in: Atom