[ns] handover mipv6

[Aris Suyudi]

Hi Przmek thanks for your response

I already installed ns-2.1b6 and mobiwan,
Then I run the sample of ns-simple.tcl from site
http://www.ti-wmc.nl/mobiwan2/ and got result output like this (with
little modification):



[root at localhost aries]# ns simple-mipv6.tcl

  >-------------------- NS Addressing --------------------<
  Domains (domain_num) : 2
  Clusters (cluster_num) : 1 5
  Nodes (nodes_num) :  1 1 3 1 1 1
  >-------------------------------------------------------<

Simulation finished

|Binding Update List for node 1.1.1 at 100
--------------------------------------- |
|Node           COA             Type    Info    Flag    Last    Time
Life     Expire          Nb|
|1.1.0          1023.2047.2047          3       HA      1       -1
-1     02.68435e+08             0 |


I didn't think this output is valid coz this output is different from
the site http://www.ti-wmc.nl/mobiwan2/ 

Do you think this sample is not work for mobiwan in ns-2.1b6 ? or need
more modification to get same result with the site belongs ?.

Note : I changed in the top of script 
Agent/MIPv6/MN set bs_forwarding_     0 with this script :
Agent/MN set bs_forwarding_     0


Thanks in advance

Aries
 

-----Original Message-----
From: Przemek Machan [mailto:przemac-ns at o2.pl] 
Sent: Wednesday, June 15, 2005 02:45
To: Aris Suyudi; ns-users at ISI.EDU
Subject: RE: [ns] handover mipv6


Hello,
Handover in Mobiwan works roughly as follows. There are two methods to
detect movement to a new MiPv6 Agent:
- MN maintains timer for each Agent. Each timer is updated on every
router
advertisement received from related Agent. When the timer expires MN
sends
router solicitation and waits for router advertisements.
- MH simply assumes that it moves to a new domain if it receives router
advertisement from a new Agent.

When MN receives router advertisement from a new BS, MN generates a new
COA.


The COA is generated as Agent hierarchial address prefix and node id
suffix.
For example if Agent address is 2.0.0 and node id is 4, the COA
generated by
MN for this Agent will be 2.0.4.


BTW, you can use mobiwan over ns-2.28. Use the patch below on clean
ns-2.28
sources (patch -p1 -u <ns-228-mobiwan-102.diff), run configure and make:
http://www.kolonianet.pl/przemac/ns-228-mobiwan-102.diff.gz 

You can find simple mobiwan script for ns-2.2{6,7,8} here:
http://www.ti-wmc.nl/mobiwan2/


Regards,
Przemek





-----Original Message-----
From: ns-users-bounces at ISI.EDU [mailto:ns-users-bounces at ISI.EDU] On
Behalf
Of Aris Suyudi
Sent: Tuesday, June 14, 2005 4:58 AM
To: ns-users at ISI.EDU
Subject: [ns] handover mipv6




Hai ns-users

I just did install ns 2.1b6 and mobiwan and now I'm trying to learn
handover
between 2 subnet. I want to know about when Mobile node move from one
Base
station to another (base station I put in 2 different router). Is mobile
node can get their COA from visited Base Station automatically ? or I
have
to make script to simulate them...? I read from tutorial by thiery
Ernst,
but I still couldn't understand. I would appreciated if someone can give
me
a simple script that explain about handover between two Base station
(IPv6).



My topology :

CN ----  R1 ---------  R2
      //   \\       //   \\
   BS1      BS2    BS3   BS4

O ----------------- o
Mobile_ move from BS1 to BS4


Thanks in advance for your response

Aries


--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.6.9 - Release Date: 2005-06-11
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.6.9 - Release Date: 2005-06-11