RE: ip6-localhost (::1) 2990.86 ms !H -> Why ?

From: NDSoftware (extml@ndsoftware.net)
Date: Sun Nov 18 2001 - 07:15:11 EST


> -----Original Message-----
> From: Pekka Savola [mailto:pekkas@netcore.fi]
> Sent: Sunday, November 18, 2001 12:28 PM
> To: NDSoftware
> Cc: linux-net@vger.kernel.org
> Subject: RE: ip6-localhost (::1) 2990.86 ms !H -> Why ?
>
>
> On Sun, 18 Nov 2001, NDSoftware wrote:
> > > Capture traffic with 'tcpdump -i interface -n ip6' on both
> > > ends and see
> > > that the messages (ICMP neighbour solications, when you ping6
> > > the other
> > > end's link-local address) get through.
> >
> > On router:
> >
> > 12:15:39.109604 0:d0:70:1:81:1b 33:33:ff:0:0:1 86dd 86:
> > 6000 0000 0020 3aff 3ffe 8271 2101 0001
> > 0000 0000 0000 0001 ff02 0000 0000 0000
> > 0000 0001 ff00 0001 8700 d1ab 0000 0000
> > 3ffe 8271 1000
>
> I suggest you upgrade tcpdump to at least 3.6.2, to get IPv6
> enabled. It's difficult to say whether these are the same packets.

Yes but Debian Potato (router) have not this package version (only
3.4.x), only Woody have this.
I can't compile on the router (Potato) because it's only a 486.

>
> > On Woody:
> >
> > 21:38:02.882404 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6:
> neighbor sol:
> > who has 3ffe:8271:2101:1::1
> > 21:38:03.882226 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6:
> neighbor sol:
> > who has 3ffe:8271:2101:1::1
>
> As said, use link-local addresses.
>
> > > Another explanation for this is that IPv6 neighbour
> discovery code is
> > > messed up. This can happen if you take down your loopback
> > > interface.
> >
> > ifdown lo and after:
>
> I'm not sure what you mean by this. In Red Hat Linux terms:
>
> Works:
>
> - ifdown lo ; ifup lo

# ifdown lo
# ifup lo
# traceroute6 www.6bone.net
traceroute to 6bone.net (3ffe:b00:c18:1::10) from 3ffe:8271:2101:1::1,
30 hops max, 16 byte packets
 1 * * *
 2 * * *
 3 * * *
 4 * * *

I have try too this routes:

Kernel IPv6 routing table
Destination Next Hop
Flags Metric Ref Use Iface
::1/128 ::
U 0 0 0 lo
2001::/16 3ffe:8271:1000:22::1
UG 1 0 0 eth0
2002::/16 3ffe:8271:1000:22::1
UG 1 0 0 eth0
3ffe:8271:1000:22::/64 ::
U 1 3 0 eth0
3ffe:8271:2101:1::/64 ::
UA 256 0 0 eth0
3ffe::/16 3ffe:8271:1000:22::1
UG 1 14 0 eth0
fe80::/10 ::
UA 256 0 0 eth0
ff00::/8 ::
UA 256 0 0 eth0

>
> Doesn't fix the problem:
>
> - ifconfig lo down ; ifconfig lo up
> (plus possibly readded routes)
>
> ==> you would have to re-add addresses like ::1/128 on the
> interface too
> (even though they already exist there)
>
> > traceroute to 6bone.net (3ffe:b00:c18:1::10) from
> 3ffe:8271:2101:1::1,
> > 30 hops max, 16 byte packets
> > 1 * * *
> > 2 * * *
> > 3 * *
> >
> > traceroute to 3ffe:8271:1000:22::1 (3ffe:8271:1000:22::1) from
> > 3ffe:8271:2101:1::1, 30 hops max, 16 byte packets
> > 1 * * *
> > 2 *
>
> Using global addresses depend on a lot of other configuration
> being right
> too. Use only link-local when debugging until that works properly.
>

Yes but the link-local don't work:

I i ping Woody on router:

PING fe80::2d0:70ff:fe01:811b(fe80::2d0:70ff:fe01:811b) from
fe80::10:4b44:56cc eth0: 56 data bytes
>From ip6-localhost: Destination unreachable: Address unreachable
>From ip6-localhost: Destination unreachable: Address unreachable
>From ip6-localhost: Destination unreachable: Address unreachable

But i understand why i have:

13:14:22.168116 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: neighbor sol:
who has 3ffe:8271:2101:1::1
13:14:23.158696 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: neighbor sol:
who has 3ffe:8271:2101:1::1
13:14:24.158518 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: neighbor sol:
who has 3ffe:8271:2101:1::1
13:14:25.179880 3ffe:8271:1000:22::1 > ff02::1:0:1: icmp6: neighbor sol:
who has 3ffe:8271:2101:1::1

Why it don't find Woody (3ffe:8271:2101:1::1) ?

> --
> Pekka Savola "Tell me of difficulties surmounted,
> Netcore Oy not those you stumble over and fall"
> Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
>
>

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html



This archive was generated by hypermail 2b29 : Fri Nov 23 2001 - 21:00:38 EST