Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by fenton, May 20, 2013, 10:00:21 PM
Quote from: fenton on May 21, 2013, 10:33:25 AMSure; here's the result (I asked for the AAAA result as well since that's what's probably relevant here)
Quote from: fenton on May 21, 2013, 10:33:25 AMGoogle did an HTTP redirect to google.com.tw, so I don't think that it's directly DNS redirecting me to the wrong place, but rather that when I get there, Google decides I'm in Taiwan, and sends me the redirect.
Quote from: kasperd on May 21, 2013, 12:53:32 PMThe only detail that I can't get to make sense yet, is why I have been able to reproduce the misdirecting DNS replies but not the redirect to google.tw. I'll have to give that another try.
telnet www.google.com 80Trying 22.214.171.124...Connected to www.google.com.Escape character is '^]'.HEAD / HTTP/1.0Host: www.google.comHTTP/1.0 302 FoundLocation: http://www.google.dk/
telnet www.google.com 80Trying 2a00:1450:4013:c00::6a...Connected to www.google.com.Escape character is '^]'.HEAD / HTTP/1.0Host: www.google.comHTTP/1.0 200 OK
QuoteThe other point where you are misdirected is when you are being redirected to the wrong country domain. With a few exceptions, Google will redirect every visitor on google.com to a country specific domain. On the country specific domain, you will find a link back to google.com, which will also set a cookie, stopping the redirection in the future.
Quote from: fenton on May 22, 2013, 08:58:33 AMfenton@kernel:~$ telnet -6 www.google.com 80Trying 2001:4860:4001:803::1014...Connected to www.google.com.Escape character is '^]'.HEAD / HTTP/1.0Host: www.google.comHTTP/1.0 302 FoundLocation: http://www.google.com.tw/(etc)
QuoteGoogle has had the location of each tunnel server, and which prefixesare associated with each one, but why they're not using that informationnow, I don't know. We've reached out to them, but haven't had a replyas of yet. Wouldn't hurt to let them know that their geolocation is notworking properly, in any case.
Quote from: fenton on May 24, 2013, 06:27:00 AMSo he.net is indeed trying, but it wouldn't hurt for us to send reports to Google as well. Once again, the reporting address is:https://support.google.com/websearch/contact/ip
Quote from: fenton on May 24, 2013, 06:38:55 AMI did this, and gave 2001:470:1f05:bfe::/64 as the address which it didn't accept. My immediate reaction was, "oh great, they don't understand IPv6 addresses" but it did accept 2001:470:1f05:bfe:: which hopefully they will interpret as a /64.But who knows what they'll do with a /48.
Quote from: ingber on May 23, 2013, 04:28:27 PMI reported this to he.net on 9 May 2013. Support tried to be helpful, but basically I was told that "sh*t happens".I also contacted google support, and they admitted they could not help. I filed a form with them wherein it was explained that it could take a month for them to get to such cases, if they could be fixed.However, I tried using Iexplorer, Firefox, and Chrome, to several sites, not just google, and using google dns as well as opendns, on two independent PCs behind my router that is registering this tunnel. The real problem is that the tunnel broker IPv6 address is just not being registered worldwide properly.I still have this annoying problem as of today.I think everyone posting here should file a ticket with he.net support. They are the best hope for correcting their own IP addresses.