Forum - Ayiya tunnel on bebru01 stopped working :: SixXS

Ayiya tunnel on bebru01 stopped working

Shadow Hawkins on Tuesday, 25 October 2011 18:23:45

My ayiya tunnel on bebru01 stopped working since 23th. Nothing change on router, and the remote IPv6 endpoint isn't pinging. ping6 2001:6f8:202:2b1::1 PING 2001:6f8:202:2b1::1 (2001:6f8:202:2b1::1): 56 data bytes ^C --- 2001:6f8:202:2b1::1 ping statistics --- 6 packets transmitted, 0 packets received, 100% packet loss The remote endpoint is not pinging from another network. ping6 2001:6f8:202:2b1::1 PING 2001:6f8:202:2b1::1(2001:6f8:202:2b1::1) 56 data bytes From 2001:6f8:200:1003::10 icmp_seq=0 Destination unreachable: No route From 2001:6f8:200:1003::10 icmp_seq=1 Destination unreachable: No route File ticket ?

Ayiya tunnel on bebru01 stopped working

Jeroen Massar SixXS Staff

on Tuesday, 25 October 2011 18:45:52

From 2001:6f8:200:1003::10 icmp_seq=0 Destination unreachable: No route

That is the PoP saying that no valid packets have been received and thus that your tunnel is down. See the FAQ for all the info on figuring out what might be wrong.

Ayiya tunnel on bebru01 stopped working

Shadow Hawkins on Thursday, 27 October 2011 02:11:10

tcpdump on external interface shows ayiya going out as 5072: UDP, length 148 packets. - Firewalling disabled. - NTP synced. Traceroute on port 5072 works. The problem, is that there's no AYIYA reply coming.

Ayiya tunnel on bebru01 stopped working

Jeroen Massar SixXS Staff

on Thursday, 27 October 2011 14:59:39

tcpdump on external interface shows ayiya going out as 5072: UDP, length 148 packets.

What is the path these packets take? 148 bytes would indicate just heartbeats, thus no real packets. You don't see anything else?

- Firewalling disabled.

On which host, and what about the intermediate hops to the PoP?

Traceroute on port 5072 works.

I assume that you mean a UDP based traceroute? (eg traceroute -U -p 5072 <pop> ?) Can you show the command and output of that?

The problem, is that there's no AYIYA reply coming.

If those packets are not valid it will not send a response no.

Ayiya tunnel on bebru01 stopped working

Shadow Hawkins on Thursday, 27 October 2011 23:25:19

148 bytes packets are generated by pings going through tunnel. dumps & pings being done directly from router. Router is connected to box/modem.

root@OpenWrt:~# traceroute -p 5072 212.100.184.146 traceroute to 212.100.184.146 (212.100.184.146), 30 hops max, 38 byte packets 1 192.168.254.254 (192.168.254.254) 47.819 ms 48.731 ms 193.316 ms 2 bzn-6k-5-v201.routers.proxad.net (212.27.55.126) 47.741 ms * * 3 th2-crs16-1-be1200.intf.routers.proxad.net (212.27.50.193) 48.914 ms 48.735 ms 49.440 ms 4 te0-0-0-1.332.ccr21.par04.atlas.cogentco.com (149.6.164.217) 49.215 ms 48.200 ms 49.443 ms 5 te0-2-0-4.ccr22.par01.atlas.cogentco.com (130.117.48.149) 48.239 ms te0-5-0-2.ccr22.par01.atlas.cogentco.com (154.54.58.229) 49.224 ms te0-3-0-4.ccr22.par01.atlas.cogentco.com (154.54.38.225) 48.784 ms 6 te0-0-0-1.ccr22.lon13.atlas.cogentco.com (130.117.50.17) 57.279 ms 154.54.59.25 (154.54.59.25) 56.876 ms multi-use.cogentco.com (154.54.37.209) 56.295 ms 7 level3.lon01.atlas.cogentco.com (130.117.14.198) 105.912 ms level3.lon01.atlas.cogentco.com (130.117.15.82) 55.823 ms level3.lon01.atlas.cogentco.com (130.117.14.198) 56.153 ms 8 * * * 9 195.50.122.106 (195.50.122.106) 61.318 ms 56.528 ms 58.306 ms 10 ge2-0-9.gr10.gdbru.be.easynet.net (87.86.77.73) 67.951 ms * * 11 ge3-1-114.br10.gdbru.be.easynet.net (87.86.71.165) 67.742 ms 65.959 ms 66.935 ms 12 ge0-0.cr3.gdbru.be.easynet.net (212.100.161.14) 66.696 ms 66.707 ms 67.176 ms 13 212.100.184.146 (212.100.184.146) 67.432 ms 67.399 ms 66.906 ms

As I mentioned, it suddenly stopped working on the 23th.

root@OpenWrt:~# ip tun sit0: ipv6/ip remote any local any ttl 64 nopmtudisc

Ayiya doesn't create an additional tunnel right ?

Ayiya tunnel on bebru01 stopped working

Jeroen Massar SixXS Staff

on Friday, 28 October 2011 11:09:47

root@OpenWrt:~# ip tun

sit0: ipv6/ip remote any local any ttl 64 nopmtudisc

Ayiya doesn't create an additional tunnel right ?

AICCU uses the TUN/TAP device for AYIYA tunnels, and that is a different device. If you would read the contact page's "Reporting Problems" section, then you would have seen the list of details that might be useful for determining problems, it also has "list interfaces", not just the tunnel devices.

Ayiya tunnel on bebru01 stopped working

Shadow Hawkins on Friday, 04 November 2011 15:26:40

I've sent more details to info@ few days ago. I just have requested another ayiya tunnel from another provider. Works with that new tunnel_id.

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