Tickets - Tunnel T118586 not able to reach any Google services, other IPV6 OK. :: SixXS

Ticket ID: SIXXS #12452097
Ticket Status: User

PoP: gblon02 - Goscomb Technologies (London)

Tunnel T118586 not able to reach any Google services, other IPV6 OK.

Shadow Hawkins on Tuesday, 07 October 2014 09:08:56

Good morning. Using the GBLON02 POP, I'm not able to use any Google services like gmail, search etc. However, all other IPV6 services are OK. I've rebooted everything this end, and can confirm all works when I disable IPV6. A V6 speedtest also works fine, as does a tracert. The situation has been going on since around 09:00 BST. I am on Plusnet using a Technicolor router configured with 6-in-4. Here's an example tracert - first ever bug report, so hope this is all OK. Thank you. (edit: this ticket system seems to take a long time (1+ minute) to generate, preview or submit a new ticket).

Tracing route to googlemail.l.google.com [2a00:1450:4009:80c::1015]
over a maximum of 30 hops:

  1     3 ms     4 ms     3 ms  cl-1694.lon-02.gb.sixxs.net [2a01:348:6:69d::2]
  2    50 ms    43 ms    53 ms  gw-1694.lon-02.gb.sixxs.net [2a01:348:6:69d::1]
  3    45 ms    59 ms    45 ms  gblon02.sixxs.net [2a01:348:0:4:0:3:1:1]
  4    73 ms    49 ms    46 ms  ge-0-0-5-20.cs0.thw.uk.goscomb.net [2a01:348:0:4:0:3:0:1]
  5    48 ms    48 ms    52 ms  xe-3-1.core00.the.uk.hso-group.net [2a01:348::65:0:1]
  6    60 ms    69 ms    76 ms  xe-3-1.core00.gs2.uk.hso-group.net [2a01:348::63:1:1]
  7    67 ms   100 ms    98 ms  xe-3-1.core00.sov.uk.hso-group.net [2a01:348::71:1:1]
  8    69 ms    39 ms    49 ms  2001:4860:1:1:0:999e:0:1
  9    76 ms    68 ms    71 ms  2001:4860::1:0:15f
 10    62 ms    57 ms    48 ms  2001:4860:0:1::1c3
 11    61 ms    56 ms    49 ms  lhr08s06-in-x15.1e100.net [2a00:1450:4009:80c::1015]

State change: user Locked

Jeroen Massar SixXS Staff

on Tuesday, 07 October 2014 12:12:10

The state of this ticket has been changed to user

Tunnel T118586 not able to reach any Google services, other IPV6 OK.

Jeroen Massar SixXS Staff

on Tuesday, 07 October 2014 12:14:49

(edit: this ticket system seems to take a long time (1+ minute) to generate, preview or submit a new ticket).

Which could be a result of problematic MTU issues and other such issues. As you are not providing any technical details, little we can tell about this. Note that Google is a far-away network, hence, we have little insight about what they do. At least those folks know not to drop ICMP and that PathMTU exists. You might want to peruse the forums to debug your setup. Also, as you might want to check with wireshark which protocols you are really using; it would not surprise me if something in your IPv6 connectivity is broken and that the 'timeout' is actually your browser falling back to IPv4.

Tunnel T118586 not able to reach any Google services, other IPV6 OK.

Shadow Hawkins on Thursday, 09 October 2014 11:53:49

For anyone else having this problem, I eventually found what was causing it. We have "Samknows Whitebox" which is a modified TP-LINK TL-WR741ND which monitors our broadband connection; without realising it, I'd moved the PC to a cable which was routed through this box. It evidently appears that this box can't handle 6in4, which is weird as I didn't realise a 6in4 packet appears any different to a router. Even odder is that it's ONLY google sites which affect it. Might email them about it - meanwhile, problem resolved by bypassing it.

Tunnel T118586 not able to reach any Google services, other IPV6 OK.

Jeroen Massar SixXS Staff

on Thursday, 09 October 2014 12:26:40

Jonathan Harris wrote:

Is that box doing passhtrough or is it doing NAT on the packets? Also, note that without touching every remote portion of the Internet it is unknown if only that destination is affected. There are a lot of combinations that can go weird. You might want to check with Wireshark when connecting in either location what the difference in packets/behavior is.

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