[support] Destination Unreachable for BU

Sebastien Decugis sdecugis at hongo.wide.ad.jp
Fri Oct 3 10:29:44 JST 2008


Hello,

Sorry my previous mail was not clear. I did not mean the TCPdump logs, 
but the messages issued by the mip6d daemon itself.
To get verbose output with the daemon, you may check the debug level in 
the configuration file or "-d" command-line option.

Sebastien.

Chulhyun Park a écrit :
> Here's the tcpdump at HA. eth1 is HA's interface that is connected to Router.
> I cannot see any packets dumped for eth2, which is linked to the Home Link..
>
> In this case, I cannot see 'destination unreachable' ICMPv6 reply, but
> still HA shows no action about the BU.
> Is there any checking point to trace the BU packet?
>
> [root at ha ~]# tcpdump ip6 -i eth1
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
> 08:34:58.274396 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:34:59.418423 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:00.710656 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:03.215054 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:04.438869 IP6 2001:a:d:1:2c0:95ff:fee0:bac9 > 2001:a:f:1::1000:
> DSTOPT mobility: BU seq#=25875 AH lifetime=20
> 08:35:04.591042 IP6 2001:a:c:1:2c0:95ff:fee0:bac8 > 2001:a:f:1::1000:
> DSTOPT mobility: BU seq#=37046 AH lifetime=20
> 08:35:04.855974 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:05.943006 IP6 2001:a:c:1:2c0:95ff:fee0:bac8 > 2001:a:f:1::1000:
> DSTOPT mobility: BU seq#=25876 AH lifetime=20
> 08:35:06.010897 IP6 2001:a:c:1:2c0:95ff:fee0:bac8 > 2001:a:f:1::1000:
> DSTOPT mobility: BU seq#=37047 AH lifetime=20
> 08:35:06.251900 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:08.568161 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:08.947356 IP6 2001:a:c:1:2c0:95ff:fee0:bac8 > 2001:a:f:1::1000:
> DSTOPT mobility: BU seq#=25877 AH lifetime=20
> 08:35:09.015282 IP6 2001:a:c:1:2c0:95ff:fee0:bac8 > 2001:a:f:1::1000:
> DSTOPT mobility: BU seq#=37048 AH lifetime=20
> 08:35:09.439146 IP6 fe80::2c0:95ff:fee0:c44c > 2001:a:e:1::1000:
> ICMP6, neighbor solicitation, who has 2001:a:e:1::1000, length 32
> 08:35:09.439264 IP6 2001:a:e:1::1000 > fe80::2c0:95ff:fee0:c44c:
> ICMP6, neighbor advertisement, tgt is 2001:a:e:1::1000, length 24
> 08:35:11.240163 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:13.663655 IP6 2001:a:c:1:2c0:95ff:fee0:bac8 > 2001:a:f:1::1000:
> DSTOPT mobility: BU seq#=25878 AH lifetime=0
> -> I stopped mip6d at MR at this point, so the MR de-registered the
> binding by setting lifetime.
> 08:35:14.240667 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:14.436077 IP6 fe80::20e:e8ff:fef8:8dc1 >
> fe80::2c0:95ff:fee0:c44c: ICMP6, neighbor solicitation, who has
> fe80::2c0:95ff:fee0:c44c, length 32
> 08:35:14.436187 IP6 fe80::2c0:95ff:fee0:c44c >
> fe80::20e:e8ff:fef8:8dc1: ICMP6, neighbor advertisement, tgt is
> fe80::2c0:95ff:fee0:c44c, length 24
> 08:35:15.664814 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:17.601113 IP6 fe80::2c0:95ff:fee0:c44c > ff02::1: ICMP6, router
> advertisement, length 72
> 08:35:19.436595 IP6 fe80::2c0:95ff:fee0:c44c >
> fe80::20e:e8ff:fef8:8dc1: ICMP6, neighbor solicitation, who has
> fe80::20e:e8ff:fef8:8dc1, length 32
> 08:35:19.436629 IP6 fe80::20e:e8ff:fef8:8dc1 >
> fe80::2c0:95ff:fee0:c44c: ICMP6, neighbor advertisement, tgt is
> fe80::20e:e8ff:fef8:8dc1, length 24
>
> 24 packets captured
> 48 packets received by filter
> 0 packets dropped by kernel
> [root at ha ~]#
>
>
>
> 2008/10/2 Sebastien Decugis <sdecugis at hongo.wide.ad.jp>:
>   
>> Hmmm ok.
>>
>> It might be useful if you send us your traces from the HA mip6d daemon...
>>
>> Sebastien.
>>
>> Chulhyun Park a écrit :
>>     
>>> Thanks Sebastien.
>>>
>>> As you assumed, 2001:a:f:1::1000 is assigned to HA's eth2, and ipv6
>>> forwarding is activated also.
>>> Radvd runs on the HA, so if I radvdump at HA, I can see RA with
>>> 2001:a:f:1::/64 prefix at eth2.
>>>
>>> I tried ping from both AR1 and AR2 to 2001:a:f:1::1000, and it works.
>>> So it seems that connectivity between machines is not the reason of
>>> the problem...
>>>
>>> 2008/10/2 Sebastien Decugis <sdecugis at hongo.wide.ad.jp>:
>>>
>>>       
>>>> Hello,
>>>>
>>>> Does the RA daemon (radvd) runs on your HA?
>>>> I assume that the 2001:a:f:1::1000 address is actually configured on your
>>>> HA's eth2 interface. Did you also activate IPv6 forwarding? Without your
>>>> mip6d daemon running, can you ping your HA address (2001:a:f:1::1000)
>>>> from
>>>> your AR1 or AR2?
>>>>
>>>> Hope these checks will help you solving your problem...
>>>>
>>>> Best regards,
>>>> Sebastien.
>>>>
>>>>
>>>> Chulhyun Park a écrit :
>>>>
>>>>         
>>>>> Hi. I'm Park.
>>>>> I'm suffering from the problem that HA doesn't recognize bu from MR.
>>>>> The test network diagram is like below.
>>>>>
>>>>>
>>>>>
>>>>>        MNN1                  MNN2
>>>>>         |                      |
>>>>>         +---------+  +---------+
>>>>>  MNP1               |  | MNP2
>>>>>  2001:a:f:2::/64    |  | 2001:a:f:3::/64
>>>>>                   |  |
>>>>>                    MR
>>>>>                   |  |
>>>>>  Access Network 1   |  |  Access network 2
>>>>>  2001:a:c:1::/64    |  |  2001:a:d:1::/64
>>>>>                   |  |
>>>>>             +-----+  +-----+
>>>>>             |              |
>>>>>            AR1            AR2
>>>>>             |              |
>>>>>             +-----+  +-----+
>>>>>  2001:a:a:1::/64    |  |  2001:a:a:2::/64
>>>>>                  Router
>>>>>                   |  |
>>>>>  2001:a:e:1::/64    |  |  2001:b:a:1::/64
>>>>>             +-----+  +-----+
>>>>>             |              |
>>>>>             HA             CN
>>>>>  HA's ETH2 |
>>>>>         ----+----- Home Link : 2001:a:f:1::/64
>>>>>
>>>>>
>>>>> MR has four interfaces, two are connected to two separated mobile
>>>>> network,
>>>>> and two are connected to different two access networks, access network 1
>>>>> and 2.
>>>>>
>>>>> When MR boots up at the foreign network, it recognizes that it is in
>>>>> foreign network
>>>>> and sends two binding updates to HA (2001:a:f:1::1000) for each CoA
>>>>> from AN1 and AN2.
>>>>> But HA cannot receive any binding updates from the MR.
>>>>>
>>>>> I tried to tcpdump packet at all machines, AR1 or AR2 and Router and HA.
>>>>> I could find binding update packets destined to the HA
>>>>> (2001:a:f:1::1000), even at the HA itself.
>>>>> Moreover, I also could see ICMPv6 destination address unreachable
>>>>> message from HA to a CoA of MR.
>>>>> HA can ping to the CoA of the MR, and as I connected another machine
>>>>> beyond AR1 then
>>>>> from that machine I also can ping to the HA. So it doesn't seem to be
>>>>> a routing problem.
>>>>>
>>>>> I included my configuration for HA and MR. Would you find a problem
>>>>> with my configuration?
>>>>>
>>>>> -----------------
>>>>>  HA mip6d.conf
>>>>> -----------------
>>>>>
>>>>> NodeConfig HA;
>>>>> DebugLevel 1;
>>>>> Interface "eth2";
>>>>> HaAcceptMobRtr enabled;
>>>>> HaAcceptMCoAReg enabled;
>>>>>
>>>>>
>>>>> # Disable MPS/MPA
>>>>> SendMobPfxAdvs enabled;
>>>>> SendUnsolMobPfxAdvs enabled;
>>>>>
>>>>> # MNP configuration
>>>>> HaServedPrefix 2001:a:f:1::/64;
>>>>> BindingAclPolicy 2001:a:f:1::1 (2001:a:f:2::/64, 2001:a:f:3::/64)
>>>>> MCoAReg
>>>>> allow;
>>>>> DefaultBindingAclPolicy allow;
>>>>>
>>>>>
>>>>> # IPsec configuration - NO IPSEC AT THE MOMENT
>>>>> UseMnHaIPsec disabled;
>>>>> KeyMngMobCapability disabled;
>>>>>
>>>>> # EOF
>>>>>
>>>>>
>>>>>
>>>>> -----------------
>>>>>  MR mip6d.conf
>>>>> -----------------
>>>>>
>>>>> NodeConfig MN;
>>>>> DebugLevel 10;
>>>>> DoRouteOptimizationCN disabled;
>>>>> DoRouteOptimizationMN disabled;
>>>>> SendMobPfxSols enabled;
>>>>> UseCnBuAck enabled;
>>>>>
>>>>> # We use Explicit Mode
>>>>> MobRtrUseExplicitMode enabled;
>>>>> OptimisticHandoff enabled;
>>>>>
>>>>> # The Binding Lifetime, for example 20 seconds
>>>>> MnMaxHaBindingLife 20;
>>>>>
>>>>> Interface "eth0" {
>>>>>   Bid 100;
>>>>>   BidPriority 20;
>>>>>   Reliable true;
>>>>> }
>>>>>
>>>>>
>>>>> Interface "eth1" {
>>>>>   Bid 101;
>>>>>   BidPriority 10;
>>>>>   Reliable true;
>>>>> }
>>>>>
>>>>> # Replace eth0 with your egress interface
>>>>> MnHomeLink "eth0" {
>>>>>   IsMobRtr enabled;
>>>>>   HomeAgentAddress 2001:a:f:1::1000;
>>>>>   HomeAddress 2001:a:f:1::1/64 (2001:a:f:2::/64, 2001:a:f:3::/64);
>>>>>   RegMultipleCoA enabled;
>>>>>   IfMultipleCoA "eth0", "eth1";
>>>>> }
>>>>>
>>>>> # IPsec configuration - NO IPSEC AT THE MOMENT
>>>>> UseMnHaIPsec disabled;
>>>>> KeyMngMobCapability disabled;
>>>>> # EOF
>>>>>
>>>>>
>>>>> Chulhyun Park, Ph.D Student
>>>>> Multimedia and Mobile Communication Lab.
>>>>> _______________________________________________
>>>>> Support mailing list
>>>>> Support at ml.nautilus6.org
>>>>> http://ml.nautilus6.org/mailman/listinfo/support
>>>>>
>>>>>
>>>>>
>>>>>           
>>>> _______________________________________________
>>>> Support mailing list
>>>> Support at ml.nautilus6.org
>>>> http://ml.nautilus6.org/mailman/listinfo/support
>>>>
>>>>
>>>>         
>>>       
>
>   



More information about the Support mailing list