Sanity check

This is a list of things that you must take into account before running Odin. Otherwise, it will not work.

• If you specify an AP in the poolfile of the Controller, you have to start Odin on it. Otherwise, strange things may happen, i.e. the Controller does not find an AP, but it sometimes it thinks it is alive. If you put an AP in the list of the poolfile, run start.sh on it. Otherwise, remove it from the poolfile.

• You must specify the same SSID in two places: a) NETWORK parameter in the Odin Controller poolfile; b) the .cli file running in the Agent, generated with this script.

• The AP SSIDs set in /etc/config/wireless has to be different than the SSID used for Odin/Wi5.

• The Odin SSID cannot have CAPITAL letters.

• You must specify the same wi-fi channel number in two places: a) the .cli file running in the Agent, generated with this script; b) the radio0 part of the file /etc/config/wireless of the AP.

• You must specify the same Odin UDP port (default 2819) in two places: a) the .cli file running in the Agent, generated with this script; b) the src/main/resources/floodlightdefault.properties file, line net.floodlightcontroller.odin.master.OdinMaster.masterPort = 2819

• You must specify the same Odin TCP port (default 6777) in two places: a) the .cli file running in the Agent; b) the src/main/java/net/floodlightcontroller/odin/master/OdinAgent.java file, line private final int ODIN_AGENT_PORT = 6777;

• In the Agent, you must create a monitor device (e.g. mon0) in addition to the wireless device (e.g. wlan0), but both interfaces must be up during operation. The reason is that a device in monitor mode does not send layer-2 ACKs, if the main interface is not active.

• In the Agent, the name of the auxiliary interface MUST BE wlan1, and the corresponding mon1.

• If the auxiliary interface is not created properly, check this page