[support] Re: AW: AW: AW: [dsmip] MR does not register IPv4 with HA

Romain KUNTZ kuntz at lsiit.u-strasbg.fr
Fri Aug 8 20:17:57 JST 2008


On 2008/08/08, at 13:07, Trinks, Marcus (K-EFFI) wrote:
> But unfortunately my MR does not receive a BAck from
> the HA. I attached the mip6d.log from the HA.  And I
> suppose these lines out of this log could explain you
> the problem!?
> 	Fri Aug  8 14:03:22 mh_bu_parse: Binding Update Received
> 	Fri Aug  8 14:03:22 ha_recv_bu_worker: NAT information: src  
> 192.168.2.33:666
> 	Fri Aug  8 14:03:22 ha_recv_bu_worker: CoA reported by MN  
> 0:0:0:0:0:ffff:c0a8:221
> 	Fri Aug  8 14:03:22 tunnel_mod: Trying to mod tunnel from  
> 0:0:0:0:0:ffff:c0a8:1 to 0:0:0:0:0:ffff:c0a8:221
> 	Fri Aug  8 14:03:22 tunnel_mod: modifying tunnel 8 end points with  
> from 192.168.0.1 to 192.168.2.33
> 	Fri Aug  8 14:03:22 MN (2001:1:1:0:0:0:0:1000) asked for TLV-format  
> UDP encap, but we don't offer support yet.

Did you use the "--enable-tlv" option at configure time when compiling  
mip6d on the MN? You should not use this option. As the log says, TLV  
option is not supported on the HA yet.

Cheers,
romain



> -----Ursprüngliche Nachricht-----
> Von: Romain KUNTZ [mailto:kuntz at lsiit.u-strasbg.fr]
> Gesendet: Freitag, 8. August 2008 12:44
> An: Trinks, Marcus (K-EFFI)
> Cc: dsmip at l2tp.nautilus6.org
> Betreff: Re: AW: AW: [dsmip] MR does not register IPv4 with HA
>
> On 2008/08/08, at 12:38, Trinks, Marcus (K-EFFI) wrote:
>> seems my mail came a little to late. This morning I started
>> troubleshooting again and activated IPv4 Forwarding on HA, MR
>> and the AR  in /proc/sys/net/ipv4/ip_forward.
>
> So does it mean that you HA now receives the BU from the MR ? :-)
>
> romain
>
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Romain KUNTZ [mailto:kuntz at lsiit.u-strasbg.fr]
>> Gesendet: Freitag, 8. August 2008 12:01
>> An: Trinks, Marcus (K-EFFI)
>> Cc: dsmip at l2tp.nautilus6.org
>> Betreff: Re: AW: [dsmip] MR does not register IPv4 with HA
>>
>> Hi Marcus,
>>
>> On 2008/08/07, at 11:39, Trinks, Marcus (K-EFFI) wrote:
>>> I used "decode as <IP>" within wireshark. Now I see the IPv6 BU
>>> packets
>>> on my MR. But none of the BU's arrive at the HA. Something with the
>>> IPv4 routing as Romain mentioned could be wrong. But I couldnt  
>>> figure
>>> out what yet. Find attached the Log-file of the HA.
>>
>> Ok, from the logs the HA does not receive any BU, so it is lost on  
>> the
>> MR-HA path. You should tcdump on both interfaces of the AR to check  
>> if
>> the packet is correctly received and forwarded. BTW did you activate
>> IPv4 forwarding on the AR via /proc?
>>
>>> I supposed there is no need for any routing entrys on the MR!?
>>
>> No, routing entries on the MR are automatically handled by UMIP.
>>
>>> Its strange, since I can ping both the 192.168.1.1 as well as the
>>> 192.168.2.1 but not the 192.168.0.1 from the HA when my MR is on
>>> Foreign
>>> Link 2 (eth1) of the Router of my network (refering to network  
>>> figure
>>> from previous mail).
>>
>> You mean that the HA cannot ping its own 192.168.0.1 address?
>> (BTW, I guess that the HA's eth2 on the figure is actually eth0?)
>>
>>> routing table HA:
>>> 192.168.2.0/24 dev eth0  scope link
>>> 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2
>>> 192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.1
>>>
>>> routing table Router:
>>> 192.168.2.0/24 dev eth1  proto kernel  scope link  src 192.168.2.1
>>> 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.1
>>> 192.168.0.0/24 via 192.168.1.2 dev eth0
>>
>> This sounds fine to me.
>>
>> Cheers,
>> -- 
>> Romain KUNTZ
>> kuntz at lsiit.u-strasbg.fr
>> LSIIT - Networks and Protocols Team
>> http://clarinet.u-strasbg.fr/~kuntz/
>>
>>
>
> -- 
> Romain KUNTZ
> kuntz at lsiit.u-strasbg.fr
> LSIIT - Networks and Protocols Team
> http://clarinet.u-strasbg.fr/~kuntz/
>
> <mip6d_dsmip.log>

-- 
Romain KUNTZ
kuntz at lsiit.u-strasbg.fr
LSIIT - Networks and Protocols Team
http://clarinet.u-strasbg.fr/~kuntz/



More information about the Support mailing list