Re: weirdness with ipv6 routing
Do you have a route for 2000::/3 on your gateway pointing through
your tunnel connection? This seems to be a necessary static route to put
on any Linux IPv6 enabled kernel to get routing to work properly as it
does not work with the default route only.
Jeremy
On Mon, Oct 15, 2001 at 02:21:44AM +0200, Wichert Akkerman wrote:
>
> I have a strange problem with my ipv6 setup at home. The basic setup
> is simple: I have a /64 range that gets routed to me through a
> tunnel. From the gateway ipv6 connections work normally.
>
> However from my other machines I can only reach outside machines
> if I have a connection open to them from my gateway, and a few
> seconds after I close the connection on the gateway all connections
> from other machines will stop as well. A ping6 demonstrates this
> nicely:
>
> [tornado;~]-3> ping6 irc6.ngnet.it
> PING irc6.ngnet.it(irc6.ngnet.it) 56 data bytes
> From thunder.ipv6.wiggy.net: Destination unreachable: Address unreachable
> (1) From thunder.ipv6.wiggy.net: Destination unreachable: Address unreachable
> From thunder.ipv6.wiggy.net: Destination unreachable: Address unreachable
> 64 bytes from irc6.ngnet.it: icmp_seq=3 hops=58 time=553.397 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=4 hops=58 time=556.061 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=5 hops=58 time=567.776 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=6 hops=58 time=549.091 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=7 hops=58 time=566.986 msec
> (2) 64 bytes from irc6.ngnet.it: icmp_seq=8 hops=58 time=550.692 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=9 hops=58 time=550.490 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=10 hops=58 time=548.389 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=11 hops=58 time=550.255 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=12 hops=58 time=549.746 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=13 hops=58 time=551.014 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=14 hops=58 time=550.113 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=15 hops=58 time=551.056 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=16 hops=58 time=556.783 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=17 hops=58 time=548.771 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=18 hops=58 time=549.876 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=19 hops=58 time=595.884 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=20 hops=58 time=564.248 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=21 hops=58 time=551.019 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=22 hops=58 time=549.669 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=23 hops=58 time=549.688 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=24 hops=58 time=549.618 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=25 hops=58 time=552.158 msec
> 64 bytes from irc6.ngnet.it: icmp_seq=26 hops=58 time=559.949 msec
> From thunder.ipv6.wiggy.net: Destination unreachable: Address unreachable
> From thunder.ipv6.wiggy.net: Destination unreachable: Address unreachable
>
> At (1) I started a ping6 from thunder (which is my gateway), and at (2)
> I stopped the ping6 there. Does anyone have any clue what the problem
> might be here?
>
> Wichert.
>
> --
> _________________________________________________________________
> / Nothing is fool-proof to a sufficiently talented fool \
> | wichert@wiggy.net http://www.liacs.nl/~wichert/ |
> | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
>
>
> --
> To UNSUBSCRIBE, email to debian-ipv6-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: