|
Ticket ID: SIXXS #5243694 Ticket Status: User PoP: gblon03 - Gyron Internet LTD - Limited UK Company (London)
Incoming pings from tunnel are not working
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Friday, 22 July 2011 09:01:48
Hi,
I upgraded my OpenWrt setup over the weekend and I am now gettting ping failures from SIXXS.
Tunnel:
Handle : AMK6-SIXXS
PoP Name : gblon03 (uk.gyron [AS29017])
Your Location: Maidenhead, gb
SixXS IPv6 : 2a00:14f0:e000:3c::1/64
Your IPv6 : 2a00:14f0:e000:3c::2/64
SixXS IPv4 : 212.113.147.150
Your IPv4 : 78.86.192.94
Last known responding: 2011-07-20 09:52:02
As far as I can see the OOB openwrt setup is set to respond to all pings.
As a test I logged in to another SIXXS tunnel that I own and pinged the endpoint of this tunnel:
diamondhead:~ adrian$ ping6 2a00:14f0:e000:3c::2
PING6(56=40+8+8 bytes) 2a01:348:168::<obscured> --> 2a00:14f0:e000:3c::2
16 bytes from 2a00:14f0:e000:3c::2, icmp_seq=0 hlim=51 time=456.042 ms
Request timeout for icmp_seq=1
16 bytes from 2a00:14f0:e000:3c::2, icmp_seq=2 hlim=51 time=442.986 ms
16 bytes from 2a00:14f0:e000:3c::2, icmp_seq=3 hlim=51 time=384.404 ms
16 bytes from 2a00:14f0:e000:3c::2, icmp_seq=4 hlim=51 time=174.914 ms
If I were blocking pings then surely this ping would not work.
Can you suggest what the problem might be?
Thanks,
Adrian
Incoming pings from tunnel are not working
16 bytes from 2a00:14f0:e000:3c::2, icmp_seq=0 hlim=51 time=456.042 ms
Is that a round trip twice around the world?
If I were blocking pings then surely this ping would not work.
What is the route that the packets take. The PoP will ping you only over the tunnel, not half around the world.
Please actually read that big yellow/orange box and provide ALL the requested details, especially your running configuration (routing tables etc) are very useful.
Do also read the FAQ item on 'my endpoint does not ping' it contains lots of useful hints. It is a FAQ afterall.
Traceroute doesn't get there, nor does ping:
$ traceroute6 2a00:14f0:e000:3c::2
traceroute to 2a00:14f0:e000:3c::2 (2a00:14f0:e000:3c::2), 30 hops max, 80 byte packets
1 ge-1-3-0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.482 ms 0.618 ms 0.728 ms
2 gi2-11.nikhef.ipv6.concepts-ict.net (2001:838:5:a::1) 1.959 ms 1.977 ms 2.013 ms
3 ge-1-0-8.border-1.thn.lon.uk.as29017.net (2001:7f8:1::a502:9017:1) 12.327 ms 12.464 ms 12.333 ms
4 ae4.core-2.lhc.lon.uk.as29017.net (2a00:14f0:0:1::16) 12.352 ms 12.441 ms 12.423 ms
5 gblon03.sixxs.net (2a00:14f0:1:2::5) 12.429 ms 12.411 ms 12.458 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 *^C
$ ping6 2a00:14f0:e000:3c::2
PING 2a00:14f0:e000:3c::2(2a00:14f0:e000:3c::2) 56 data bytes
^C
--- 2a00:14f0:e000:3c::2 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms
Incoming pings from tunnel are not working
Shadow Hawkins on Sunday, 24 July 2011 18:36:26
OK all fixed once I realised it was pinging the IPv4 protocol 41 end of the tunnel not the IPv6 endpoint.
Thanks for the pointers.
State change: user
The state of this ticket has been changed to user
|
![[ch]](/s/countries/ch.gif)
on Friday, 22 July 2011 10:16:18
Posting is only allowed when you are