Ticket ID: SIXXS #1236927 Ticket Status: Resolved PoP: deham01 - Easynet (Hamburg)
Tunnel
Shadow Hawkins on Thursday, 22 October 2009 19:00:08
Hi.
My tunnel T11085 to deham01 - Easynet ceased to work between today 01:00 (CEST) and now. Aiccu seems to work, though
Oct 22 18:52:06 grml aiccu: Succesfully retrieved tunnel information for T11085
Oct 22 18:52:06 grml kernel: [1917045.931121] sixxs: Disabled Privacy Extensions
Oct 22 18:52:06 grml aiccu: AICCU running as PID 3268
and the sixxs tunnel interface is being created
root@grml ~ # ip addr show dev sixxs
36: sixxs@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN
link/sit 217.229.189.107 peer 212.224.0.188
inet6 2001:6f8:900:849::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::d9e5:bd6b/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::c0a8:11d/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::c0a8:131/64 scope link
valid_lft forever preferred_lft forever
This dump shows the traffic on my physical interface (IPv6 in IPv4 in PPPoE) which confirms that no firewall is prohibiting traffic going out (or in):
18:52:53.104371 PPPoE [ses 0x87e] IP 217.229.189.107 > 212.224.0.188: IP6 2001:6f8:900:849::2 > 2001:6f8:900:849::1: ICMP6, echo request, seq 18, length 64
There are no replies being received by my machine.
I can ping the IPv4 address of the tunnel endpoint.
grml@grml ~ % ping 212.224.0.188
PING 212.224.0.188 (212.224.0.188) 56(84) bytes of data.
64 bytes from 212.224.0.188: icmp_seq=1 ttl=57 time=69.7 ms
64 bytes from 212.224.0.188: icmp_seq=2 ttl=57 time=68.5 ms
Greetings from Bavaria,
Chris
State change: resolved
Jeroen Massar on Thursday, 22 October 2009 21:40:11
The state of this ticket has been changed to resolved
Tunnel
Jeroen Massar on Thursday, 22 October 2009 21:42:13
works here again:
64 bytes from 2001:6f8:900:849::2: icmp_seq=1 ttl=57 time=106 ms
Notes to your message:
This dump shows the traffic on my physical interface (IPv6 in IPv4 in PPPoE) which confirms that no firewall is prohibiting traffic going out (or in):
No, it only shows that at the point where you tcpdump that packet passes. It can be lost anywhere after that. Note also that for quite a few OSs you will see packets in tcpdump (pcap) but they will be filtered out by the actual stack just before hitting the network (and there it can of course be filtered by a lot of intermediate hops).
There are no replies being received by my machine.
Also no ICMP messages?
Tunnel deham01 working again
Shadow Hawkins on Friday, 23 October 2009 11:00:59
Hi Jeroen,
I know about the limitations of tcpdump/wireshark/... but wanted to point out that I was looking at the latest/earliest stage when packets enter/leave my machine. And the ethernet side of my PPPoE link is completely unfiltered, unlike the ppp-side which is.
There were no IPv6 messages (that includes ICMP echo replies) being received through the IPv6-tunnel yesterday, even though deham01 was pingable over IPv4.
Thanks a lot for your work, sorry for the inadequate subject of my bugreport.
Chris
Posting is only allowed when you are logged in. |