Statistics
| Branch: | Tag: | Revision:

mininet @ 3e1100b7

Name Size Revision Age Author Comment
  bin 686a9993 over 6 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 over 7 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 4a304688 over 6 years Bob Lantz Select TCP Reno and run iperf for a longer time...
  mininet 3e1100b7 over 6 years Bob Lantz Clarify MultiTopo docstrs and copy addLInk opts...
  util abcdf185 over 6 years Bob Lantz Uninstall ntpd to disable it more reliably
.gitattributes 17 Bytes 29884297 over 8 years Bob Lantz show method names in git diff output
.gitignore 106 Bytes 4f33cad0 over 8 years Bob Lantz Ignore more stuff, notably generated docs and m...
.pylint 8.74 KB 350fdbfe about 9 years Bob Lantz Allow modules (node.py) to be 1500 lines. Maybe...
CONTRIBUTORS 914 Bytes 083322a2 over 6 years Bob Lantz Draft update for Mininet 2.2b0
INSTALL 5.27 KB bb76c212 over 6 years Bob Lantz Use 2.2.0b0 for consistency with earlier Minine...
LICENSE 1.66 KB bb76c212 over 6 years Bob Lantz Use 2.2.0b0 for consistency with earlier Minine...
Makefile 1.49 KB 8842e450 over 7 years Jose Pedro Oliveira Turns on gcc warnings (CFLAGS += -Wall -Wextra)
README.md 4.64 KB 481cbea1 over 6 years Bob Lantz Update mininet docs ref to markdown format
mnexec.c 5.63 KB b85943dc over 6 years Bob Lantz chdir() to correct path after calling chroot() ...
setup.py 1.19 KB 896c4cbc over 7 years Bob Lantz Edits for 2.1.0

Latest revisions

# Date Author Comment
3e1100b7 11/10/2014 11:18 PM Bob Lantz

Clarify MultiTopo docstrs and copy addLInk opts

Note: it's a bit confusing, but we need to copy the link
parameter dicts (since we update them with node info), but we
can share the node dicts. Perhaps we should copy the node
dicts as well...

086afe85 11/10/2014 10:12 PM lantz

Merge pull request #434 from cdburkard/patches/cluster_x11

wrap the title string in quotes so that bash interprets it correctly

abcdf185 11/10/2014 10:09 PM Bob Lantz

Uninstall ntpd to disable it more reliably

4a304688 11/10/2014 08:39 PM Bob Lantz

Select TCP Reno and run iperf for a longer time interval

The hope is that this will make the results a bit more consistent
when running in a VM environment.

d3377bf9 11/10/2014 08:37 PM Bob Lantz

Add seconds option to iperf()

15275048 11/08/2014 12:58 AM lantz

Merge pull request #433 from mininet/devel/update-version-2.2b0

Initial update of README, text files and versions for 2.2.0b0

3baccfee 11/08/2014 12:16 AM lantz

Merge pull request #416 from mininet/devel/multitopo

Multi-link topology support

481cbea1 11/07/2014 11:23 PM Bob Lantz

Update mininet docs ref to markdown format

b817cbc0 11/07/2014 11:12 PM Bob Lantz

Update documentation link

bb76c212 11/07/2014 11:08 PM Bob Lantz

Use 2.2.0b0 for consistency with earlier Mininet releases

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.2.0b0

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 1.3-compatible Wireshark dissector using Loxigen
    • install.sh -y installs Ryu 1.3-compatible controller
  • A new nodelib.py node library, and new Node types including LinuxBridge, OVSBridge, LinuxRouter and NAT

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

  • 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!

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