Schemes

Scheme of the elements

This is a scheme of these elements, for the particular case of the router TP-Link AC1750 (note that the names of the network interfaces may change for other routers):

As you may observe, we have used different interfaces for the Data plane and the Control plane, in order to separate them.

• The data traffic generated by the mobile device arrives at mon0, and to the Click Wi-5 agent. It is sent to the ap interface. The OpenVswitch bridge br0 sends it to eth1.2 and then to the router (Internet).

• The Odin control traffic is sent by the Click Wi-5 agent to eth1.1, and then to the controller.

• The traffic to control the OpenVswitch (Openflow) also goes through eth1.1.

Scheme of our setup

This is the scheme of our setup, which includes a separate control and data planes:

Each agent has an IP address on each plane:

• Control plane: 192.168.1.x, eth1.1.

• Data plane: 192.168.2.x, eth1.2.

The machine acting as router & DHCP server performs NAT between data plane addresses and its public address, in order to provide access to the Internet. This is the script that runs in the router:

#!/bin/bash

#Activate forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward

#Configure NAT
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

#Initiate the dhcp server
/etc/init.d/isc-dhcp-server start