Mobility experiments

De Ensiwiki
Aller à : navigation, rechercher
Project schedule.png
Titre du projet VoIP et Mobilité IPv6
Cadre Projets de spécialité
Page principale Projet de spécialité VoIP et Mobilité IPv6


In this part, you can observe some "typical" cases which illustrate our plateform and its running. For each situation we give you the initial state and after what we did and the results.

Remarks:

ha means "Home Agent", cn means "Correspondant Node" and mn means "Mobile Node". ha22 is the second HA in the second VLAN and ha13, for example, the first HA in the third VLAN.

Mobility with connexion loss

  • At the beginning, the MN (Mobile Node) is in its local network with a wire connexion.
  • You can ping (in IPv6 of course) the MN from an other hote like a CN (Correspondant Node).
  • Next, undock the connexion of MN and connect the MN to a stranger network (an other VLAN) in which there is an access point. If your network is well configure, the MN take the wireless connexion thanks to Wifi interface.

Results

When the MN takes and connects on the Wlan Wifi, there is:

   * Router advertisement reception by the MN
   * A Multicast listener 
   * Two neighbour solicitations for the MN 

(We note that the is illustrates by "from ::" which is used for the IPv6 phase receipt)

   * One Binding update from the tunneled interface to the "mother" HA (initial)
   * Neighbour sollicitation / advertisement
   * Binding update by the tunnel and its acceptance

By way of illustration, you can see the below woof:

    traceroute to mn22 (5f02::221:70ff:feb4:ae95) from 5f00::1, 30 hops max, 
    16 byte  packets
    1  ha22 (5f00::3)  0.195 ms  0.12 ms  0.115 ms
    2  mn22 (5f02::221:70ff:feb4:ae95)  47.488 ms  1.173 ms  1.166 ms
   (transported by the tunnel)


Mobility without connexion loss (part 1)

   * At the beginning, the MN (Mobile Node) is in its local network with a wire  
   connexion.
   * You can launch the MIPv6 tester application from the CN (which play the 
   server role) to the MN (which is the client). You must precise the remote host  
   adresse for each system.
   * Next, undock the connexion of MN and connect the MN to a stranger network 
   (an other VLAN) in which there is an access point. If your network is well configure, 
   the MN take the wireless connexion thanks to Wifi interface.

Results

The time that the MN takes and connects in the Wlan Wifi, there is a "handover":

By way of illustration, you can see the below woof from the CN:

   [11:02:50] Configuration: "Default"
   [11:02:50] Start tester
   [11:02:50] Start udp server
   [11:02:50] Start tcp server
   [11:02:50] Start udp client
   [11:02:50] Start udpunbound server
   [11:02:50] Start udpunbound client
   [11:03:28] [UDPUNBOUND] Handover detected at 11:03:28
   [11:03:29] [UDPUNBOUND] Last handover duration: 1.404  <<---
   [11:03:33] [UDP] Handover detected at 11:03:33
   [11:03:33] [TCP] Handover detected at 11:03:33
   [11:03:33] [UDPUNBOUND] Handover detected at 11:03:33
   [11:03:34] [UDPUNBOUND] Last handover duration: 1.229  <<---
   [11:03:34] [TCP] Last handover duration: 1.235         <<---
   [11:03:34] [UDP] Last handover duration: 1.309         <<---
   [11:04:28] Stop tester


Mobility without connexion loss (part 2)

   * At the beginning, the MN (Mobile Node) is a foreign network with 
   a wire connexion.
   * You can launch the MIPv6 tester application from the CN (server role) 
   to the MN (which is the client). You must precise the remote host adresse 
   for each system.
   * Next, connect the host to the Wan Wifi in an other VLAN. Then, undock the 
   wire connexion of MN. 

Résults

   [15:41:50] Configuration: "Default"
   [15:41:50] Start tester
   [15:41:50] Start udp client
   [15:41:50] Start udp server
   [15:41:50] Start tcp server
   [15:41:50] Start udpunbound client
   [15:41:50] Start udpunbound server
   [15:42:12] [UDPUNBOUND] Handover detected at 15:42:12
   [15:42:12] [TCP] Handover detected at 15:42:12
   [15:42:12] [TCP] Last handover duration: 0.006             <<----
   [15:42:12] [UDPUNBOUND] Last handover duration: 0.006
   [15:42:22] [UDP] Handover detected at 15:42:22
   [15:42:22] [UDPUNBOUND] Handover detected at 15:42:22
   [15:42:22] [TCP] Handover detected at 15:42:22
   [15:42:23] [UDP] Last handover duration: 0.348             <<----
   [15:42:23] [UDPUNBOUND] Last handover duration: 0.356
   [15:42:23] [UDP] Handover detected at 15:42:23
   [15:42:23] [UDPUNBOUND] Handover detected at 15:42:23
   [15:42:26] [UDPUNBOUND] Last handover duration: 2.971      <<----
   [15:42:26] [UDP] Last handover duration: 2.982             <<----
   [15:42:29] [TCP] Last handover duration: 6.308             <<----
   [15:42:45] Start tcp server
   [15:42:45] [UDP] Handover detected at 15:42:45
   [15:42:45] [UDPUNBOUND] Handover detected at 15:42:45
   [15:42:50] Stop tester

   [15:52:07] Configuration: "Default"
   [15:52:07] Start tester
   [15:52:07] Start udpunbound server
   [15:52:07] Start udp client
   [15:52:07] Start udp server
   [15:52:07] Start tcp server
   [15:52:07] Start udpunbound client
   [15:52:14] [UDP] Handover detected at 15:52:14 
   [15:52:14] [UDPUNBOUND] Handover detected at 15:52:14
   [15:52:14] [TCP] Handover detected at 15:52:14
   [15:52:15] [UDP] Last handover duration: 0.346         <<----
   [15:52:15] [UDPUNBOUND] Last handover duration: 0.366
   [15:52:15] [TCP] Last handover duration: 0.587         <<----
   [15:52:21] Start tcp server
   [15:52:21] [UDPUNBOUND] Handover detected at 15:52:21
   [15:52:21] [UDP] Handover detected at 15:52:21
   [15:52:27] Stop tester

Remarks: In a nutshell, we observe that the TCP handover is longer than the UDP or UDPUNBOUND handover. Indeed, in TCP there is congestion control and some mechanisms which allow to save datas and send it in order. At the opposite, in UDP there is no control.

Mobility without connexion loss in Wifi

   * At the beginning, the MN (Mobile Node) is in a foreign network with 
   a wireless connexion.
   * You can launch the MIPv6 tester application from the CN (server role) 
   to the MN (which is the client). You must precise the remote host adresse 
   for each system.
   * Next, connect the host to the Wan Wifi in an other VLAN. Then, undock the 
   first access point to simulate the access point border.

Results: (click Dérouler to expand)