Statistics
| Branch: | Tag: | Revision:

mininet @ 804c4bbf

Name Size Revision Age Author Comment
  bin 294bbad4 about 8 years Bob Lantz Display usage information if there are extra ar...
  custom dec1f402 over 8 years Brandon Heller custom topo: remove author name No need for th...
  debian 65c35b65 about 8 years ryanc Remove networkx dependency Conflicts: util/i...
  doc c04ef88e over 8 years Bob Lantz Add note regarding removing old OVS junk.
  examples 33e39a24 about 8 years Bob Lantz Fix some pylint messages.
  mininet 804c4bbf about 8 years Bob Lantz Workaround: add dpopts to UserSwitch Currently...
  util 307d60a0 about 8 years Bob Lantz Replace /etc/hostname entirely; clarify sources...
.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 (node.py) to be 1500 lines. Maybe...
INSTALL 4.06 KB 5879c492 over 8 years Bob Lantz Minor clarifications.
LICENSE 1.66 KB 21366afc over 8 years Bob Lantz 2.0.0rc1 -> 2.0.0 final
Makefile 1.46 KB e1205a8a over 8 years Brandon Heller Add a simple unit test for link/host creation w...
README.md 4.18 KB 21366afc over 8 years Bob Lantz 2.0.0rc1 -> 2.0.0 final
mnexec.c 4.59 KB 33c7e464 over 8 years Bob Lantz Use __NR_setns so that setns has the right sysc...
setup.py 1.17 KB 65c35b65 about 8 years ryanc Remove networkx dependency Conflicts: util/i...

Latest revisions

# Date Author Comment
804c4bbf 06/26/2013 01:14 PM Bob Lantz

Workaround: add dpopts to UserSwitch

Currently, slicing on the user switch breaks bandwidth limits.
We don't yet have a good way of using both of them at the same time.
I'm inclined to turn off slicing by default, but I have to think
about it and also see if any one is using it...

1a658054 06/26/2013 12:00 PM Bob Lantz

Ensure dpid is a valid hex string in OVSSwitch

33e39a24 06/26/2013 03:26 AM Bob Lantz

Fix some pylint messages.

538a856c 06/26/2013 03:16 AM Bob Lantz

Add Switch.connected() and OVSSwitch.controllerUUIDs()

877e7efb 06/26/2013 02:39 AM Bob Lantz

Minor comment change and text change.

bdd43bea 06/26/2013 02:31 AM Bob Lantz

Clean up (and fix) OVSSwitch fast reconnect

307d60a0 06/25/2013 11:35 PM Bob Lantz

Replace /etc/hostname entirely; clarify sources.list edit

12758046 06/25/2013 07:51 PM Bob Lantz

Fix setDefaultRoute to work with passed parameters.

9aaf87c1 06/25/2013 07:06 AM Bob

Fix typo.

400bbbac 06/25/2013 07:04 AM Bob

Update archive for 13.04

View all revisions | View revisions

README


Mininet: Rapid Prototyping for Software Defined Networks

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

Version 2.0.0

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).

Features

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.0.0

Mininet 2.0.0 is a major upgrade and provides a number of enhancements and new features, including:

  • "Mininet-HiFi" functionality:

    • Link bandwidth limits using tc (TCIntf and TCLink classes)
    • CPU isolation and bandwidth limits (CPULimitedHost class)
  • Support for Open vSwitch 1.4+ (including Ubuntu OVS packages)

  • Debian packaging (and apt-get install mininet in Ubuntu 12.10)

  • First-class Interface (Intf) and Link (Link) classes for easier extensibility

  • An upgraded Topology (Topo) class which supports node and link customization

  • Man pages for the mn and mnexec utilities.

[Since the API (most notably the topology) has changed, existing code that runs in Mininet 1.0 will need to be changed to run with Mininet 2.0. This is the primary reason for the major version number change.]

Installation

See INSTALL for installation instructions and details.

Documentation

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.)

Support

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

https://mailman.stanford.edu/mailman/listinfo/mininet-discuss

Contributing

Mininet is an open-source project and is currently hosted at https://github.com/mininet. You are encouraged to download the code, examine it, modify it, and submit bug reports, bug fixes, feature requests, and enhancements!

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

Credits

The Mininet Team:

  • Bob Lantz
  • Brandon Heller
  • Nikhil Handigol
  • Vimal Jeyakumar

Also available in: Atom