• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

google is blocked through my tunnel

Started by drookie, September 14, 2012, 04:26:31 AM

Previous topic - Next topic

drookie

Hi.

Seems like starting from today's morning (GMT+5 here) google is blocked through my tunnel:

[emz@taiga:/<2>etc/squid]# traceroute6 -I google.com
traceroute6 to google.com (2a00:1450:4010:c04::64) from 2001:470:1f08:14c0::2, 64 hops max, 16 byte packets
1  drookie-1.tunnel.tserv5.lon1.ipv6.he.net  93.431 ms  93.604 ms  93.478 ms
2  gige-g4-8.core1.lon1.he.net  100.132 ms  99.376 ms  119.673 ms
3  2001:7f8:4::3b41:1  89.780 ms !P  89.288 ms !P  89.828 ms !P

As far as I understand !P means it's blocked by a filter. Why ?

Although other destinations seem to be fine:

[emz@taiga:/<2>etc/squid]# traceroute6 -I freebsd.org
traceroute6 to freebsd.org (2001:4f8:fff6::28) from 2001:470:1f08:14c0::2, 64 hops max, 16 byte packets
1  drookie-1.tunnel.tserv5.lon1.ipv6.he.net  94.268 ms  93.638 ms  94.540 ms
2  gige-g4-8.core1.lon1.he.net  89.751 ms  99.511 ms  89.074 ms
3  10gigabitethernet7-4.core1.nyc4.he.net  157.830 ms  170.427 ms  160.044 ms
4  10gigabitethernet2-3.core1.ash1.he.net  162.757 ms  167.841 ms  163.411 ms
5  10gigabitethernet1-2.core1.atl1.he.net  178.996 ms  176.740 ms  175.829 ms
6  isc.gige-g2-1.core1.atl1.he.net  175.007 ms  182.927 ms  174.769 ms
7  iana.r1.atl1.isc.org  174.934 ms  175.580 ms  174.946 ms
8  int-0-5-0-1.r1.pao1.isc.org  253.428 ms  234.479 ms  235.409 ms
9  int-0-0.r3.pao1.isc.org  234.505 ms  234.237 ms  234.473 ms
10  ipv6gw-isc.freebsd.org  234.958 ms  249.957 ms  235.265 ms
11  freefall.freebsd.org  235.527 ms  235.017 ms  235.289 ms

[emz@taiga:/<2>etc/squid]# traceroute6 -I facebook.com
traceroute6: Warning: facebook.com has multiple addresses; using 2a03:2880:10:cf01:face:b00c::
traceroute6 to facebook.com (2a03:2880:10:cf01:face:b00c::) from 2001:470:1f08:14c0::2, 64 hops max, 16 byte packets
1  drookie-1.tunnel.tserv5.lon1.ipv6.he.net  94.276 ms  94.213 ms  93.836 ms
2  gige-g4-8.core1.lon1.he.net  99.334 ms  95.447 ms  89.525 ms
3  2001:7f8:4::80a6:1  163.071 ms  163.392 ms  163.196 ms
4  ae15.bb02.iad2.tfbnw.net  171.144 ms  163.244 ms  163.111 ms
5  ae8.bb04.prn1.tfbnw.net  234.104 ms  233.929 ms  233.946 ms
6  ae3.dr05.prn1.tfbnw.net  234.985 ms  237.488 ms  234.900 ms
7  2620:0:1cff:dead:beee::2bd  235.370 ms  235.355 ms  235.520 ms
8  www6-slb-10-12-prn1.facebook.com  241.408 ms  245.831 ms  235.490 ms

My tunnel:

gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
        tunnel inet 89.250.210.67 --> 216.66.80.26
        inet6 2001:470:1f08:14c0::2 --> 2001:470:1f08:14c0::1 prefixlen 128
        inet6 fe80::21a:64ff:fec6:a87c%gif0 prefixlen 64 scopeid 0x1e
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        options=1<ACCEPT_REV_ETHIP_VER>

Thanks.

kcochran

That !P is a response from a Google router.  Looks like something may be amiss in their EU network.

drookie


kasperd

I send an email with information about this outage to someone I know at Google. I hope he isn't on vacation.

kasperd

Quote from: kasperd on September 14, 2012, 05:13:21 AMI send an email with information about this outage to someone I know at Google.
I didn't hear back yet. But it looks like they got the problematic IPv6 address removed from DNS and replaced with a functional one.

drookie

Quote from: kasperd on September 14, 2012, 08:08:27 AM
Quote from: kasperd on September 14, 2012, 05:13:21 AMI send an email with information about this outage to someone I know at Google.
I didn't hear back yet. But it looks like they got the problematic IPv6 address removed from DNS and replaced with a functional one.

Thank you a lot. It works for me now.