|
Address unreachable
![[fi]](/s/countries/fi.gif) Carmen Sandiego on Monday, 14 June 2004 15:39:37
I just got my tunnel from SixXS and did as said in the FAQ to set up it to my computer. Now when I try to ping something I get "From ::1 icmp_seq=1 Destination unreachable: Address unreachable". What could be wrong?
Here are my interfaces:
sit0 Link encap:IPv6-in-IPv4
inet6 addr: ::80.221.143.33/96 Scope:Compat
inet6 addr: ::80.223.231.144/96 Scope:Compat
inet6 addr: ::127.0.0.1/96 Scope:Unknown
UP RUNNING NOARP MTU:1280 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:4 dropped:0 overruns:0 carrier:4
collisions:0 txqueuelen:0
RX bytes:2080 (2.0 Kb) TX bytes:0 (0.0 b)
sit1 Link encap:IPv6-in-IPv4
inet6 addr: fe80::50dd:8f21/64 Scope:Link
inet6 addr: 2001:14b8:100:38::2/64 Scope:Global
inet6 addr: fe80::50df:e790/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2080 (2.0 Kb) TX bytes:2236 (2.1 Kb)
# ip -6 route
::/96 via :: dev sit0 metric 256 mtu 1280 advmss 1220
2001:14b8:100:38::2 dev sit1 metric 1 mtu 1480 advmss 1420
2001:14b8:100:38::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 advmss 1420
2000::/3 via 2001:14b8:100:38::1 dev sit1 metric 1 mtu 1480 advmss 1420
unreachable fe80:: dev lo metric 1 error -101 mtu 16436 advmss 16376
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1220
fe80::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 advmss 1420
ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 proto kernel metric 256 mtu 1500 advmss 1220
ff00::/8 dev sit1 proto kernel metric 256 mtu 1480 advmss 1420
default dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
default dev eth1 proto kernel metric 256 mtu 1500 advmss 1220
unreachable default dev lo metric -1 error -101 advmss 1220
Address unreachable
Carmen Sandiego on Tuesday, 15 June 2004 11:06:52
How I can remove that "unreachable default dev lo metric -1 error -101 advmss 1220"?
Address unreachable
You might want to read the FAQ first and configure your tunnel correctly. You have two default routes over your ethernet interfaces, clean those up too, unless you use them but that would mean you have native IPv6 connectivity and you don't need a tunnel, but there is no gateway thus that is not the case.
How I can remove that "unreachable default dev lo metric -1 error -101 advmss 1220"?
You can't as that is the default bitbucket when there is no route to a destination.
Address unreachable
Carmen Sandiego on Thursday, 17 June 2004 20:22:45
I run these commands:
$ifconfig sit0 up
$ifconfig sit0 tunnel ::62.78.96.38
$ifconfig sit1 up
$ifconfig sit1 add 2001:14b8:100:38::2/64
$route -A inet6 add 2000::/3 gw 2001:14b8:100:38::1 dev sit1
And then I removed those default routes to eth0 and eth1. After that I ran:
$ip -6 ro add default via 2001:14b8:100:38::1 dev sit1
... and route looks this after those:
::/96 via :: dev sit0 metric 256 mtu 1480 advmss 1420
2001:14b8:100:38::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 advmss 1420
2000::/3 via 2001:14b8:100:38::1 dev sit1 metric 1 mtu 1480 advmss 1420
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440
fe80::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 advmss 1420
ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440
ff00::/8 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440
ff00::/8 dev sit1 proto kernel metric 256 mtu 1480 advmss 1420
default via 2001:14b8:100:38::1 dev sit1 metric 1024 mtu 1480 advmss 1420
I don't see anything wrong with that although I'm not familiar with with this.
Still it doesn't ping (I don't even get any error message) and I also tried to remove those eth0 and eth1 routes but nothing.
Address unreachable
Compare your commands to Linux using IPRoute2. the sit0/sit1 stuff is the old way and that won't properly work on newer kernels.
Adding 2000::/3 is also not needed anymore, a 'default' route works also on the newer kernels. Also.. check tcpdump while pinging etc
Address unreachable
Carmen Sandiego on Friday, 18 June 2004 11:46:50
I got it to work. Thanks a lot.
I used that old method also in my other computer and it worked there but I wonder why it didn't work on this computer, both have 2.4.x kernel.
Address unreachable
![[de]](/s/countries/de.gif) Shadow Hawkins  on Friday, 25 June 2004 18:17:29
It's frustrating. I searched the FAQ threw the hole day, but i don't find my error. Could anybody help me please? I could ping6 my local ipv6 endpoint, but not my POP IPv6 endpoint or any other v6 address. All what i get is this:
From 2001:6f8:900:22::1 icmp_seq=1 Destination unreachable: Address unreachable
When i do a traceroute6 on that address i geht this:
traceroute to 2001:6f8:900:2a4::1 (2001:6f8:900:2a4::1) from 2001:6f8:900:2a4::2, 30 hops max, 16 byte packets
1 ip6-localhost (::1) 0.894 ms !H 0.886 ms !H 0.751 ms !H
Here are some other information wich could be usefull for you:
heartbeat.conf:
os "linux"
ipv4_interface "ppp0"
ipv4_pop "deham01.sixxs.net"
ipv6_interface "sixxs"
ipv6_pop "2001:6f8:900:2a4::1"
ipv6_local "2001:6f8:900:2a4::2"
ipv6_prefixlen 64
hb_password "***"
hb_sendinterval 60
hb_timeout 300
I found in the FAQ (https://noc.sixxs.net/faq/connectivity/?faq=ossetup&os=linuxdebian), that i have to configure my /etc/network/interfaces like this:
auto sixxs
iface sixxs inet6 v4tunnel
address 2001:6f8:900:2a4::2
netmask 64
endpoint 80.138.111.92
ttl 64
up ip link set mtu 1280 dev sixxs
up ip route add 2000::/3 via 2001:6f8:900:2a4::1 dev sixxs
I don't really know, what i should set to the endpoint, becaus this v4 address is dynamic and i should use heartbeat for it? It's a little bit confusing or i understand something wrong...
This says ip -f inet6 r l:
2001:6f8:900:2a4::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
3ffe:bc0:a70:1::/64 dev eth0 metric 256 mtu 1500 advmss 1220
3ffe:bc0:a70::/48 dev eth0 metric 1 mtu 1500 advmss 1220
2000::/3 via 2001:6f8:900:2a4::1 dev sixxs metric 1024 mtu 1280 advmss 1220
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth2 metric 256 mtu 1500 advmss 1220
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth2 metric 256 mtu 1500 advmss 1220
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220
unreachable default dev lo proto none metric -1 error -101 advmss 122
Another thing what is confusing, that i could ping6 from a remote mashine in a shell my POP v6 sometimes, and sometimes i get "Adress unreachable".
Please don't say something like "Read the FAQ", i searched it threw over a few hours and i don't understand, what i am doing wrong. :(
Address unreachable
Oh yes there is a big FAQ for this with exclamation mark and all:
Heartbeat FAQ
aka sync your clock ;)
Btw you still have 3ffe:bc0:a70::/48 on eth0
Also that is a /48, which should be a /64...
Next to that you can set a 'default' route with most recent kernels (2.4.20+ or something)
Next to that read the Debian Setup FAQ.
And pasting your Heartbeat password is extremely stupid, now everybody can use your tunnel. Thus that one has been reset, check your tunnel information page for the new one.
Address unreachable
Shadow Hawkins on Friday, 25 June 2004 18:28:18
Hmmm, seems i am too confused to post correct, i am sorry. The time on the machine is synched and i got this in my /var/log/messages:
Jun 25 18:25:59 kaya heartbeat-client: [HB] HEARTBEAT TUNNEL 2001:6f8:900:2a4::2 80.138.111.92
The old v6 address were deletet a hole time, that was i posted, was an old output, sorry again. It looks at the moment like that:
2001:6f8:900:2a4::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
2000::/3 via 2001:6f8:900:2a4::1 dev sixxs metric 1024 mtu 1280 advmss 1220
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth2 metric 256 mtu 1500 advmss 1220
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth2 metric 256 mtu 1500 advmss 1220
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220
unreachable default dev lo proto none metric -1 error -101 advmss 1220
I saw the misstake with the password after i pushed the evil reply button. I changed it directly after that and edit it in the post. ;(
Address unreachable
Shadow Hawkins on Friday, 25 June 2004 18:54:38
Could anybody shot me please down? I fond the error. It was the part in /etc/network/interfaces...
"endpoint [POP IPv4 Endpoint]"
I overreaded the "POP" and i thaught, i have to use my own v4 address. I changed it now to the address of my POP and it works now. *D
|
![[ch]](/s/countries/ch.gif)
Posting is only allowed when you are