|
Tunnel Downtime?
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Sunday, 01 February 2004 14:06:02
Hi,
I'm receiving emails saying that my tunnel is down. Checking the tunnel statistics show that my packet loss is 100% and there are no latency statistics anymore. This sounds strange to me, as I'm using IPv6 without problems, so I started to test some things:
- Ping from network to outside: OK
- Ping from outside to network: OK
- Ping from router to outside: OK
- Ping from outside to router: OK
- Ping from router to noc.sixxs.net: OK
- Ping from router to tunnelserver.ipng.nl: OK
At the moment I haven't configured any IPv6 firewalling, so that shouldn't be the problem. I'm using a Linux-2.4.24 kernel and these are my IPv6 routing tables:
root@router1:~# ip -6 ro show table all
local ::1 via :: dev lo proto none metric 0 mtu 16436 rtt 10ms rttvar 10ms cwnd 3 advmss 1220
local 3ffe:8114:1000::69c via :: dev lo proto none metric 0 mtu 16436 advmss 16376
local 3ffe:8114:1000::69d via :: dev lo proto none metric 0 mtu 16436 advmss 16376
3ffe:8114:1000::69c/127 via :: dev sixxs metric 256 mtu 1280 advmss 1220
local 3ffe:8114:2000:1e70:: via :: dev lo proto none metric 0 mtu 16436 advmss 16376
local 3ffe:8114:2000:1e70::1 via :: dev lo proto none metric 0 mtu 16436 rtt 10ms rttvar 10ms cwnd 3 advmss 16376
3ffe:8114:2000:1e70::/64 dev eth1 metric 256 mtu 1500 advmss 1220
local fe80:: via :: dev lo proto none metric 0 mtu 16436 advmss 16376
local fe80::3efb:7a8e via :: dev lo proto none metric 0 mtu 16436 advmss 1220
local fe80::200:e8ff:fea3:9e7e via :: dev lo proto none metric 0 mtu 16436 advmss 16376
local fe80::250:bfff:fe34:57e via :: dev lo proto none metric 0 mtu 16436 advmss 16376
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
ff02::1 via ff02::1 dev eth1 metric 0
cache mtu 1500 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 sixxs metric 256 mtu 1280 advmss 1220
default via 3ffe:8114:1000::69c dev sixxs metric 1024 mtu 1280 advmss 1220
3ffe:8114:1000::69c is POPs tunnel endpoint address
3ffe:8114:1000::69d is my tunnel endpoint address
3ffe:8114:2000:1e70::/64 is the prefix assigned to eth1
Hopefully someone can find a problem, as I'm spending 5 credits each day at the moment O-)
- Mark
Tunnel Downtime?
Let me guess, you recently upgraded your kernel ? :)
local 3ffe:8114:1000::69c via :: dev lo proto none metric 0 mtu 16436 advmss 16376 local 3ffe:8114:1000::69d via :: dev lo proto none metric 0 mtu 16436 advmss 16376
Whoah, what a surprise, you are routing the gateway address to /dev/null no wonder that ping replies never reach the POP (the gateway) that is requesting these.
You should have read the rest of the forum or used the search button, then you would have found: this article
Tunnel Downtime?
Shadow Hawkins on Sunday, 01 February 2004 16:17:02
Hi,
First of all, thank you for spotting this. Although I did search the forum, I didn't find this post (I was searching for terms like tunnel, downtime).
And of course I should have noticed this behaviour: :z
PING 3ffe:8114:1000::69c(3ffe:8114:1000::69c) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.203 ms
- Mark
|
![[ch]](/s/countries/ch.gif)
on Sunday, 01 February 2004 15:41:48
Posting is only allowed when you are