Statistics
| Branch: | Tag: | Revision:

mininet @ 824afb84

Name Size Revision Age Author Comment
  bin 19bc1df1 over 7 years Brian O'Connor fixed style error
  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 824afb84 almost 7 years Rémy Léone fixup: useless_parenthesis
  mininet 824afb84 almost 7 years Rémy Léone fixup: useless_parenthesis
  util fb51cdac almost 7 years Brian O'Connor adding output file to build.py
.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 350fdbfe over 8 years Bob Lantz Allow modules (node.py) to be 1500 lines. Maybe...
CONTRIBUTORS 759 Bytes 87c37bb1 about 7 years Bob Lantz Add jpoliv
INSTALL 5.01 KB 96952b92 almost 7 years Bob Lantz 2.1.0 -> 2.1.0+
LICENSE 1.66 KB 96952b92 almost 7 years Bob Lantz 2.1.0 -> 2.1.0+
Makefile 1.49 KB 8842e450 about 7 years Jose Pedro Oliveira Turns on gcc warnings (CFLAGS += -Wall -Wextra)
README.md 4.6 KB 96952b92 almost 7 years Bob Lantz 2.1.0 -> 2.1.0+
mnexec.c 4.63 KB 8f80f875 about 7 years Jose Pedro Oliveira Change cgroup() return type from int to void (a...
setup.py 1.19 KB 896c4cbc about 7 years Bob Lantz Edits for 2.1.0

Latest revisions

# Date Author Comment
824afb84 12/20/2013 01:43 PM Rémy Léone

fixup: useless_parenthesis

a6a0cb43 12/14/2013 08:36 PM Bob

Merge pull request #250 from rlane/killpg

kill entire process group in Node.terminate

2200d8d1 12/14/2013 07:12 PM Rich Lane

node: kill entire process group in terminate

mnexec already puts the shell into its own process group. Killing the entire
process group cleans up after any background processes the user left running.

fb51cdac 12/13/2013 02:38 AM Brian O'Connor

adding output file to build.py

50423936 12/12/2013 11:56 PM Brian O'Connor

Merge branch 'master' of github.com:mininet/mininet

49994c89 12/12/2013 11:38 PM Brian O'Connor

adding noneTest to Mininet vm build script

17dbc7e0 12/12/2013 02:33 AM Bob Lantz

Minor codecheck fixes

312c386c 12/12/2013 02:29 AM Bob Lantz

Fix regex to support Mininet 20.30.40+++

96952b92 12/12/2013 02:08 AM Bob Lantz

2.1.0 -> 2.1.0+

c7e86f93 12/06/2013 01:30 AM Brian O'Connor

fixing CLI host rewriting when host's default interface does not have an IP

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.1.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.1.0+

Mininet 2.1.0+ provides a number of bug fixes as well as several new features, including:

  • Convenient access to Mininet() as a dict of nodes
  • X11 tunneling (wireshark in Mininet hosts, finally!)
  • Accurate reflection of the Mininet() object in the CLI
  • Automatically detecting and adjusting resource limits
  • Automatic cleanup on failure of the mn command
  • Preliminary support for running OVS in user space mode
  • Preliminary support (IVSSwitch()) for the Indigo Virtual Switch
  • support for installing the OpenFlow 1.3 versions of the reference user switch and NOX from CPqD
  • The ability to import modules from mininet.examples

We have provided several new examples (which can easily be imported to provide useful functionality) including:

  • Modeling separate control and data networks: mininet.examples.controlnet
  • Connecting Mininet hosts the internet (or a LAN) using NAT: mininet.examples.nat
  • Creating per-host custom directories using bind mounts: mininet.examples.bind

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!

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, new features and other issues and pull requests. Thanks to everyone who has contributed to the project (see CONTRIBUTORS for more info!)

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

Credits

The Mininet 2.1.0+ Team:

  • Bob Lantz
  • Brian O'Connor

Also available in: Atom