Changes between Version 7 and Version 8 of HandoverTestbed


Ignore:
Timestamp:
09/30/15 16:38:18 (9 years ago)
Author:
ljw725@gmail.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • HandoverTestbed

    v7 v8  
    1313
    1414[[Image(up-ovs.jpg, align=center)]]
     15
    1516Figure (2) Bring up OVS
    1617
    … …  
    1920
    2021[[Image(ovs-show.jpg, align=center)]]
     22
    2123Figure (3) OVS Configuration
    2224
    … …  
    2628
    2729[[Image(initial-flow.jpg, align=center)]]
     30
    2831Figure (4) Initial Flow Entries for WiFi in OVS
    2932
    … …  
    3134
    3235[[Image(ip-brtap.jpg, align=center)]]
     36
    3337Figure (5) IP of br_tap
    3438
    35397. Run script “add_default_route.sh” to set br_tap as the default interface for all application packets. The correct routing table setting is shown in Figure (6).
    3640
     41[[Image(route-n.jpg, align=center)]]
    3742
    38 Figure (5) IP Routing Table
     43Figure (6) IP Routing Table
    3944
    40458. Now you are all set for the configuration. As mentioned above, we set WiFi as the networking being used in the beginning. Then, to switch to WiMAX network, you only need to run the script “switch_from_wifi_to_wmax.sh”. After this, to switch back to WiFi again, you can run script “switch_from_wmax_to_wifi.sh”.  Figure (6) illustrates two transparent handover. First, at icmp_req=17, we switch to WiMAX. After this, we see that the RTT increases to around 100ms, which represents the WiMAX. Second, at icmp_req=27, we switch back to WiFi. After this, the RTT falls to around 25ms, which represents the WiFi.
    4146
     47[[Image(switch.jpg, align=center)]]
    4248
    43 Figure (6) Switch to WiMax and then back to WiFi
     49Figure (7) Switch to WiMax and then back to WiFi
    4450
    4551'''Part II: Doing an Experiment'''