AFAIK you have to have native peering with them to be part of the
pilot. At least, you did when we signed up. They may have relaxed
that since.
According to a Google IPv6 talk I attended yesterday, they don't
intend to relax that rule. Tunneling ipv6 connectivity over ipv4 is
trash
On 1 Apr 2009, at 11:19, TJ wrote:
You do not (or, atleast I do not :)) have the option of connecting
to Google over MPLS, Ethernet, etc.
r1.owls#show arp | inc 198.32.245.6
Internet 198.32.245.62 001f.128e.56f2 ARPA
FastEthernet0/1
r1.owls#show ipv6 neighbors | inc
Nick Hilliard wrote:
On 27/03/2009 15:26, Leo Bicknell wrote:
AFAIK you have to have native peering with them to be part of the
pilot. At least, you did when we signed up. They may have relaxed
that since.
According to a Google IPv6 talk I attended yesterday, they don't intend
to relax
Everything is a tunnel...
Tube man. Everything is a tube... and Al Gore invented tubes.
MMC
Nick
--
Matthew Moyle-Croft Internode/Agile Peering and Core Networks
Athanasios Douitsis aduit...@gmail.com wrote:
Heard that they are somewhat picky about who they -enable. Our campus
has had native IPv6 everywhere and upwards all the way to Geant for many
years. We are thinking of applying in the hopes that it will boost IPv6
usage. Did you have any
Yes I do.
I can use it but sometimes got trouble with teredo.
Retry half an hour later works :)
ipv6.google.com looks better to me than the IPv4 version does.
More comfort. It is worth the trouble with teredo.
Peter
Robert D. Scott wrote:
http://www.google.com/intl/en/ipv6/
yup... and it is nice, adwords don't work pretty well (or at least on the GeoIP
thingie), and i get less publicity to look at :-)
---
Nuno Vieira
nfsi telecom, lda.
nuno.vie...@nfsi.pt
Tel. (+351) 21 949 2300 - Fax (+351) 21 949 2301
http://www.nfsi.pt/
- Robert D. Scott rob...@ufl.edu
Google over IPv6?
This is *not the same thing* as ipv6.google.com.
Google over IPv6 is about accessing www.google.com via IPv6. For you to
be doing this, you must have IPv6 connectivity and your IPv6 network
must meet Google's fairly stringent requirements.
Regards, K
http://www.google.com/intl/en/ipv6/
http://www.networkworld.com/news/2009/032509-google-ipv6-easy.html
Any one making use of Google IPV6?
Robert D. Scott rob...@ufl.edu
Senior Network Engineer 352-273-0113 Phone
CNS - Network Services 352-392-2061 CNS Phone Tree
On 27/03/09 11:59 PM, Daniel Verlouw dan...@bit.nl wrote:
yes. We participate in the Google IPv6 trial program so our recursors
get records for www.google.com and so far it's been great, no
issues whatsoever.
Same.
We've been participating since January and haven't had any problems:
#
On Fri, 2009-03-27 at 09:34 -0400, Steven M. Bellovin wrote:
It's working for me, too, though I noticed that tcptraceroute (at least
the version I have) doesn't do well with ipv6.google.com.
seems to work fine from over here:
# tcptraceroute6 www.google.com 80
traceroute to www.google.com
On Fri, 27 Mar 2009 14:46:50 +0100
Daniel Verlouw dan...@bit.nl wrote:
On Fri, 2009-03-27 at 09:34 -0400, Steven M. Bellovin wrote:
It's working for me, too, though I noticed that tcptraceroute (at
least the version I have) doesn't do well with ipv6.google.com.
seems to work fine from
In a message written on Fri, Mar 27, 2009 at 08:18:50AM -0400, Robert D. Scott
wrote:
Any one making use of Google IPV6?
We are in the trial:
% traceroute6 -n www.google.com
traceroute6 to www.l.google.com (2001:4860:b002::68) from
2001:4f8:3:bb::5, 64 hops max, 12 byte packets
1
Daniel Verlouw wrote:
yes. We participate in the Google IPv6 trial program so our recursors
get records for www.google.com and so far it's been great, no
issues whatsoever.
Same experiences - it just works.
dan...@jun1 traceroute www.google.com
traceroute6 to www.l.google.com
Robert D. Scott wrote:
When I posted my original note, I was not really looking for end user
feedback, but rather is anyone peering V6 with them on either a public
fabric or private peer. Any idea if they have native V6 transit, or are
tunneling, and to where.
No tuneling I think. We have with
-0421 Cell
-Original Message-
From: Grzegorz Janoszka [mailto:grzeg...@janoszka.pl]
Sent: Friday, March 27, 2009 10:55 AM
To: Daniel Verlouw
Cc: nanog@nanog.org
Subject: Re: Google Over IPV6
Daniel Verlouw wrote:
yes. We participate in the Google IPv6 trial program so our recursors
get
When I posted my original note, I was not really looking for end user
feedback, but rather is anyone peering V6 with them on either a public
fabric or private peer. Any idea if they have native V6 transit, or are
tunneling, and to where.
They are peering over some IXPs and private peerings
In a message written on Fri, Mar 27, 2009 at 11:03:05AM -0400, Robert D. Scott
wrote:
When I posted my original note, I was not really looking for end user
feedback, but rather is anyone peering V6 with them on either a public
fabric or private peer. Any idea if they have native V6 transit, or
On Fri, Mar 27, 2009 at 2:59 PM, Daniel Verlouw dan...@bit.nl wrote:
On Fri, 2009-03-27 at 08:18 -0400, Robert D. Scott wrote:
Any one making use of Google IPV6?
yes. We participate in the Google IPv6 trial program so our recursors
get records for www.google.com and so far it's been
On 27/03/2009 15:26, Leo Bicknell wrote:
AFAIK you have to have native peering with them to be part of the
pilot. At least, you did when we signed up. They may have relaxed
that since.
According to a Google IPv6 talk I attended yesterday, they don't intend to
relax that rule. Tunneling
Steven M. Bellovin wrote:
On Fri, 27 Mar 2009 14:46:50 +0100
Daniel Verlouw dan...@bit.nl wrote:
On Fri, 2009-03-27 at 09:34 -0400, Steven M. Bellovin wrote:
It's working for me, too, though I noticed that tcptraceroute (at
least the version I have) doesn't do well with ipv6.google.com.
Robert D. Scott wrote:
http://www.google.com/intl/en/ipv6/
http://www.networkworld.com/news/2009/032509-google-ipv6-easy.html
It's relatively easy to make _your own_ apps (i.e. ones you have the
source for) support IPv6.
Most companies, though, are completely reliant on their vendors,
sure you are using Google over IPv6?
This is *not the same thing* as ipv6.google.com.
Google over IPv6 is about accessing www.google.com via IPv6. For you to
be doing this, you must have IPv6 connectivity and your IPv6 network
must meet Google's fairly stringent requirements.
Regards, K
the IPv4 version does.
More comfort. It is worth the trouble with teredo.
Um, are you sure you are using Google over IPv6?
This is *not the same thing* as ipv6.google.com.
Google over IPv6 is about accessing www.google.com via IPv6. For
you to be doing this, you must have IPv6
version does.
More comfort. It is worth the trouble with teredo.
Um, are you sure you are using Google over IPv6?
This is *not the same thing* as ipv6.google.com.
Google over IPv6 is about accessing www.google.com via IPv6. For you to
be doing this, you must have IPv6 connectivity
* Robert D. Scott:
When I posted my original note, I was not really looking for end
user feedback, but rather is anyone peering V6 with them on either a
public fabric or private peer. Any idea if they have native V6
transit, or are tunneling, and to where.
Google seems to aim at Tier 1
On 27/03/2009, at 11:20 AM, Florian Weimer wrote:
Google seems to aim at Tier 1 status for IPv6. No transit, no
tunneling.
That seems to be the case, yep. It's an interesting plan.
On 27/03/2009, at 8:03 AM, Robert D. Scott wrote:
Their press would indicate that more than www is IPV6.
native V6
transit, or are tunneling, and to where.
Google seems to aim at Tier 1 status for IPv6. No transit, no
tunneling.
From their web page at http://www.google.com/intl/en/ipv6/:
To qualify for Google over IPv6, your network must have good IPv6
connectivity to Google. Multiple direct
28 matches
Mail list logo
