Ticket ID: SIXXS #5696002 Ticket Status: Resolved PoP: uschi03 - Team Cymru (Chicago, Illinois)
Cannot reach tunnel endpoint
Shadow Hawkins on Saturday, 08 October 2011 18:46:01
I cannot reach the remote endpoint of my tunnel. On Saturday at 12:00 by the Tunnel Statistics graphs, there was an odd spike in latency, packets/s, and octets/s. Now the tunnel seems to be dead: as far as I can tell, it gets set up correctly and simply won't accept traffic.
$ sudo aiccu start
$ grep aiccu /var/log/everything.log
Oct 8 11:01:26 localhost aiccu: Succesfully retrieved tunnel information for T51857
Oct 8 11:01:26 localhost aiccu: AICCU running as PID 8466
Oct 8 11:01:26 localhost aiccu: [AYIYA-start] : Anything in Anything (draft-02)
Oct 8 11:01:26 localhost aiccu: [AYIYA-tun->tundev] : (Socket to TUN) started
$ netstat -u
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 0 0 10.3.2.24:37332 uschi03.sixxs.net:ayiya ESTABLISHED
$ ip -6 route
2604:8800:100:54::/64 dev sixxs proto kernel metric 256
2604:8800:121:feef::/64 dev br0 proto kernel metric 256
fe80::/64 dev br0 proto kernel metric 256
fe80::/64 dev eth1 proto kernel metric 256
fe80::/64 dev sixxs proto kernel metric 256
default via 2604:8800:100:54::1 dev sixxs metric 1024
$ ip addr show dev sixxs
12: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500
link/none
inet6 2604:8800:100:54::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::8800:100:54:2/64 scope link
valid_lft forever preferred_lft forever
$ ip addr show dev br0
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:21:01:11:11:11 brd ff:ff:ff:ff:ff:ff
inet 10.3.2.24/24 brd 10.3.2.255 scope global br0
inet6 2604:8800:121:feef::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::221:1ff:fe11:1111/64 scope link
valid_lft forever preferred_lft forever
$ ping6 -c4 2604:8800:100:54::1
PING 2604:8800:100:54::1(2604:8800:100:54::1) 56 data bytes
--- 2604:8800:100:54::1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
$ ip -s link show sixxs
13: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500
link/none
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
46272 549 0 0 0 0
I would be happy to provide any additional necessary information.
Cannot reach tunnel endpoint
Shadow Hawkins on Saturday, 08 October 2011 20:35:12
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
Same problem and behavior here as well with my tunnel(T72929). It was working fine last night, now it reports that it is connected but not passing traffic.
State change: resolved
Jeroen Massar on Saturday, 08 October 2011 20:40:50
The state of this ticket has been changed to resolved
Cannot reach tunnel endpoint
Jeroen Massar on Saturday, 08 October 2011 20:41:48
Thanks for reporting, all should work fine again.
Cannot reach tunnel endpoint
Shadow Hawkins on Sunday, 18 December 2011 06:08:34
This issue appears to have reoccurred as of an hour ago. I do not have physical access to the end-point machine at this time, but the tunnel statistics graphs appear similar to the first occurrence.
Cannot reach tunnel endpoint
Shadow Hawkins on Sunday, 01 January 2012 05:57:47
This issue seems to have occurred once again. Was the previous occurrence silently resolved, or did it eventually resolve itself?
Cannot reach tunnel endpoint
Jeroen Massar on Sunday, 01 January 2012 10:46:56
You will really have to describe what exact problem is occurring and provide details of that problem along with the information requested.
Posting is only allowed when you are logged in. |