MiniEdit 2.1.0.8

This release got more focus on adding different node types.  From a MiniNet perspective, all these can by done using the MiniNet Python API.  But from the MiniEdit GUI perspective, I thought I’d create them as different icons you can see on the canvas for better visualization.

New node types:

  • Switch now includes additional options to be:
    • UserSwitch
    • UserSwitch inNamespace
  • Legacy Switch.  This is Open vSwitch running in standalone mode as a non-SDN L2 learning switch.
  • Legacy Router.  This under the hood is the same as a Host but with IPv4 forwarding turned on. Since is extends Host, you have the ability to XTerm into it and setup any additional static routes you want or run a dynamic routing protocol in it.

Other improvements and fixes:

  • Fixed bug in setting DPID on Switch.
  • New icons for some of the nodes. The OpenFlow switch uses the OpenFlow icon.
  • Only use TCLink and CPULimitedHost classes when actually needed.

Download MiniEdit 2.1.0.8 here.

MiniEdit2108

 

 

Advertisements

5 Responses to MiniEdit 2.1.0.8

  1. brownbytes says:

    Hi Gregory,

    I have been following your blog since sometime now and have interacted with you over mininet discussion forums. Just curious to know about the routers you have used in miniedit, assuming they are hosts in mininet, did you succeed in running dynamic routing protocols or an routing engine on them? I tried to run quagga but since there is single /etc file , running the routing daemon on one host, prohibited me from running the routing daemon on other host. I am just curious to know, if you got it working?

    • gregorygee says:

      I tried getting quagga OSPF to run, but as you mentioned, the OSPF instance in each were sharing information with each other which meant that when i told OSPF to list all the interfaces in h1, it listed all the interfaces in h1 and h2. Something I want to try, maybe you could try, is to create a host like in the bind.py example and see if that works better. The bind.py in Mininet 2.1 was broke and I believe they fixed it just last week, so you will need the latest Mininet from GIT to do it.

      BTW, if you grab the latest from GIT, the miniedit.py that is in the example directory is a copy of my 2.1.0.8.1 MiniEdit. They let me merge in my latest copy.

  2. olu says:

    Any success on this? I am trying to work on something similar. if yes kindly provide directions.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: