[hipl-users] Re: long delay in mobility handling procedure
- From: Szabolcs Nováczki <novaczkisz@xxxxxxxxx>
- To: hipl-users@xxxxxxxxxxxxx
- Date: Sat, 7 Mar 2009 13:26:43 +0100
Hi!
Well this is very useful and much more advanced than what we are doing but
anyway a simple solution which works also works:
*****************************************
tshark -i wlan0 -te -f "ip6 proto 0x8b" -R "ipv6.plen==216" >>
HO_stop_min0.224_max0.656_V.csv &
sleep 5
echo " //////////BEGIN/////////// "
for ((i=1; i < 100; i++))
do
iwconfig wlan0 essid ap1
ip -6 addr del xxxx:xxxx:xxxx:xxxx:219:d2ff:fe37:c2cf/64 dev wlan0
ip -6 route del default via fe80::213:20ff:fe20:7c4d dev wlan0
date +%s.%N >> HO_start_min1_max3_V.csv
echo "$i. HO: 2 to 1"
sleep 7
echo "-----------------------------------------------------"
iwconfig wlan0 essid ap2
ip -6 addr del xxxx:xxxx:xxxx:xxxx::219:d2ff:fe37:c2cf/64 dev wlan0
ip -6 route del default via fe80::214:4fff:fe2a:389 dev wlan0
date +%s.%N >> HO_start_min1_max3_V.csv
let i=i+1;
echo "$i. HO: 1 to 2"
sleep 7
echo "====================================================="
done
echo "//////////////END////////////"
*****************************************
Br,
Szabi
2009/3/6 Miika Komu <miika.komu@xxxxxxx>
> Szabolcs Nováczki wrote:
>
> Hi,
>
> you might be interested about earlier discussion thread on radvd from last
> year:
>
>
> //www.freelists.org/post/hipl-users/Got-RADVD-prefix-changing-working-but-without-hipfw,5
>
> HI!
>>
>> I'll share the script soon. We have some ideas how to improve it. We try
>> them and after i'll share it.
>>
>> We used different values for the radvd parameters.
>>
>> For help on radvd: man radvd.conf
>> no better i know
>>
>> 2009/3/6 Robert Moskowitz <rgm@xxxxxxxxxxxxxxx <mailto:
>> rgm@xxxxxxxxxxxxxxx>>
>>
>> Szabolcs Nováczki wrote:
>>
>> What we do is instead of waiting for the old address (and the
>> old default route!!!) to disappear we delete them manually (i.e.
>> with the script).
>>
>>
>> Can you share the script?
>>
>>
>> We configured radvd like:
>> MinRtrAdvInterval 1;
>> MaxRtrAdvInterval 3;
>> We also used other min-max combinations.
>>
>>
>> What do you mean by 'other min-max combinations'? Other values for
>> these parameters or other parameters?
>>
>> When I was getting RADVD set up back in August, I could not find any
>> advise or help with it.
>>
>>
>> 2009/3/6 Robert Moskowitz <rgm@xxxxxxxxxxxxxxx
>> <mailto:rgm@xxxxxxxxxxxxxxx> <mailto:rgm@xxxxxxxxxxxxxxx
>> <mailto:rgm@xxxxxxxxxxxxxxx>>>
>>
>> Szabolcs Nováczki wrote:
>>
>> All is IPv6. There are three different /64 networks. One
>> for
>> the cn and two for the mobile. The cn is attached on
>> wire. The
>> mobile is attched to one of the latter two sites through
>> wireless acces points and uses IPv6 stateless
>> autoconfiguration when receiving router advertisements to
>> configure its IP address. We use a script which periodically
>> changes (iwconfig new_ap) from one ap to the other and back.
>> The mobile reconfigures its ip address which triggers the
>> hip
>> update mechanism.
>>
>>
>> I am also running IPv6 and using RADVD for the addresses. I am
>> using separate vlans and right now just unplug a mobile from one
>> vlan port and plug it into another. I hope at some point to
>> have
>> a wireless setup, but vlaning and wireless typically means
>> separate SSIDs or multiple APs, this is why I am using the wired
>> approach for now.
>>
>> When I do switch ports, the old IPv6 address hangs in there for
>> a
>> little while, then goes away. By this time it seems the RVS
>> update has gone out. I can do some more testing and report
>> what I
>> see.
>>
>> BTW, here is one of my entries in radvd.conf:
>>
>> interface eth1.16
>> {
>> AdvSendAdvert on;
>> MinRtrAdvInterval 3;
>> MaxRtrAdvInterval 10;
>> prefix 2607:f4b8:3:3::/64
>> {
>> AdvOnLink off;
>> AdvAutonomous on;
>> AdvRouterAddr on;
>> AdvPreferredLifetime 20;
>> AdvValidLifetime 30;
>> };
>> route ::/0
>> {
>> };
>> };
>>
>>
>>
>>
>> 2009/3/6 Robert Moskowitz <rgm@xxxxxxxxxxxxxxx
>> <mailto:rgm@xxxxxxxxxxxxxxx>
>> <mailto:rgm@xxxxxxxxxxxxxxx <mailto:rgm@xxxxxxxxxxxxxxx>>
>> <mailto:rgm@xxxxxxxxxxxxxxx <mailto:rgm@xxxxxxxxxxxxxxx>
>>
>> <mailto:rgm@xxxxxxxxxxxxxxx <mailto:rgm@xxxxxxxxxxxxxxx>>>>
>>
>>
>>
>> Szabolcs Nováczki wrote:
>>
>> Hi hipl users!
>>
>> We are doing some tests with infraHIP recently.
>> With basic
>> mobility tests we run into the following behaviour:
>>
>> There is a significant delay in infraHIP (on the
>> mobile
>> side)
>> before sending out the first update package.
>>
>>
>> How do you create the mobility? What protocol
>> provides the
>> new IP
>> address? Is this IPv4 or IPv6?
>>
>>
>>
>> I attached a commented trace of the hipd output
>> (hipd_trace_medium) where I highlighted the
>> suspected part.
>>
>> My request is that if some of you has time to analyze
>> this or
>> someone knows the reason for this behaviour please
>> share with
>> us! What happenes there? Is this delay ok? We are
>> also
>> interested of mechanisms triggering the update
>> procedure in
>> hipd, and how this trigger is processed.
>>
>> Thx!
>>
>> Br,
>> Szabolcs Novaczki
>>
>> Ps.: hipd is running on 2.6.27-11 generic kernel
>> installed
>> from ubuntu interpid package
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Other related posts:
