[support] HA and MR are unable to recognize NEMO packet
zze-ALLOVON Etienne RD-RESA-ISS
etienne.allovon at orange-ftgroup.com
Tue Oct 23 18:24:08 JST 2007
Hello,
We already had some problems of ICMPv6 Unreachable packets on our platform : our MR was on Debian and our HA on Fedora Core 6.
I noticed in your "ip -6 route show table 0" entries this route :
"unreachable default dev lo table unspec proto none metric -1 error -101 hoplimit 255"
that I noticed also on our HA. This route appeared occasionally and I never found with what it was linked.
It seems that this route entry break the routing process. And I never managed to remove these entries.
I thought it was due to a misconfiguration of the network on the HA.
Therefore, because I'm not that familiar with the configuration files of Fedora, I installed the HA on Debian and the problem was resolved.
Thus I write simply this message to confirm that I already had this problem with Fedora and to indicate a work around which corrected the problem for us.
But I repeat that I think it's mainly due to the fact that I'm more familiar with the way of configuring the network on Debian and that if you want to use Fedora, you should check carefully your network configuration (as others already said).
Regards,
Etienne
-----Message d'origine-----
De : support-bounces at ml.nautilus6.org [mailto:support-bounces at ml.nautilus6.org] De la part de Rahman, Md Sazzadur
Envoyé : mardi 23 octobre 2007 10:02
À : Support ML; Support ML
Objet : RE: [support] HA and MR are unable to recognize NEMO packet
I am attaching routing table logs here further for HA: Please let me know if anything seems to be incorrect:
route -A inet6
---------------
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
[UNKNOWN]/64 * U 256 0 0 eth1
[UNKNOWN]/64 [UNKNOWN] UG 1 0 0 eth1
[UNKNOWN]/128 [UNKNOWN] UC 0 12 0 eth0
[UNKNOWN]/64 * U 256 1 0 eth0
[UNKNOWN]/64 [UNKNOWN] UG 1 0 0 eth0
[UNKNOWN]/64 * U 256 0 0 eth1
[UNKNOWN]/64 * U 256 0 0 eth0
localhost.localdomain/128 * U 0 161 1 lo
[UNKNOWN]/128 * U 0 0 2 lo
[UNKNOWN]/128 * U 0 79 1 lo
[UNKNOWN]/128 * U 0 0 2 lo
[UNKNOWN]/128 * U 0 0 2 lo
[UNKNOWN]/128 * U 0 38 1 lo
[UNKNOWN]/128 * U 0 0 2 lo
[UNKNOWN]/128 * U 0 0 2 lo
[UNKNOWN]/128 * U 0 171 1 lo
[UNKNOWN]/128 * U 0 0 1 lo
[UNKNOWN]/128 [UNKNOWN] UC 0 591 0 eth0
[UNKNOWN]/128 [UNKNOWN] UC 0 1020 0 eth1
[UNKNOWN]/8 * U 256 0 0 eth1
[UNKNOWN]/8 * U 256 0 0 eth0
ip -6 rule
-----------
0: from all lookup local
1005: from all lookup 252
32766: from all lookup main
sysctl -a | grep ipv6 | grep forwarding
--------------------------------------
net.ipv6.conf.lo.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.sit0.forwarding = 1
net.ipv6.conf.ip6tnl0.forwarding = 1
net.ipv6.conf.eth0.forwarding = 1
net.ipv6.conf.eth1.forwarding = 1
ip -6 route show table 0
-------------------------
unreachable default dev lo table unspec proto none metric -1 error -101 hoplimit 255 unreachable ::/96 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
2001:a:b::/64 dev eth1 metric 256 expires 21332019sec mtu 1500 advmss 1440 hoplimit 4294967295
2001:a:b:1::/64 via fe80::250:4ff:fe6f:ba14 dev eth1 metric 1 expires 21332019sec mtu 1500 advmss 1440 hoplimit 4294967295
2001:a:c:1:250:4ff:fe6f:ba14 via 2001:a:c:1:250:4ff:fe6f:ba14 dev eth0 metric 0
cache mtu 1500 advmss 1440 hoplimit 4294967295
2001:a:c:1::/64 dev eth0 metric 256 expires 21332019sec mtu 1500 advmss 1440 hoplimit 4294967295
2001:a:d:1::/64 via 2001:a:c:1::1 dev eth0 metric 1 expires 21332019sec mtu 1500 advmss 1440 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 expires 21330835sec error -101 mtu 16436 advmss 16376 hoplimit 4294967295
fe80::/64 dev eth1 metric 256 expires 21332019sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 21332019sec mtu 1500 advmss 1440 hoplimit 4294967295 unreachable default dev lo table unspec proto none metric -1 error -101 hoplimit 255 local ::1 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local 2001:a:b:: via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local 2001:a:b::1000 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local 2001:a:b:0:fdff:ffff:ffff:fffe via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local 2001:a:c:1:: via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local 2001:a:c:1::1000 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local fe80:: via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local fe80:: via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local fe80::2a0:24ff:fe3d:1868 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295 local fe80::2a0:24ff:fe6d:3943 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
ff02::1 via ff02::1 dev eth0 metric 0
cache mtu 1500 advmss 1440 hoplimit 4294967295
ff02::1 via ff02::1 dev eth1 metric 0
cache mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth1 table local metric 256 expires 21332019sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth0 table local metric 256 expires 21332019sec mtu 1500 advmss 1440 hoplimit 4294967295 unreachable default dev lo table unspec proto none metric -1 error -101 hoplimit 255
ip -6 route show table 252
--------------------------
ip -6 neigh show
----------------
fe80::250:4ff:fe6f:ba14 dev eth0 lladdr 00:50:04:6f:ba:14 router STALE
2001:a:c:1:250:4ff:fe6f:ba14 dev eth0 lladdr 00:50:04:6f:ba:14 router STALE fe80::214:22ff:feac:355e dev eth0 lladdr 00:14:22:ac:35:5e router REACHABLE
Best Regards,
Sazzad.
-----Original Message-----
From: support-bounces at ml.nautilus6.org [mailto:support-bounces at ml.nautilus6.org] On Behalf Of Romain KUNTZ
Sent: Tuesday, October 23, 2007 1:47 AM
To: Support ML
Subject: Re: [support] HA and MR are unable to recognize NEMO packet
Hello,
On 2007/10/22, at 18:03, sazzadur rahman wrote:
> I was struggling implementing NEMO (http://www.nautilus6.org/doc/
> nepl-howto/). I am using kernel 2.6.21.3 on Fedora Core 6 for both HA
> and MR. I could install the kernel along with the patches and user
> land application as described by the above HOWTO. Before handoff, I
> could reach every node from every other node (LFN, HA, MR, Router
> etc.). But after handoff, I observed that HA doesn't recognize Binding
> Update packet sent from MR and MR gets and ICMP (cause 3: port
> unreachable) from HA.
>
Looking at the HA logs, it seems that your HA does not process correctly the received BU. It looks like a known bug, that is fixed in one of the patches included in the Howto. Did you correctly apply the patch mipv6-daemon-umip-0.3-20070613.patch before applying the NEPL patch?
> On the contrary, when I ping6 to HA from MR, HA replies it with
> Binding Error to MR
>
This is because the MR is not registered to the HA but sends packets with Home Address option in it. This will be fixed once your MR correctly registered to the HA.
> and this time, MR doesn't recognize Binging Error NEMO packet and
> replies ICMP to HA.
>
Do you have any log messges on the MR for this? Anyway, this may be due to the previous errors, so let's first try to fix the first problem.
Regards,
romain
_______________________________________________
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