Statistics
| Branch: | Tag: | Revision:

mininet @ b1ec912d

Name Size Revision Age Author Comment
  bin 5a530af1 almost 6 years Bob Lantz Remove trailing whitespace. ;-/
  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 b1ec912d almost 6 years Bob Lantz Fixing pylint errors
  mininet b1ec912d almost 6 years Bob Lantz Fixing pylint errors
  util 5a530af1 almost 6 years Bob Lantz Remove trailing whitespace. ;-/
.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 8.74 KB 3c9f5ad5 almost 6 years Bob Lantz Disable pep8 whitespace errors
CONTRIBUTORS 914 Bytes 083322a2 almost 6 years Bob Lantz Draft update for Mininet 2.2b0
INSTALL 5.32 KB 4219b229 almost 6 years Bob Lantz 2.2.0b2
LICENSE 1.66 KB 4219b229 almost 6 years Bob Lantz 2.2.0b2
Makefile 1.57 KB db45b7c6 almost 6 years Bob Lantz Parseable output format for newer pylint
README.md 5.1 KB 4219b229 almost 6 years Bob Lantz 2.2.0b2
mnexec.c 5.59 KB 9b5fa1d7 almost 6 years Bob Lantz Always chdir() to current working directory.
setup.py 1.19 KB 896c4cbc about 7 years Bob Lantz Edits for 2.1.0

Latest revisions

# Date Author Comment
b1ec912d 12/03/2014 07:00 AM Bob Lantz

Fixing pylint errors

db45b7c6 12/03/2014 07:00 AM Bob Lantz

Parseable output format for newer pylint

2256a538 12/03/2014 06:59 AM Bob Lantz

Fix pylint error

03ef5567 12/03/2014 06:58 AM Bob Lantz

Add cleanup and fix pylint errors

c45bfab3 12/03/2014 06:58 AM Bob Lantz

Add cleanup

b2fcab82 12/03/2014 06:58 AM Bob Lantz

Add cleanup and fix pylint errors

1471da95 12/03/2014 06:57 AM Bob Lantz

Fix pylint errors

5a530af1 12/01/2014 11:39 PM Bob Lantz

Remove trailing whitespace. ;-/

3c9f5ad5 12/01/2014 11:38 PM Bob Lantz

Disable pep8 whitespace errors

c5d9e0e0 12/01/2014 11:10 PM Bob Lantz

Set default route in one cmd line to avoid dc'ing root NS

Usually you won't want to create a node in the root namespace,
and usually you won't want to use the Mininet API to set your
(real) default route, but if you do then you will probably want
to use a single command line to avoid disconnecting an SSH...

View all revisions | View revisions

README


Mininet: Rapid Prototyping for Software Defined Networks

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

Mininet 2.2.0b2

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 this release

This release 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
    • install.sh -w installs a 1.3-compatible Wireshark dissector using Loxigen
    • install.sh -y installs the Ryu 1.3-compatible controller
  • A new nodelib.py node library, and new Node types including LinuxBridge, OVSBridge, LinuxRouter (see examples/) and NAT

  • A --nat option which connects a Mininet network to your LAN using NAT (For this to work correctly, Mininet's --ipbase subnet should not overlap with any external or internet IP addresses you wish to use)

  • An improved MiniEdit GUI (examples/miniedit.py) - thanks to Gregory Gee

  • Support for multiple --custom arguments to mn

  • Experimental cluster support - consult the documentation for details - as well as examples/cluster.py 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!

A number of bugs have also been fixed, most notably multiple link support in Topo(). See github issues and the release notes on the Mininet wiki for additional information.

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

Join Us

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, 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 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