Tickets - T13710 is not working with plpoz1 :: SixXS

Ticket ID: SIXXS #9643890
Ticket Status: User

PoP: plpoz01 - Poznan Supercomputing and Networking Center (Poznan)

T13710 is not working with plpoz1

Shadow Hawkins on Friday, 28 June 2013 09:25:39

Hello, Tunnel T13710 to plpoz01 stopped working with no configuration changes on my (LFW-RIPE) side (I was on vacation at the time). I can reach plpoz1 IPv4 tunnel endpoint (it responds to icmp ping), but IPv6 tunnel endpoint is not pingable from T13710. IPv6 tunnel endpoint is pingable from my other tunnel, so it seems that problem is local to plpoz01 and T13710. T13710 information: I've disabled firewall but this didn't fixed the problem.

# uname -sr FreeBSD 9.1-RELEASE-p4 # ifconfig em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> ether 00:50:56:85:76:bf inet 176.122.227.43 netmask 0xffffff00 broadcast 176.122.227.255 inet6 fe80::250:56ff:fe85:76bf%em0 prefixlen 64 scopeid 0x1 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active enc0: flags=41<UP,RUNNING> metric 0 mtu 1536 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280 tunnel inet 176.122.227.43 --> 150.254.166.147 inet6 fe80::250:56ff:fe85:76bf%gif0 prefixlen 64 scopeid 0x4 inet6 2001:808:10f::1 prefixlen 48 inet6 2001:808:100:1a::2 --> 2001:808:100:1a::1 prefixlen 128 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> options=1<ACCEPT_REV_ETHIP_VER> pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33200 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 176.122.227.254 UGS 0 694 em0 127.0.0.1 link#3 UH 0 34 lo0 176.122.227.0/24 link#1 U 0 0 em0 176.122.227.43 link#1 UHS 0 0 lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRS lo0 => default 2001:808:100:1a::1 UGS gif0 ::1 link#3 UH lo0 ::ffff:0.0.0.0/96 ::1 UGRS lo0 2001:808:100:1a::1 link#4 UH gif0 2001:808:100:1a::2 link#4 UHS lo0 2001:808:10f::/48 link#4 U gif0 2001:808:10f::1 link#4 UHS lo0 fe80::/10 ::1 UGRS lo0 fe80::%em0/64 link#1 U em0 fe80::250:56ff:fe85:76bf%em0 link#1 UHS lo0 fe80::%lo0/64 link#3 U lo0 fe80::1%lo0 link#3 UHS lo0 fe80::%gif0/64 link#4 U gif0 fe80::250:56ff:fe85:76bf%gif0 link#4 UHS lo0 ff01::%em0/32 fe80::250:56ff:fe85:76bf%em0 U em0 ff01::%lo0/32 ::1 U lo0 ff01::%gif0/32 fe80::250:56ff:fe85:76bf%gif0 U gif0 ff02::/16 ::1 UGRS lo0 ff02::%em0/32 fe80::250:56ff:fe85:76bf%em0 U em0 ff02::%lo0/32 ::1 U lo0 ff02::%gif0/32 fe80::250:56ff:fe85:76bf%gif0 U gif0 # traceroute 150.254.166.147 traceroute to 150.254.166.147 (150.254.166.147), 64 hops max, 40 byte packets 1 176.122.227.254 (176.122.227.254) 1.193 ms 1.477 ms 0.727 ms 2 176.122.215.246 (176.122.215.246) 0.976 ms 1.053 ms 0.870 ms 3 77-252-107-153.ip.netia.com.pl (77.252.107.153) 14.963 ms 13.379 ms 13.766 ms 4 WarsB010RT06-WarsC001RT06.inetia.pl (81.210.126.254) 20.513 ms WarsB010RT06-WarsC001RT06.inetia.pl (81.210.126.252) 21.078 ms WarsB010RT06-WarsC001RT06.inetia.pl (81.210.126.254) 21.306 ms 5 83.238.248.53 (83.238.248.53) 19.991 ms 22.209 ms 19.817 ms 6 PoznH002RT09-PoznH002RT16.inetia.pl (83.238.251.217) 20.207 ms 22.187 ms 21.633 ms 7 css5-XE0-0-0-1116.man.poznan.pl (212.126.28.210) 18.682 ms 19.011 ms 23.868 ms 8 css6-XE0-2-0-60.man.poznan.pl (150.254.210.230) 37.054 ms 36.696 ms 36.670 ms 9 chives.man.poznan.pl (150.254.166.147) 36.764 ms 37.358 ms 37.245 ms # ping -c3 150.254.166.147 PING 150.254.166.147 (150.254.166.147): 56 data bytes 64 bytes from 150.254.166.147: icmp_seq=0 ttl=46 time=36.919 ms 64 bytes from 150.254.166.147: icmp_seq=1 ttl=46 time=36.858 ms 64 bytes from 150.254.166.147: icmp_seq=2 ttl=46 time=36.774 ms --- 150.254.166.147 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 36.774/36.850/36.919/0.059 ms # ping6 -c 3 2001:808:100:1a::1 PING6(56=40+8+8 bytes) 2001:808:100:1a::2 --> 2001:808:100:1a::1 --- 2001:808:100:1a::1 ping6 statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss

What other information should I provide to help resolve the issue? Thank you in advance.

T13710 is not working with plpoz1

Jeroen Massar SixXS Staff

on Sunday, 30 June 2013 20:59:13

As per the PoP's live tunnel status (log in to your user home, select the tunnel from the list and click on the link there), the PoP has been sending your packets but none are being answered. You'll have to start digging into your configuration to figure out what is going wrong. A tcpdump to see if proto-41 is being sent/received is likely a good start.

T13710 is not working with plpoz1

Shadow Hawkins on Monday, 08 July 2013 17:40:44

I have read and followed the "Reporting Problems" section on the Contact page. I am removing these pre-filled lines to demonstrate that I really read it. I am providing the full details as requested on the mentioned Contact page. If I do not remove this, then please ignore this message as I didn't read it anyway.
You're right, my ISP blocked proto 41 without notice. It's fixed now, thank you.

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