Tickets - Tunnel router unable to respond to ping :: SixXS

Ticket ID: SIXXS #11499069
Ticket Status: User

PoP: gblon03 - Gyron Internet LTD - Limited UK Company (London)

Tunnel router unable to respond to ping

Carmen Sandiego on Thursday, 24 April 2014 08:05:54

I have an issue with my new router required for my new broadband connection: Due to a software bug, it is unable to respond to pings to the tunnel interface (packets originating from the router itself never make it out of the router when running a tunnel over PPPoE). There is no fix available at this time. Unfortunately, this means that my tunnel fails the ping test yet it is working perfectly fine and traffic flows perfectly in and out of the tunnel. Is there a way to keep the tunnel up and enabled despite not responding to pings, at least until a fix can be found? Thanks in advance. Jens Fallesen Tunnel ID: T92090 Ping from tunnel router:

swi-r1#ping 2A00:14F0:E000:99::2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2A00:14F0:E000:99::2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms swi-r1#ping 2A00:14F0:E000:99::1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2A00:14F0:E000:99::1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) swi-r1#

Ping from server on the inside:

tardis:~$ ping6 2A00:14F0:E000:99::1 PING6(56=40+8+8 bytes) 2a00:14f0:e000:8099::eeee --> 2a00:14f0:e000:99::1 16 bytes from 2a00:14f0:e000:99::1, icmp_seq=0 hlim=63 time=30.449 ms 16 bytes from 2a00:14f0:e000:99::1, icmp_seq=1 hlim=63 time=30.027 ms 16 bytes from 2a00:14f0:e000:99::1, icmp_seq=2 hlim=63 time=30.292 ms ^C --- 2A00:14F0:E000:99::1 ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 30.027/30.256/30.449/0.174 ms tardis:~$ ping6 2A00:14F0:E000:99::2 PING6(56=40+8+8 bytes) 2a00:14f0:e000:8099::eeee --> 2a00:14f0:e000:99::2 16 bytes from 2a00:14f0:e000:99::2, icmp_seq=0 hlim=64 time=0.621 ms 16 bytes from 2a00:14f0:e000:99::2, icmp_seq=1 hlim=64 time=0.464 ms 16 bytes from 2a00:14f0:e000:99::2, icmp_seq=2 hlim=64 time=0.510 ms ^C --- 2A00:14F0:E000:99::2 ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.464/0.532/0.621/0.066 ms tardis:~$ ping6 www.google.com PING6(56=40+8+8 bytes) 2a00:14f0:e000:8099::eeee --> 2a00:1450:4009:808::1014 16 bytes from 2a00:1450:4009:808::1014, icmp_seq=0 hlim=56 time=32.309 ms 16 bytes from 2a00:1450:4009:808::1014, icmp_seq=1 hlim=56 time=32.537 ms 16 bytes from 2a00:1450:4009:808::1014, icmp_seq=2 hlim=56 time=32.556 ms ^C --- www.google.com ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 32.309/32.467/32.556/0.112 ms tardis:~$

Tunnel router unable to respond to ping

Jeroen Massar SixXS Staff

on Thursday, 24 April 2014 08:12:11

(This is obviously not a technical problem with the SixXS service, hence this question really belongs in the Forums....)

I have an issue with my new router

What kind of router? Brand/Model/versions?

Is there a way to keep the tunnel up and enabled despite not responding to pings, at least until a fix can be found?

Only static tunnels have a requirement to ping. If they do not ping they get disabled. Heartbeat and AYIYA tunnels are not required to ping, though they are checked.

Tunnel router unable to respond to ping

Carmen Sandiego on Thursday, 24 April 2014 14:45:03

I am aware it is not a technical problem. It is more of a policy problem: I.e. is it possible to disable the ping check requirement? This is why I opened a ticket rather than asking in the forum. The router is a Cisco 1921 running IOS 15.4(2)T. Tested with several firmware versions and all are affected.

Tunnel router unable to respond to ping

Jeroen Massar SixXS Staff

on Thursday, 24 April 2014 14:49:34

I.e. is it possible to disable the ping check requirement?

No, the check cannot be disabled. Static tunnels are required to respond to ICMPv6 on their tunnel endpoint.

The router is a Cisco 1921 running IOS 15.4(2)T. Tested with several firmware versions and all are affected.

IOS has had fully functional IPv6 tunneling since 1996. You likely have either a route or ACL mis-configured. Use the forums for figuring this out by providing full details there.

Tunnel router unable to respond to ping

Carmen Sandiego on Thursday, 24 April 2014 15:10:05

Believe me, it is a problem with the software on the router - not a configuration issue. Full troubleshooting and tracing has been done and it has been confirmed to me that there is a problem with the combination of the tunnel and PPPoE in this software. But thanks for confirming about the pings. I will disable the tunnel until I have a fix.

Please note Posting is only allowed when you are logged in.