On Fri, 2004-07-16 at 13:02, Jan Wagner wrote: <SNIP> > > > # ifup ipv6 Try running "ifup -v ipv6" then at least you can see the actions taken. > > > # ifconfig ipv6 > > > ipv6 Protokoll:IPv6-nach-IPv4 > > > inet6 Adresse: fe80::d991:6309/64 Gültigkeitsbereich:Verbindung > > > inet6 Adresse: fe80::d991:630d/64 Gültigkeitsbereich:Verbindung > > > inet6 Adresse: 2001:8d0:20ff:fffe::5/127 > > > Gültigkeitsbereich:Global inet6 Adresse: 2001:8d0:20ff:fffe::7/127 > > > Gültigkeitsbereich:Global > > > > Two link-local addresses ? :) > > > > ipv6calc -i 2002:d991:6309:: 2>&1 | grep "IPv4 address" > > Address type is 6to4 and included IPv4 address is: 217.145.99.9 > > > > ipv6calc -i 2002:d991:630d:: 2>&1 | grep "IPv4 address" > > Address type is 6to4 and included IPv4 address is: 217.145.99.13 > > > > This surely isn't correct, it doesn't even match your local IPv4 address > > This IPs are totaly correct. Two link locals is never correct. Also those two IP addresses are not in the rest of your configuration output. > > Which kernel and also which debian version is this? > > resolv1:~# uname -a > Linux resolv1 2.4.25-1-386 #2 Wed Apr 14 19:38:08 EST 2004 i686 GNU/Linux > resolv1:~# cat /etc/debian_version > testing/unstable 2.4.x could be the problem, but I more guess it has to do with the multiple IPv4 addresses. You should at least maybe specify a 'local' line so that the local endpoint is known to the kernel. Greets, Jeroen
Attachment:
signature.asc
Description: This is a digitally signed message part