SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3676201
Ticket Status: Resolved

PoP: deham02 - Easynet (Hamburg)

Tunnel stopped working after working over a week
[de] Shadow Hawkins on Tuesday, 15 February 2011 01:22:24
Hi, * my tunnel (T54825) stopped working after over a week. * NIC-Handle: MSN16-SIXXS aiccu test Results: * everthing works until its pinging the inner-tunnel remote endpoint: PING 2001:6f8:1c00:3a7::1(2001:6f8:1c00:3a7::1) 56 data bytes --- 2001:6f8:1c00:3a7::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2017ms More information: * tunnel is configured using aiccu on pc server (gentoo) in local network (private class-c net) * behind NAT-Router (linux as well, small linksys box with tomato firmware (dnsmasq+iptables)) Info from that gentoo box: lisa ~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: sit0: <NOARP> mtu 1480 qdisc noop state DOWN link/sit 0.0.0.0 brd 0.0.0.0 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:24:8c:5d:61:6c brd ff:ff:ff:ff:ff:ff inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0 inet6 2001:6f8:1ddc::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::224:8cff:fe5d:616c/64 scope link valid_lft forever preferred_lft forever 19: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500 link/none inet6 2001:6f8:1c00:3a7::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4f8:1c00:3a7:2/64 scope link valid_lft forever preferred_lft forever lisa ~ # ip r 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1 metric 3 127.0.0.0/8 via 127.0.0.1 dev lo default via 192.168.1.254 dev eth0 metric 3 lisa ~ # ip -6 r 2001:6f8:1c00:3a7::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 2001:6f8:1ddc::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 default via 2001:6f8:1c00:3a7::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0 iptables is stopped to make sure its not the firewall: lisa ~ # iptables -vnL Chain INPUT (policy ACCEPT 1226 packets, 184K bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 1165 packets, 486K bytes) pkts bytes target prot opt in out source destination lisa ~ # ip6tables -vnL Chain INPUT (policy ACCEPT 12 packets, 1248 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 18 packets, 1776 bytes) pkts bytes target prot opt in out source destination lisa ~ # lisa ~ # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== +213.9.73.106 134.34.3.18 2 u 155 1024 377 24.273 1.117 0.228 +85.25.139.186 130.149.17.8 2 u 248 1024 377 28.643 1.267 0.343 -85.31.187.67 131.188.3.222 2 u 730 1024 377 28.283 -2.983 19.730 *46.4.54.78 129.69.1.153 2 u 58 1024 377 28.887 -0.041 0.055 lisa ~ # I restarted the router too(to have "clean" internet connection, regarding state tables etc) The setup here did not change i any way since a week. TIA -Marc
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 15 February 2011 12:26:02
Message is Locked
The state of this ticket has been changed to resolved
Tunnel stopped working after working over a week
[de] Shadow Hawkins on Wednesday, 29 June 2011 18:00:47
I have read and followed the "Reporting Problems" section on the Contact page. I am removing these five pre-filled lines to demonstrate that I really read it. I am providing the full details as requested on the mentioned Contact page. If I do not remove this, then please ignore this message as I didn't read it anyway. ------------------------------------------------------------------------------>8 Please re-open. My tunnel has stopped working again after many weeks. TIA -Marc
Tunnel stopped working after working over a week
[de] Shadow Hawkins on Wednesday, 29 June 2011 18:01:42
Please re-open. My tunnel has stopped working again after many weeks. TIA -Marc
Tunnel stopped working after working over a week
[ch] Jeroen Massar SixXS Staff on Wednesday, 29 June 2011 18:48:05
I am really wondering what makes your tunnel so special that it happens. Oh well, only few more days of testing the new sixxsd and I'll be comfortable to throw it on that box and it should never happen again.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker