MobilityFirst in OpenFlow-enabled SDN Networks

Contents

1. 0. Requirements
2. 1. System Architecture
3. 2. Installation
4. 2.1 Required Packages
5. 2.2 Installing and Building Floodlight

0. Requirements

• Software prototype with reference implementation of the MobilityFirst protocol stack, for end hosts.
• Software prototype with reference implementation of GSTAR for handling storage of chunks.
• Floodlight controller running the MobilityFirst modules.

1. System Architecture

The figure below shows the overall design of an OpenFlow based network that can support MobilityFirst.

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.

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.

2. Installation

2.1 Required Packages

sudo apt-get install build-essential default-jdk ant python-dev eclipse git

2.2 Installing and Building Floodlight

git clone git://github.com/floodlight/floodlight.git
cd floodlight
git checkout fl-last-passed-build
ant

The MobilityFirst modules for Floodlight can be downloaded from