2.2.1d1 -> 2.2.1d2

This commit is contained in:
Bob Lantz
2015-03-18 15:47:53 -07:00
parent f49e2539b7
commit df56fa2716
4 changed files with 18 additions and 39 deletions
+1 -1
View File
@@ -2,7 +2,7 @@
Mininet Installation/Configuration Notes Mininet Installation/Configuration Notes
---------------------------------------- ----------------------------------------
Mininet 2.2.1d1 Mininet 2.2.1d2
--- ---
The supported installation methods for Mininet are 1) using a The supported installation methods for Mininet are 1) using a
+2 -2
View File
@@ -1,6 +1,6 @@
Mininet 2.2.1d1 License Mininet 2.2.1d2 License
Copyright (c) 2013-2014 Open Networking Laboratory Copyright (c) 2013-2015 Open Networking Laboratory
Copyright (c) 2009-2012 Bob Lantz and The Board of Trustees of Copyright (c) 2009-2012 Bob Lantz and The Board of Trustees of
The Leland Stanford Junior University The Leland Stanford Junior University
+14 -35
View File
@@ -3,7 +3,7 @@ Mininet: Rapid Prototyping for Software Defined Networks
*The best way to emulate almost any network on your laptop!* *The best way to emulate almost any network on your laptop!*
Mininet 2.2.1d1 Mininet 2.2.1d2
### What is Mininet? ### What is Mininet?
@@ -68,44 +68,23 @@ Mininet includes:
### New features in this release ### New features in this release
This release provides a number of bug fixes as well as This is primarily a performance improvement and bug fix release.
several new features, including:
* Improved OpenFlow 1.3 support - Batch startup has been implemented for Open vSwitch, improving
startup performance.
- `mn --switch ovs,protocols=openflow13` starts OVS in 1.3 mode - OVS patch links have been implemented via OVSLink and --link ovs
- `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 Warning! These links have *serious limitations* compared to
`LinuxBridge`, `OVSBridge`, `LinuxRouter` (see `examples/`) virtual Ethernet pairs: they are not attached to real Linux
and `NAT` interfaces so you cannot use tcpdump or wireshark with them;
they also cannot be used in long chains - we don't recommend more
than 64 OVSLinks, for example --linear,64. However, they can offer
significantly better performance than veth pairs, for certain
configurations.
* A `--nat` option which connects a Mininet network to your LAN using NAT - Additional information for this release and previous releases
(For this to work correctly, Mininet's `--ipbase` subnet should not may be found in the release notes on docs.mininet.org
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](http://docs.mininet.org) 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 ### Installation
+1 -1
View File
@@ -108,7 +108,7 @@ from mininet.util import ( quietRun, fixLimits, numCores, ensureRoot,
from mininet.term import cleanUpScreens, makeTerms from mininet.term import cleanUpScreens, makeTerms
# Mininet version: should be consistent with README and LICENSE # Mininet version: should be consistent with README and LICENSE
VERSION = "2.2.1d1" VERSION = "2.2.1d2"
class Mininet( object ): class Mininet( object ):
"Network emulation with hosts spawned in network namespaces." "Network emulation with hosts spawned in network namespaces."