| Branch: | Tag: | Revision:

mininet @ 083322a2

Name Size Revision Age Author Comment
  bin 686a9993 almost 7 years cody burkard add Ryu controller to mininet
  custom dec1f402 over 8 years Brandon Heller custom topo: remove author name No need for th...
  debian f66e9af5 almost 8 years Bob Lantz Update for 2.1.0 final packaging
  doc c04ef88e over 8 years Bob Lantz Add note regarding removing old OVS junk.
  examples 736db20c over 6 years cody burkard merge HostWithPrivateDirs into Host
  mininet 083322a2 over 6 years Bob Lantz Draft update for Mininet 2.2b0
  util 8225105c over 6 years Bob Lantz Fix to allow more flexible version numbers
.gitattributes 17 Bytes 29884297 almost 9 years Bob Lantz show method names in git diff output
.gitignore 106 Bytes 4f33cad0 almost 9 years Bob Lantz Ignore more stuff, notably generated docs and m...
.pylint 8.74 KB 350fdbfe over 9 years Bob Lantz Allow modules ( to be 1500 lines. Maybe...
CONTRIBUTORS 914 Bytes 083322a2 over 6 years Bob Lantz Draft update for Mininet 2.2b0
INSTALL 5.27 KB 083322a2 over 6 years Bob Lantz Draft update for Mininet 2.2b0
LICENSE 1.66 KB 083322a2 over 6 years Bob Lantz Draft update for Mininet 2.2b0
Makefile 1.49 KB 8842e450 almost 8 years Jose Pedro Oliveira Turns on gcc warnings (CFLAGS += -Wall -Wextra) 4.63 KB 083322a2 over 6 years Bob Lantz Draft update for Mininet 2.2b0
mnexec.c 5.63 KB b85943dc almost 7 years Bob Lantz chdir() to correct path after calling chroot() ... 1.19 KB 896c4cbc almost 8 years Bob Lantz Edits for 2.1.0

Latest revisions

# Date Author Comment
083322a2 11/06/2014 08:05 PM Bob Lantz

Draft update for Mininet 2.2b0

8225105c 11/06/2014 08:05 PM Bob Lantz

Fix to allow more flexible version numbers

4f8aa1d8 11/06/2014 12:49 AM Bob Lantz

Don't check rt_runtime_us for CFS scheduler

060d46a2 11/06/2014 12:18 AM Bob Lantz

Set VM date based on host date.

This should fix #398 for real; note that if we try to shut down ntpd
right at boot, it doesn't work! ;-(

However, setting the Unix time in the traditional manner using seconds
since 1970 should do the trick!

820c3be7 11/05/2014 01:20 AM Bob Lantz

Reorganize CFS and RT default/error conditions.

a562ca1b 11/05/2014 12:27 AM Bob Lantz

Move RT check into its own method, and save value.

658761d9 11/05/2014 12:09 AM lantz

Merge pull request #419 from cdburkard/patches/rt_failure_output

fix silent failures when rt cannot be assigned - will follow up on this

ec9f02c7 11/04/2014 11:09 PM lantz

Merge pull request #424 from cdburkard/devel/mergePrivate

merge HostWithPrivateDirs into Node

f75bee62 11/04/2014 08:49 PM lantz

Merge pull request #429 from cdburkard/patches/cluster_m

ensure we retrieve a single PID when run on a cluster node

6e5ac34b 11/04/2014 04:01 AM Bob Lantz

Update module comment.

View all revisions | View revisions


Mininet: Rapid Prototyping for Software Defined Networks

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

Version 2.2b0

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 2.2b0

Mininet 2.2b0 provides a number of bug fixes as well as several new features, including:

  • Improved OpenFlow 1.3 support

    • mn --switch ovs,protocols=openflow13 starts OVS in 1.3 mode
    • -w installs 1.3-compatible Wireshark dissector using Loxigen
    • -y installs Ryu 1.3-compatible controller
  • A new node library, and new Node types including LinuxBridge, OVSBridge, LinuxRouter and NAT

  • An improved MiniEdit GUI (examples/ - thanks to Gregory Gee

  • Experimental cluster support - consult the documentation for details, as well as examples/ and an experimental --cluster option for topologies built with the default Host and OVSSwitch classes:

    mn --cluster localhost,server1,server2


Note that examples contain experimental features which might "graduate" into mainline Mininet in the future, but they should not be considered a stable part of the Mininet API!


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

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!

The Mininet 2.2b0 Core Team:

  • Bob Lantz
  • Brian O'Connor
  • Cody Burkard

Thanks again to all of the Mininet contributors, particularly Gregory Gee for his work on MiniEdit.

Also available in: Atom