Testing

These are some miscellaneous tasks to test various aspects of the system.

Booting up

The first step is to boot up all the nodes. For Soekris boxes, you would need a PC-based hyperterminal (http://blizzard.cs.uwaterloo.ca/tetherless/index.php/Viewing_Soekris_Console_Display_on_Windows) connected to the serial port to view the output.

Logging In

The nodes have been initiated with login "root" and password "KioskNet", both without the quotes. Use this to log in to the nodes.

Setting the Date and Time

To check the date and time:

        $date

This will produce an output like:

        Wed Jan 1 00:00:00 EDT 2005

To set the date to (for example) April 30, 2008 on all the four nodes, one by one, use the following:

        $date 30042008

To set the time to (for examples) 4:35pm:

        $date 16:35

Wired Connectivity between Ferry, Kiosk and Gateway

Setting wired IP addresses for the kiosk and ferry

The first step however is to set up a wired network connecting the nodes together. Use Ethernet cables and a hub to connect the 3 nodes -- Kiosk, Ferry, and Gateway. To set the IP addresses on the kiosk and ferry nodes, use the serial port hyperterminal for each to do the following:

Open a terminal window and type:

         $ifconfig 

Check the output to see which ethernet identifier out of eth0-eth9 is up. Then manually configure the IP address using:

         $ifconfig eth<0-9> 192.168.1.100 netmask 255.255.255.0 

To check the routing tables, type:

         $ route -n 

If a gateway is not present, then add the gateway:

         $route add default gw <IP address of Gateway> 

This should be done on both the Kiosk and the Ferry, but the IP addresses of the Kiosk and ferry should not be the same.

Example:
If you assigned 192.168.1.100 to the kiosk assign an IP like 192.168.1.101 to the ferry. The gateway for both will be the same however.

IP Configuration of the Gateway

Repeat the previous steps for the Gateway to initialize it with 192.168.1.1:

        $ifconfig eth<0-9> 192.168.1.1 netmask 255.255.255.0 

        $route -n

If the gateway does not show up, type:

        $route add default gw 192.168.1.1 

Test the connectivity between the nodes by pinging them from each other.

   kiosk$ping <Wired IP of the ferry> 

This should produce a valid response.Similarly it can be checked from all the nodes.

SSH connectivity to the nodes

Once the nodes have been configured, connect your own computer or laptop into the subnet and access the nodes through SSH.

         $ssh 192.168.1.1

Check if password-less SSH to the nodes works. If not, then copy the /root/.ssh/ folder into the node.

Wireless connectivity

The default wireless setting of the Kiosk and Ferry is to use Channel = 11, Essid = KioskNet. To make sure that the ferry associates with the kiosk, on the ferry do an ifconfig to check the wireless interface identifier -- this would appear as ath(0-9).

       $ifconfig 

Then type the following:

       $iwconfig ath(0-9) essid KioskNet

Check if it worked:

       $iwconfig

The output will show that the interface is in managed mode with the essid as KioskNet.

Throughput between the Kiosk and Ferry

To check the throughput between nodes, we use iperf. To install iperf on the nodes:

        $apt-get install iperf

Next, run the following on the kiosk:

        $iperf -s

And the following on the ferry:

       $iperf -c (IP address of the kiosk)

Hopping between Kiosk and Gateway for Testing

A script called essid_flipper is used to flip the ferry to connect alternately to the kiosk and gateway. It uses a configuration file, essid_flipper.conf, which can be obtained from the CVS.

Sample essid_flipper.conf file

VISUALIZATION=0
VISUALIZATION_SERVER=laptop
KIOSK_DURATION=180
KIOSK_TO_GATEWAY=190
GATEWAY_DURATION=180
GATEWAY_TO_KIOSK=190
IF_NAME="ath1"
KIOSK_ESSID="apurva"
GATEWAY_ESSID="apurvagw"
KIOSK_CHANNEL=11
GATEWAY_CHANNEL=11

Note that to get this to work, the essid of the gateway and kiosk will also have to be changed accordingly.

File transfer

To check for file transfer, copy a large file (about 10 MB) into the following folder:

         kiosk:/var/ocmp/client/<user name>/otube/upload/

When the ferry associates with the Kiosk, the file will be transferred to the ferry. When the ferry flips and associates with the Gateway, the file will be transferred to the gateway. Now, execute the dbstatus.ssh script on the gateway to check the status of data transferred.

This script access the Postgres database and returns the number of bundles transferred from the Kiosk to the ferry , from the ferry to the gateway, and from the gateway to the proxy. It also gives information about the acknowledgments received at each stage.

Return to deployment guide.