|
PING6 Destination unreachable: No route
![[fi]](/s/countries/fi.gif) Carmen Sandiego on Thursday, 02 September 2004 08:49:03
when i ping6 from other system, i get this:
PING 2000:14b8:100:3c::2(2000:14b8:100:3c::2) from 3ffe:200:13f::49 : 56 data bytes
From 2001:730:4::1:9 icmp_seq=1 Destination unreachable: No routeFrom 2001:730:4::1:9 icmp_seq=2 Destination unreachable: No routeFrom 2001:730:4::1:9 icmp_seq=3 Destination unreachable: No routeFrom 2001:730:4::1:9 icmp_seq=4 Destination unreachable: No routeFrom 2001:730:4::1:9 icmp_seq=5 Destination unreachable: No route
--- 2000:14b8:100:3c::2 ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% loss, time 4044ms
EDIT: just realised swedish have again some problems probably..
in red hat linux 8 with kernel 2.4.20 i can't setup properly tunnel, today when tried to fix that graphs (didn't show anything) i get now this:
# ip -6 ro add default via 2001:14b8:100:3c::1 dev sixxs
RTNETLINK answers: No route to host
heartbeat-client running.
ping6 works:
PING 3ffe:200:13f::49(3ffe:200:13f::49) from 2001:14b8:100:3c::2 : 56 data bytes
64 bytes from 3ffe:200:13f::49: icmp_seq=1 ttl=61 time=207 ms
this sixxs tunnel worked fine on windows 2000 professional, but don't work in red hat, maybe there is another tunnel for linux ;)
PING6 Destination unreachable: No route
a) check your clock and sync it using NTP
b) ping something more local, eg the remote endpoint
c) check your routing table
d) tcpdump
Or read the FAQ and the contact page
And you might want to try out the AICCU beta.
PING6 Destination unreachable: No route
![[de]](/s/countries/de.gif) Carmen Sandiego on Monday, 06 September 2004 16:52:43
hi...
I had the same problem a couple days ago, when I configured my Router ( Gentoo Linux Box ).
I solved the problem by adding a second default route..
the first:
default via *POP IPV6* dev sixxs metric 1024 mtu 1280 advmss 1220
and the second one:
2000::/3 via *POP IPV6* dev sixxs metric 1024 mtu 1280 advmss 1220
hope this helps you too....
Jan
PING6 Destination unreachable: No route
Carmen Sandiego on Thursday, 16 September 2004 00:06:45
just to say, i had all set up.
and i wanted to fix that graphs showing it didn't work while it worked.
when i was adding route, it said this: RTNETLINK answers: No route to host
but problem wasn't there.
it had nothing to do with clock or routing table.
there just was pop's ipv6 address for eth0 that i didn't set.
i wonder why. but just ifconfig eth0 del pop_ipv6 worked.
btw, everytime that linux will boot, it will have pop's ipv6 in eth0.
i wonder why, if i do only this:
ip tunnel add sixxs mode sit local 80.223.177.10 remote 62.78.96.38
ip link set sixxs up
ip link set mtu 1280 dev sixxs
ip tunnel change sixxs ttl 64
ip -6 addr add 2001:14b8:100:3c::2/64 dev sixxs
route -A inet6 add 2000::/3 dev sixxs
ip -6 ro add default via 2001:14b8:100:3c::1 dev sixxs
ifconfig eth0 add 2001:14b8:100:3c::2/64
i don't set 2001:14b8:100:3c::1/64 for eth0, but it comes there but from where?
PING6 Destination unreachable: No route
2001:14b8:100:3c::1/64 is routed on the sixxs interface, nowhere else.
You should thus also remove: "ifconfig eth0 add 2001:14b8:100:3c::2/64"
You can write "route -A inet6 add 2000::/3 dev sixxs" as "ip -6 ro add 2000::/3 dev sixxs", but if you have a correct kernel the line with 'default' already works.
Also "route -A inet6 add 2000::/3 dev sixxs" actually breaks your setup as you are not routing it over a gateway, but you are routing 2000::/3 to the sixxs, thus all the traffic going to 2000::/3 is directly send to the sixxs interface and won't go any further...
PING6 Destination unreachable: No route
If you need to add a 2000::/3 you need to upgrade your kernel. All the Linux kernels which do not support the 'default' + ipv6_forwarding have some kind of vulnerability, thus you would really need to upgrade anyway.
PING6 Destination unreachable: No route
Shadow Hawkins on Saturday, 09 October 2004 12:32:09
for me and kernel 2.6.8.1 it works only with 2000::/3
we are talking about this, don't we:
echo 1 > /proc/sys/net/ipv6/conf/[interface]/forwarding
there is no ipv6_forwarding for me.
I also asked some guys in IRC, the all agreed that 2000::/3 is not deprecated and still in need for setups like that. :(
PING6 Destination unreachable: No route
When you have no IPv6 forwarding, eg:
$ sysctl -a 2>/dev/null | grep forwarding | grep ipv6
net.ipv6.conf.sixxs.forwarding = 0
net.ipv6.conf.eth0.forwarding = 0
net.ipv6.conf.eth0.forwarding = 0
net.ipv6.conf.lo.forwarding = 0
net.ipv6.conf.default.forwarding = 0
net.ipv6.conf.all.forwarding = 0
Then 'default' should work on _all_ kernels.
When you have IPv6 forwarding enabled, thus:
$ sysctl -a 2>/dev/null | grep forwarding | grep ipv6
net.ipv6.conf.sixxs.forwarding = 1
net.ipv6.conf.eth0.forwarding = 1
net.ipv6.conf.eth1.forwarding = 1
net.ipv6.conf.lo.forwarding = 1
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
Then you can use 'default' on >=2.4.21, or have to use 2000::/3 on <2.4.21
Also see this explaination from the maintainers of the kernel code, which is also linked from the FAQ.
2000::/3 always works of course, but it should be 'default'.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 02 September 2004 09:34:35
Posting is only allowed when you are