[support] DAD Delay too high?
support at adhari.de
support at adhari.de
Tue Sep 29 18:47:46 JST 2009
Hi arno, Thanks for taking out time for so much support from your side.
the tipp with the Radvd Version was good, I measured better values in the Router discovery delay.
But the DAD Delay, I still have the same Problem. I made new 450 tests and had again an average of 2,95 seconds between the first NSsent and the BU.
Any other Ideas?
Hakim
-----UrsprünglicheNachricht-----
Hi,
support at adhari.de writes:
> I performed the same tests on a fresh installedSystem (debian /kernel 2.6.31)
> Only MIP6 Support without NEMO or MCOA patches.Istill have too high
> DAD delays (delay between the first NeighborhoodSolicitation and the
> HomeAgent registration.)
>
> I made about 300 tests and had an average value of2,95 seconds.
>
> Look at this case for example:The first Neighborsolicitation was sent
> at time 12.556429 and the Binding update more than 3seconds later at
> 15.920365
>
> Any Idea?
Maybe. Are you using Debian unstable radvd > 1.2(probably 1.3) which is
broken. See the discussion here:
http://lists.litech.org/pipermail/radvd-devel-l/2009-July/thread.html
> 00:59:10.856905 fe80::201:2ff:fe1a:d2be ->ff02::1 ICMPv6 Router advertisement
> 00:59:10.859420 :: ->ff02::16 ICMPv6 Multicast ListenerReport Message v2
> 00:59:10.947435 :: ->ff02::2 ICMPv6 Router solicitation
> 00:59:10.948423 :: ->ff02::16 ICMPv6 Multicast ListenerReport Message v2
> 00:59:11.369853 2001:a:b::1 ->2001:a:b::1000 ICMPv6 Echo request
> 00:59:11.370763 2001:a:b::1000 ->2001:a:b::1 ICMPv6 Echo reply
> 00:59:11.528376 :: ->ff02::1:ff1d:b521 ICMPv6Neighbor solicitation
> 00:59:12.454521 :: ->ff02::2 ICMPv6 Router solicitation
> 00:59:12.537394 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
> 00:59:12.537802 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
> 00:59:12.538302 fe80::201:2ff:fea7:a651 -> ff02::1 ICMPv6 Router advertisement
> 00:59:12.538851 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
> 00:59:12.539392 :: ->ff02::16 ICMPv6 Multicast ListenerReport Message v2
> 00:59:12.539418 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
> 00:59:12.556429 :: ->ff02::1:ff1d:b521 ICMPv6Neighbor solicitation
> 00:59:12.630719 :: ->ff02::2 ICMPv6 Router solicitation
> 00:59:13.148431 :: ->ff02::1:ff1d:b521 ICMPv6 Neighborsolicitation
> 00:59:13.370432 2001:a:b::1 ->2001:a:b::1000 ICMPv6 Echo request
> 00:59:13.618430 fe80::216:6fff:fe1d:b521 ->ff02::16 ICMPv6 Multicast ListenerReport Messagev2
> 00:59:14.370462 2001:a:b::1 ->2001:a:b::1000 ICMPv6 Echo request
> 00:59:15.370475 2001:a:b::1 ->2001:a:b::1000 ICMPv6 Echo request
> 00:59:15.916589 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
> 00:59:15.917068 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
> 00:59:15.917439 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
> 00:59:15.917936 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
> 00:59:15.918380 :: ->ff02::16 ICMPv6 Multicast ListenerReport Message v2
> 00:59:15.920365 2001:a:b::1 ->2001:a:b::1000 MIPv6 Binding Update
In fact, the BU is triggered 0.01 sec after receiving theRA (one in
the set of 4 RA).
I was hit by that same bug last week. I reinstalleddowngraded my radvd
to version 1.2.
Cheers,
a+
-----UrsprünglicheNachricht-----
Von: support-bounces at jules.nautilus6.org[mailto:support-bounces at jules.nautilus6.org] Im Auftrag von support at adhari.de
Gesendet: Montag, 21. September 2009 09:51
An: support at jules.nautilus6.org; arno at natisbad.org
Cc: faqir.yousaf at uni-dortmund.de
Betreff: [support] DAD Delay too high?
Hi Arnaud,
I performed the same tests on a fresh installed System(debian /kernel 2.6.31)
Only MIP6 Support without NEMO or MCOA patches.I stillhave too high DAD delays (delay between the first Neighborhood Solicitation andthe HomeAgent registration.)
I made about 300 tests and had an average value of2,95 seconds.
Look at this case for example:The first Neighborsolicitation was sent at time 12.556429 and the Binding update more than 3seconds later at 15.920365
Any Idea?
Merci beaucoup
Hakim
00:59:10.856905 fe80::201:2ff:fe1a:d2be ->ff02::1 ICMPv6 Router advertisement
00:59:10.859420 :: ->ff02::16 ICMPv6 Multicast ListenerReportMessage v2
00:59:10.947435 :: ->ff02::2 ICMPv6 Router solicitation
00:59:10.948423 :: ->ff02::16 ICMPv6 Multicast ListenerReportMessage v2
00:59:11.369853 2001:a:b::1 ->2001:a:b::1000ICMPv6 Echo request
00:59:11.370763 2001:a:b::1000 -> 2001:a:b::1 ICMPv6 Echo reply
00:59:11.528376 :: ->ff02::1:ff1d:b521 ICMPv6 Neighbor solicitation
00:59:12.454521 :: ->ff02::2 ICMPv6 Router solicitation
00:59:12.537394 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:12.537802 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:12.538302 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:12.538851 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:12.539392 :: ->ff02::16 ICMPv6 Multicast ListenerReportMessage v2
00:59:12.539418 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:12.556429 :: ->ff02::1:ff1d:b521 ICMPv6 Neighbor solicitation
00:59:12.630719 :: ->ff02::2 ICMPv6 Router solicitation
00:59:13.148431 :: ->ff02::1:ff1d:b521 ICMPv6 Neighbor solicitation
00:59:13.370432 2001:a:b::1 ->2001:a:b::1000ICMPv6 Echo request
00:59:13.618430 fe80::216:6fff:fe1d:b521 ->ff02::16 ICMPv6 Multicast Listener Report Messagev2
00:59:14.370462 2001:a:b::1 ->2001:a:b::1000ICMPv6 Echo request
00:59:15.370475 2001:a:b::1 ->2001:a:b::1000ICMPv6 Echo request
00:59:15.916589 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:15.917068 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:15.917439 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:15.917936 fe80::201:2ff:fea7:a651 ->ff02::1 ICMPv6 Router advertisement
00:59:15.918380 :: ->ff02::16 ICMPv6 Multicast ListenerReportMessage v2
00:59:15.920365 2001:a:b::1 ->2001:a:b::1000MIPv6 Binding Update
I adjusted my configurationfiles Here aremy configuration files:
*********MobileNode*************
--------mip6d.conf:----------
NodeConfig MN;
DebugLevel 10;
DoRouteOptimizationCN disabled;
DoRouteOptimizationMN disabled;
UseCnBuAck disabled;
OptimisticHandoff disabled;
MnRouterProbes 0;
MnRouterProbeTimeout 0.02;
MnMaxHaBindingLife 60;
Interface "eth1" {
MnIfPreference 1;
}
MnHomeLink "eth1" {
HomeAgentAddress 2001:a:b:0::1000;
HomeAddress2001:a:b:0::1/64(2001:a:b:1::/64); }
UseMnHaIPsec disabled;
KeyMngMobCapability disabled;
*********HomeAgent*************
--------mip6d.conf:----------
NodeConfig HA;
DebugLevel 10;
Interface "eth1";
UseMnHaIPsec disabled;
KeyMngMobCapability disabled;
--------Radvd.conf----------
interface eth1
{
AdvSendAdverton;
MaxRtrAdvInterval 0.07;
MinRtrAdvInterval 0.03;
AdvIntervalOpton;
AdvHomeAgentFlag on;
AdvHomeAgentInfo on;
HomeAgentLifetime 1800;
HomeAgentPreference 10;
AdvMobRtrSupportFlag on;
prefix2001:a:b:0::1000/64
{
AdvRouterAddr on;
AdvOnLink on;
AdvAutonomous on;
};
};
*********ForeignRouter************* (the MN tryes toconnect to this Router)
--------Radvd.conf----------
interface eth3
{
AdvSendAdverton;
MaxRtrAdvInterval 0.07;
MinRtrAdvInterval 0.03;
AdvIntervalOpton;
prefix2001:a:f2:1::1/64
{
AdvRouterAddr on;
AdvOnLink on;
AdvAutonomous on;
};
};
Hi,
support at adhari.de writes:
> Hi Arnaud,
>
> I´m not sure if this problem have something to dowith the
> DADRetransTimer. But I don´t know where to checkthis setting in order
> to exclude this possibilty.
>
> Here are my configuration files:
>
> *********MobileNode*************
>
> --------mip6d.conf:----------
>
> NodeConfigMN;
> DebugLevel 10;
> DoRouteOptimizationCN disabled;
> DoRouteOptimizationMN disabled;
> UseCnBuAckdisabled;
>
> OptimisticHandoff disabled;
> MnRouterProbes 0;
> MnRouterProbeTimeout 0.02;
> MnMaxHaBindingLife 60;
>
> Interface"eth1" {
> Bid 100;
> BidPriority10;
> Reliabletrue;
MCoA patch applied? Can you try w/o it to see if this isrelated?
a+
_______________________________________________
Support mailing list
Support at ml.nautilus6.org
http://ml.nautilus6.org/mailman/listinfo/support
More information about the Support
mailing list