MiniEdit 2.1.0.1

Mininet 2.1.0 is out, so I though I would drop in a new version of MiniEdit with a few new features.

  • Preference to start CLI.  This will start the Mininet CLI in the window you started MiniEdit.  Note that there is a warning about this feature.  You will need to remember to ‘quit’ the CLI as well whenever you ‘Stop’ your mininet if you enable this feature.  By default, CLI option is off, but it can be turned on in the Preferences.
  • Made some improvements to the Export code to also export all your Preferences.
  • If you decide to upgrade your Open vSwitch in the VM to Open vSwitch 1.10 or higher, you now have the option in MiniEdit of choosing which versions of OpenFlow to enable.  OVS 1.10 added support for choosing 1.0, 1.2 and 1.3.
  • A new feature in Mininet 2.1.0 is experimental support of Indigo Virtual Switch.  I have added a Preference so you can choose to use Indigo Virtual Switch or Open vSwitch.

Download MiniEdit 2.1.0.1 here.

 

Installing Indigo Virtual Switch in Mininet 2.1.0

Mininet 2.1.0 has been released with many new improvement and features.  One of the new features is experimental support of  Indigo Virtual Switch (IVS).  By default, the Mininet 2.1.0 VM does not include IVS.  But to add this, it’s a simple few steps.

  1. Login to your Mininet VM as ‘mininet’.
  2. Make sure you Mininet VM has access to the Internet.  Just try and ping something to see if it works.
  3. In your mininet home directory, run the command mininet/util/install.sh -i

Once the installer finished, IVS should be installed.  You can check if the installation worked by running the command ivs-ctl help.

Now to try it out, we’ll copy the emptynet.py to your home directory and make a few modifications to it.

Add the import for the IVS node.

from mininet.node IVSSwitch

Then change the following line

    s3 = net.addSwitch( 's3' )

to look like the following.

    s3 = net.addSwitch( 's3', cls=IVSSwitch )

Now run the new network.

sudo ./emptynet.py

If it started successfully, you should see switch s3 show up in IVS by running ivs-ctl show in another window.

mininet@mininet-vm:~$ ivs-ctl show
ovs-system:
  kernel lookups: hit=60 missed=116 lost=0
  kernel flows=0
  ports:
    0 ovs-system (internal)
      rx: packets=0 bytes=0 errors=0 dropped=0
      tx: packets=0 bytes=0 errors=0 dropped=0
s3:
  kernel lookups: hit=0 missed=10 lost=0
  kernel flows=0
  ports:
    0 s3 (internal)
      rx: packets=0 bytes=0 errors=0 dropped=0
      tx: packets=0 bytes=0 errors=0 dropped=0
    1 s3-eth1
      rx: packets=5 bytes=378 errors=0 dropped=0
      tx: packets=5 bytes=378 errors=0 dropped=0
    2 s3-eth2
      rx: packets=5 bytes=378 errors=0 dropped=0
      tx: packets=5 bytes=378 errors=0 dropped=0

 

MiniEdit 2.0.0.6

This is more of a bug fix release.  The only major change was that I rewrote the Export code to create a Python Mininet script instead of a Mininet Topology file.  Things are going to get complicated and creating a script instead would be easier.

  • Change export file format from Mininet Topology file to Python script running Mininet.  More wiggle room.
  • Update export file to include missing host opts, hwintf additions and controller setup.
  • Fix bug in popup menues not working after loading saved file.

Download MiniEdit 2.0.0.6 here.