Hello, Eugen Leitl a écrit : > I've got a /56 from which I assigned to eth0 a > 2a01:4f8:7d:300::2, with the gateway 2a01:4f8:7d:300::1 > > I can ping the assigned address from outside (another > machine with a sixx tunnel), but no dice with e.g. > ping6 ipv6.google.com > PING ipv6.google.com(2a00:1450:8005::68) 56 data bytes > > It looks like a route problem. My routes look like > > route --inet6
The output of ip -6 addr and ip -6 route may be more compact. > Kernel IPv6 routing table > Destination Next Hop Flag Met Ref Use If > 2a01:198:200::/64 :: UAe 256 0 3 > eth0 > 2a01:4f8:7d:300::/56 :: U 256 0 1 > eth0 IMO the prefix length for any local prefix should always be /64. The purpose of a /56 prefix is to be divided into multiple /64 prefixes. > ::/0 2a01:4f8:7d:300::1 UG 1024 0 1 > eth0 > ::/0 fe80::2e0:81ff:fe58:58b3 UGDAe 1024 0 0 > eth0 > 2a01:198:200:0:225:90ff:fe02:326e/128 :: Un 0 1 3 lo > 2a01:4f8:7d:300::2/128 :: Un 0 1 6 lo It looks like eth0 has also got a prefix 2a01:198:200::/64 and default router from stateless autoconfiguration (a router on the link sends advertisements for this prefix). Maybe your box uses the wrong source prefix and router combination when sending packets. If you don't want eth0 to use stateless autoconfiguration, you can disable by setting /proc/sys/net/ipv6/conf/eth0/autoconf to 0. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
