Ticket ID: SIXXS #877091 Ticket Status: User PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)
uschi02 not accepting traffic from tunnel T14780
Shadow Hawkins on Friday, 12 December 2008 16:06:06
Username: AL4315-RIPE
Email: ripe@clusterfsck.com
Tunnel type: heartbeat
OS: Debian LInux 2.6.24 using aiccu
The endpoint of my tunnel (T14780) is 2001:4978:f:e6::1. It stopped accepting traffic sometime yesterday afternoon. Haven't changed anything on my side. Tried restarting aiccu, but no change. Any help in resolving this would be greatly appreciated. Thanks!!! -Arion
shinjuku:~# ip -6 addr show dev sixxs
28: sixxs@NONE: <POINTOPOINT,NOARP,UP,10000> mtu 1280
inet6 2001:4978:f:e6::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::60ff:ec9f/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::ac14:cc01/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::c0a8:1/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::a14:cc01/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::c0a8:8101/64 scope link
valid_lft forever preferred_lft forever
shinjuku:~# ip -6 route show default
default via 2001:4978:f:e6::1 dev sixxs metric 1024 expires 21333489sec mtu 1280 advmss 1220 hoplimit 4294967295
shinjuku:~# ping6 -c 5 2001:4978:f:e6::2
PING 2001:4978:f:e6::2(2001:4978:f:e6::2) 56 data bytes
64 bytes from 2001:4978:f:e6::2: icmp_seq=1 ttl=64 time=0.129 ms
64 bytes from 2001:4978:f:e6::2: icmp_seq=2 ttl=64 time=0.104 ms
64 bytes from 2001:4978:f:e6::2: icmp_seq=3 ttl=64 time=0.096 ms
64 bytes from 2001:4978:f:e6::2: icmp_seq=4 ttl=64 time=0.112 ms
64 bytes from 2001:4978:f:e6::2: icmp_seq=5 ttl=64 time=0.105 ms
--- 2001:4978:f:e6::2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3997ms
rtt min/avg/max/mdev = 0.096/0.109/0.129/0.012 ms
shinjuku:~# ping6 -c 5 2001:4978:f:e6::1
PING 2001:4978:f:e6::1(2001:4978:f:e6::1) 56 data bytes
--- 2001:4978:f:e6::1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4010ms
shinjuku:~#
State change: user
Jeroen Massar on Friday, 12 December 2008 16:28:08
The state of this ticket has been changed to user
uschi02 not accepting traffic from tunnel T14780
Jeroen Massar on Friday, 12 December 2008 16:29:24
Please actually read the "Reporting Problems" section on the Contact page and provide the details requested.
You seem to have 5 IP addresses configured on that host, you might want to check the setup of that, your firewall, routing entries etc etc etc etc.
uschi02 not accepting traffic from tunnel T14780
Shadow Hawkins on Friday, 12 December 2008 17:34:55
I cleared out the old link-local addresses of my tunnel interface device, but that didn't make any difference (they shouldn't matter anyway, since its a point to point link).
shinjuku:~# ip -6 addr show dev sixxs
29: sixxs@NONE: <POINTOPOINT,NOARP,UP,10000> mtu 1280
inet6 2001:4978:f:e6::2/64 scope global
valid_lft forever preferred_lft forever
shinjuku:~#
Running a sniffer on my outbound interface just shows that I'm not getting any responses back from the uschi02 (traffic below shows me trying to ping6 www.kame.net):
shinjuku:/home/arion# tcpdump -n -i ppp0 ip host 216.14.98.22
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
11:30:43.328799 IP 96.255.236.159 > 216.14.98.22: IP6 2001:4978:f:e6::2 > 2001:200:0:8002:203:47ff:fea5:3085: ICMP6, echo request, seq 10, length 64
11:30:44.328807 IP 96.255.236.159 > 216.14.98.22: IP6 2001:4978:f:e6::2 > 2001:200:0:8002:203:47ff:fea5:3085: ICMP6, echo request, seq 11, length 64
11:30:45.328800 IP 96.255.236.159 > 216.14.98.22: IP6 2001:4978:f:e6::2 > 2001:200:0:8002:203:47ff:fea5:3085: ICMP6, echo request, seq 12, length 64
...
(my ISP uses PPPoE, sucky... but works..)
Posting is only allowed when you are logged in. |