Reaching google.com using Chrome

Brian E Carpenter brian.e.carpenter at gmail.com
Mon Jan 13 23:16:47 CET 2014


On 14/01/2014 10:21, Justin Krejci wrote:
> Also when troubleshooting HTTP connectivity in general but can be really help when dealing with a transition from IPv4 to IPv6 if you install the browser extension IPvFoo for Chrome (IPvFox for Firefox) it can take out a significantly complicated step in the troubleshooting process as it easily shows you all of the IP addresses (v4 and v6) being connected to on any given page and which are SSL and or non-SSL as well. It's very small and quite useful.

Thanks for that - nicer than ShowIP on Firefox. If you're running ShowIP, you need to
disable it when installing IPvFox.

   Brian

> ________________________________________
> From: ipv6-ops-bounces+jkrejci=usinternet.com at lists.cluenet.de [ipv6-ops-bounces+jkrejci=usinternet.com at lists.cluenet.de] on behalf of Jeroen Massar [jeroen at massar.ch]
> Sent: Monday, January 13, 2014 12:13 PM
> To: Sammer Mati; ipv6-ops at lists.cluenet.de
> Subject: Re: Reaching google.com using Chrome
> 
> On 2014-01-13 19:02 , Sammer Mati wrote:
> [..]
>> We ran wireshark and found out that the IPv6 address is different for
>> Google.com when using IE or Chrome! I haven't tested yet with Windows7
> 
> That is just pure DNS selection luck...
> 
> Note that a lot of properties on this massive Internet are using
> Geo-DNS, load-balancing, BGP-based routing tricks/anycasting and a lot
> of other nasty funny tricks.
> 
> Hence, as you did not include any traceroute or other data, little else
> anybody can say...
> 
> Greets,
>  Jeroen
> 
> 


More information about the ipv6-ops mailing list