|
Ticket ID: SIXXS #10694706 Ticket Status: User PoP: gblon02 - Goscomb Technologies (London)
T122970 Problems
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Monday, 16 December 2013 04:30:24
Since 9pm on Tuesday 10th December, I have been unable to ping out from my SixXS tunnel on gblon02. A tcpdump shows the pings are getting out over the sixxs interface but there is no response:
10:45:33.819541 IP6 cl-1747.lon-02.gb.sixxs.net >
gw-1747.lon-02.gb.sixxs.net: ICMP6, echo request, seq 1, length 64
I tried pinging the IPv4 address of my PoP and this worked fine and a traceroute to this also showed no problems:
traceroute to 77.75.104.126 (77.75.104.126), 30 hops max, 60 byte packets
1 iam-router.core.ecs.soton.ac.uk (152.78.65.254) 3.678 ms 3.589 ms 3.570 ms
2 fw2.core.ecs.soton.ac.uk (152.78.70.228) 3.674 ms 3.634 ms 3.969 ms
3 152.78.108.6 (152.78.108.6) 10.681 ms 10.294 ms 10.064 ms
4 b54xagesw1-ba.net.soton.ac.uk (152.78.108.137) 7.213 ms 6.991 ms 6.357 ms
5 b54gafwc1-int.net.soton.ac.uk (152.78.109.7) 5.501 ms 7.743 ms 4.148 ms
6 b54gagesw2-hafw.net.soton.ac.uk (152.78.0.30) 5.944 ms 7.745 ms 7.975 ms
7 212.219.151.113 (212.219.151.113) 7.071 ms 7.052 ms 7.146 ms
8 195.194.38.33 (195.194.38.33) 6.900 ms 6.245 ms 6.094 ms
9 195.194.38.158 (195.194.38.158) 5.859 ms 5.476 ms 3.810 ms
10 ae3.bradss-sbr1.ja.net (146.97.41.1) 27.451 ms * 26.821 ms
11 ae27.londpg-sbr1.ja.net (146.97.33.33) 11.424 ms 11.357 ms 8.309 ms
12 ae30.londtw-sbr1.ja.net (146.97.33.6) 9.516 ms 10.133 ms 10.271 ms
13 ae29.londtn-sbr1.ja.net (146.97.33.10) 10.660 ms 10.539 ms 10.436 ms
14 ae0.lond-gw-ixp4.ja.net (146.97.35.182) 10.625 ms 10.475 ms 10.422 ms
15 xe-0-0-0-0.edge00.thn.uk.hso-group.net (195.66.224.226) 9.779 ms 10.659 ms 9.851 ms
16 ae0.cs0.thn.uk.goscomb.net (46.17.60.181) 15.175 ms 14.579 ms 13.718 ms
17 xe-0-1-1.cs0.thw.uk.goscomb.net (93.89.94.202) 12.181 ms 12.572 ms 12.359 ms
18 gblon02.sixxs.net (77.75.104.126) 11.725 ms 11.768 ms 11.556 ms
Running a traceroute6 to 2a01:348:6:6d2::1 (the tunnel's PoP) from the tunnel endpoint just timed out each time.
Before the tunnel was blocked for excessive aiccu restarts, no error messages appeared when I ran aiccu restart of aiccu test, I just saw the following status information:
Tunnel Information for T122970:
POP Id : gblon02
IPv6 Local : 2a01:348:6:6d2::2/64
IPv6 Remote : 2a01:348:6:6d2::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
I hadn't changed anything on my endpoint device the day that the tunnel ceased to work. Below are the v4 and v6 routing tables on this device, which as far as I can tell do not show anything to explain why I cannot get IPv6 pings back from the tunnel's PoP:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default iam-router.core 0.0.0.0 UG 0 0 0 eth1
10.0.0.0 * 255.255.255.0 U 0 0 0 eth0
10.0.1.0 * 255.255.255.0 U 0 0 0 wlan0
152.78.64.0 * 255.255.254.0 U 0 0 0 eth1
152.78.94.0 * 255.255.255.0 U 0 0 0 wlan1
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
::/96 :: Un 256 0 0 sit0
2a01:348:6:6d2::/64 :: U 256 0 1 sixxs
2a01:348:6:86d2::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 eth1
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 wlan0
fe80::/64 :: U 256 0 0 sixxs
fe80::/64 :: U 256 0 0 wlan1
::/0 2a01:348:6:6d2::1 UG 1024 0 0 sixxs
::/0 :: !n -1 1 26881 lo
::1/128 :: Un 0 1552514 lo
::10.0.0.1/128 :: Un 0 1 0 lo
::10.0.1.1/128 :: Un 0 1 0 lo
::127.0.0.1/128 :: Un 0 1 0 lo
::152.78.65.82/128 :: Un 0 1 0 lo
::152.78.94.82/128 :: Un 0 1 0 lo
2a01:348:6:6d2::/128 :: Un 0 1 0 lo
2a01:348:6:6d2::2/128 :: Un 0 1 0 lo
2a01:348:6:86d2::/128 :: Un 0 1 0 lo
2a01:348:6:86d2::1/128 :: Un 0 1 654 lo
fe80::/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::/128 :: Un 0 1 0 lo
fe80::48:6:6d2:2/128 :: Un 0 1 0 lo
fe80::21f:1fff:fecb:d294/128 :: Un 0 1 0 lo
fe80::280:c8ff:fe3b:1ab8/128 :: Un 0 1 0 lo
fe80::ba27:ebff:fed8:15cd/128 :: Un 0 1 74 lo
ff00::/8 :: U 256 0 0 eth1
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 wlan0
ff00::/8 :: U 256 0 0 sixxs
ff00::/8 :: U 256 0 0 wlan1
::/0 :: !n -1 1 26881 lo
Any help on resolving this matter would be most appreciated, as I really have no idea what might be going wrong.
David Newman (on behalf of Kirk Martinez)
T122970 Problems
A tcpdump shows the pings are getting out over the sixxs interface but there is no response:
That only shows that your host is sending the packet on the virtual interface.
As mentioned on the contact page
"* Check with Wireshark or tcpdumps of the interface over which the tunnel runs."
This as then you would see the tunneled packet going outbound and possibly any ICMPv4 errors if there are any.
Running a traceroute6 to 2a01:348:6:6d2::1 (the tunnel's PoP) from the tunnel endpoint just timed out each time.
If your tunnel does not work, then that is not going to work. Also note that as it is a PtP tunnel that would only be one single hop, and thus would equal a ping.
Any help on resolving this matter would be most appreciated, as I really have no idea what might be going wrong.
Please read the Contact page's "Reporting problems / Troubleshooting / Checklist" and provide all the details requested there.
According to the Live Tunnel status the last successful heartbeat, and thus AYIYA packet, was about 13 hours ago. Around that same time there where also ICMPv4 errors reported from your side of the tunnel.
T122970 Problems
Shadow Hawkins on Thursday, 02 January 2014 23:33:30
Sorry it took a while to get back to you. I was waiting until the temporary ban expired for too many aiccu restarts and then a combination of a power outage in the office whilst I was away over Christmas has meant this is the first opportunity I have had to do some more investigation:
Running TCPDump on the sixxs interface and then running ping6 -5 ipv6.google.com and then ping6 -5 2a01:348:6:6d2::1 (tunnel PoP), I get:
23:04:14.840011 IP6 cl-1747.lon-02.gb.sixxs.net > lhr14s21-in-x14.1e100.net: ICMP6, echo request, seq 1, length 64
23:04:15.846800 IP6 cl-1747.lon-02.gb.sixxs.net > lhr14s21-in-x14.1e100.net: ICMP6, echo request, seq 2, length 64
23:04:16.846635 IP6 cl-1747.lon-02.gb.sixxs.net > lhr14s21-in-x14.1e100.net: ICMP6, echo request, seq 3, length 64
23:04:17.846666 IP6 cl-1747.lon-02.gb.sixxs.net > lhr14s21-in-x14.1e100.net: ICMP6, echo request, seq 4, length 64
23:04:18.846691 IP6 cl-1747.lon-02.gb.sixxs.net > lhr14s21-in-x14.1e100.net: ICMP6, echo request, seq 5, length 64
23:10:44.179632 IP6 cl-1747.lon-02.gb.sixxs.net > gw-1747.lon-02.gb.sixxs.net: ICMP6, echo request, seq 1, length 64
23:10:45.186915 IP6 cl-1747.lon-02.gb.sixxs.net > gw-1747.lon-02.gb.sixxs.net: ICMP6, echo request, seq 2, length 64
23:10:46.186648 IP6 cl-1747.lon-02.gb.sixxs.net > gw-1747.lon-02.gb.sixxs.net: ICMP6, echo request, seq 3, length 64
23:10:47.186653 IP6 cl-1747.lon-02.gb.sixxs.net > gw-1747.lon-02.gb.sixxs.net: ICMP6, echo request, seq 4, length 64
23:10:48.186659 IP6 cl-1747.lon-02.gb.sixxs.net > gw-1747.lon-02.gb.sixxs.net: ICMP6, echo request, seq 5, length 64
Where the ping output unsuprisingly looks like:
PING ipv6.google.com(lhr14s21-in-x14.1e100.net) 56 data bytes
--- ipv6.google.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4006ms
PING 2a01:348:6:6d2::1(2a01:348:6:6d2::1) 56 data bytes
--- 2a01:348:6:6d2::1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4007ms
As you can see from my original message there is nothing out of the ordinary in the IPv6 routing table. So I can only think it is something wrong Goscomb's end or there is something blocking the ping6 responses. A server in a similar location to the tunnel endpoint that has native IPv6 can successfully ping6 the tunnel PoP IP. Maybe something is being blocked in the AYIYA protocol rather than the ping6 responses themselves at my institutional (University of Southampton) firewall level. However, it seems unlikely if Aiccu could set up the tunnel up in the first place.
|
![[ch]](/s/countries/ch.gif)
on Monday, 16 December 2013 09:39:44
Posting is only allowed when you are