mininet

Files

T

Brandon Heller befa1310df Revamp custom topology input

Defining custom topologies, switch types, controllers, and hosts is now
much easier.  Plus, all Ripcord-specific stuff has been moved out.

2010-01-30 02:46:08 -08:00

custom_example.py

Revamp custom topology input

2010-01-30 02:46:08 -08:00

README

Renamed mn_run.py -> mn, mn_clean.py -> mnclean; updated Makefle

2010-02-03 15:29:07 -08:00

README

This directory should hold configuration files for custom mininets.

See custom_example.py, which loads the default minimal topology.  The advantage of defining a mininet in a separate file is that you then use the --custom option in mn to run the CLI or specific tests with it.

Each custom file must define a Mininet object for an 'mn' variable.

To start up a mininet with this custom topology, do:
  sudo mn --custom custom_example.py