close Warning: Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.

Changes between Version 5 and Version 6 of Proto/cModules/e0SDN/a0OpenFlow/a0Floodlight/a0SoftwareDesign


Ignore:
Timestamp:
Mar 5, 2013, 4:03:29 PM (11 years ago)
Author:
aravind
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Proto/cModules/e0SDN/a0OpenFlow/a0Floodlight/a0SoftwareDesign

    v5 v6  
    1212 The figure below shows the overall design of an OpenFlow based network that can support MobilityFirst.
    1313
    14 [[SDN supporting MobilityFirst (GEC_Poster_Figure.png)]]
     14[[Image(GEC_Poster_Figure.png)]]
    1515
    1616 All OpenFlow switches that are to perform the functions of a MobilityFirst router are connected to a central controller. As the sender starts to transmit data, the first packet of the chunk is sent to the controller since there is no matching flow rule as of yet. The controller uses the GUID  map it created using link probe messages to compute the out port on the switch and sends an appropriate flow rule. The rest of the packets are then forwarded by the switch. Chunks that have to be stored are sent to a software CLICK based router which can handle chunk storage.
     17 
     18 The flow rules are set up using VLAN tags. Every host that wants to send MobilityFirst chunks inserts the hop ID of the packet as a VLAN tag. The controller uses this tag to set up a matching flow rule on the switch.
    1719
     20== 2. Installation ==
     21
     22== 2.1 Required Packages ==
     23
     24{{{
     25sudo apt-get install build-essential default-jdk ant python-dev eclipse git
     26}}}
     27
     28== 2.2 Installing and Building Floodlight ==
     29
     30{{{
     31git clone git://github.com/floodlight/floodlight.git
     32cd floodlight
     33git checkout fl-last-passed-build
     34ant
     35}}}
     36The MobilityFirst modules for Floodlight can be downloaded from
     37
     38{{{
     39}}}