|
Tunnel not working. Setup looks alright. Using Linux 2.4.21
![[ca]](/s/countries/ca.gif) Shadow Hawkins on Tuesday, 24 August 2004 20:58:01
Hi!
I'm trying to put my tunnel UP but it still doesn't work. I followed all the instructions on the "Linux iproute2" page. Here's what I have:
root@box1:/home/spanska/heartbeat/client# ip tunnel show
tunl0: ip/ip remote any local any ttl inherit nopmtudisc
gre0: gre/ip remote any local any ttl inherit nopmtudisc
sit0: ipv6/ip remote any local any ttl 64 nopmtudisc
ioctl: No such device or address
ioctl: No such device or address
ioctl: No such device or address
ioctl: No such device or address
sixxs: ipv6/ip remote 212.224.0.188 local any ttl 64
root@box1:/home/spanska/heartbeat/client# ifconfig sixxs
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2001:6f8:900:31d::2/64 Scope:Global
inet6 addr: fe80::18ca:27d0/64 Scope:Link
inet6 addr: fe80::c0a8:201/64 Scope:Link
inet6 addr: fe80::c0a8:101/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:868 (868.0 b)
When I try to ping the remote IPv4 endpoint it works, but it doesn't for the IPv6 endpoint. When I ping and I sniff (tcpdump -i eth1 -n host 212.224.0.188) I can see that:
14:41:28.919967 24.202.39.208 > 212.224.0.188: 2001:6f8:900:31d::2 > 2001:6f8:900:31d::1: icmp6: echo request (DF)
14:41:29.919882 24.202.39.208 > 212.224.0.188: 2001:6f8:900:31d::2 > 2001:6f8:900:31d::1: icmp6: echo request (DF)
14:41:30.919875 24.202.39.208 > 212.224.0.188: 2001:6f8:900:31d::2 > 2001:6f8:900:31d::1: icmp6: echo request (DF)
14:41:31.919877 24.202.39.208 > 212.224.0.188: 2001:6f8:900:31d::2 > 2001:6f8:900:31d::1: icmp6: echo request (DF)
14:41:32.919886 24.202.39.208 > 212.224.0.188: 2001:6f8:900:31d::2 > 2001:6f8:900:31d::1: icmp6: echo request (DF)
14:41:33.919926 24.202.39.208 > 212.224.0.188: 2001:6f8:900:31d::2 > 2001:6f8:900:31d::1: icmp6: echo request (DF)
14:41:56.372201 24.202.39.208.2125 > 212.224.0.188.3740: udp 94 (DF)
14:42:56.413120 24.202.39.208.2125 > 212.224.0.188.3740: udp 94 (DF)
14:43:56.452656 24.202.39.208.2125 > 212.224.0.188.3740: udp 94 (DF)
14:44:56.492207 24.202.39.208.2125 > 212.224.0.188.3740: udp 94 (DF)
14:45:56.507127 24.202.39.208.2125 > 212.224.0.188.3740: udp 94 (DF)
I can see the heartbeat packet every minute. I just don't get any replies back. What can be wrong? :{
Tunnel not working. Setup looks alright. Using Linux 2.4.21
![[de]](/s/countries/de.gif) Shadow Hawkins on Tuesday, 24 August 2004 23:07:20
Hello,
I note some differences to my setup:
ioctl: No such device or address ...strange!?...i don't see those.
sixxs: ipv6/ip remote 212.224.0.188 local any ttl 64 instead of "any", I have my local IPv4 address.
can you show me your
"ip -6 route" output?
Another point of failure might be that the clock is not in sync.
Cheers
Thorsten
Tunnel not working. Setup looks alright. Using Linux 2.4.21
Shadow Hawkins on Tuesday, 24 August 2004 23:12:59
Here the "ip -6 route" output:
root@box1:/home/spanska# ip -6 route
2001:6f8:900:31d::/64 via :: dev sixxs proto kernel metric 256 mtu 1480 advmss 1420
3ffe:b80:d14:1::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1220
3ffe:b80:d14:2::/64 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1220
3ffe:b80:d14:3::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
fe80::/64 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1220
unreachable fe80::/64 dev lo metric 256 error -101 mtu 16436 advmss 1220
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1480 advmss 1420
ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
ff00::/8 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 proto kernel metric 256 mtu 1500 advmss 1220
unreachable ff00::/8 dev lo metric 256 error -101 mtu 16436 advmss 1220
ff00::/8 dev sixxs proto kernel metric 256 mtu 1480 advmss 1420
default via 2001:6f8:900:31d::1 dev sixxs metric 1024 mtu 1480 advmss 1420
And here's what I have to sync my clock:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/sbin/ntpdate -u ntp.cpsc.ucalgary.ca >>/dev/null 2>&1
And that's in root's crontab.
Tunnel not working. Setup looks alright. Using Linux 2.4.21
Shadow Hawkins on Wednesday, 25 August 2004 06:47:16
Is your tunnel bound to the device you have internet access to?
(ip tunnel add sixxs mode sit local [Your IPv4 Endpoint] remote [POP IPv4 Endpoint] dev eth0) ?
Thorsten
Tunnel not working. Setup looks alright. Using Linux 2.4.21
root@box1:/home/spanska/heartbeat/client# ifconfig sixxs sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
That is your problem, that is the wrong tunneling encap for Linux boxes.
"ip -6 link sho" should show something like:
8<-------------
8: sixxs@NONE: <POINTOPOINT,NOARP,UP> mtu 1280 qdisc noqueue
link/sit you.you.you.you peer pop.pop.pop.pop
------------->8
Tunnel not working. Setup looks alright. Using Linux 2.4.21
Shadow Hawkins on Sunday, 05 September 2004 17:01:27
"ip -6 link show" was showing the right thing. And when I type "ip -6 tunnel show" I also see what I gotta see for the tunnel. I can now ping the other side of the IPv6 tunnel, even though I did nothing during all that time because I was cleaning up my new appartement for univ. I guess the problem was on their side.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 25 August 2004 09:20:34
Posting is only allowed when you are