On 2011/06/06 18:38, r...@u13.net wrote:
On Mon, 06 Jun 2011 08:19:37 +0300, Hank Nussbacher wrote:
Will Google have inverse working by June 8th?
[hank@noc ~]$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2a00:1450:8001::68) from
2001:bf8:0:3:202:b3ff:feaf:f3fc, 30 hops max, 16
On Mon, 06 Jun 2011 08:19:37 +0300, Hank Nussbacher wrote:
Will Google have inverse working by June 8th?
[hank@noc ~]$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2a00:1450:8001::68) from
2001:bf8:0:3:202:b3ff:feaf:f3fc, 30 hops max, 16 byte packets
1 2001:bf8:0:3::1 (2001:bf8:
In a message written on Mon, Jun 06, 2011 at 11:08:28AM -0400,
valdis.kletni...@vt.edu wrote:
> On Mon, 06 Jun 2011 07:49:41 PDT, Leo Bicknell said:
> > I have not had good luck with that feature.
> >
> > Here's a FreeBSD traceroute, using the same host I referenced before:
> >
> > % traceroute
On Mon, 06 Jun 2011 07:49:41 PDT, Leo Bicknell said:
> I have not had good luck with that feature.
>
> Here's a FreeBSD traceroute, using the same host I referenced before:
>
> % traceroute -a efes.iucc.ac.il
s/-a/-A/ - FTFY.
pgpCnlQnuHxpp.pgp
Description: PGP signature
In a message written on Mon, Jun 06, 2011 at 04:38:26PM +0200, Bjørn Mork wrote:
> You can convince your traceroute to do that for you:
>
> -A --as-path-lookups Perform AS path lookups in routing registries
> and
> print results directly after the correspond
Leo Bicknell writes:
> Quick question, which network providers were involved in that trace?
> Have fun hitting up whois to find out!
You can convince your traceroute to do that for you:
-A --as-path-lookups Perform AS path lookups in routing registries and
In a message written on Mon, Jun 06, 2011 at 08:45:31AM -0400, Christopher
Morrow wrote:
> On Mon, Jun 6, 2011 at 1:19 AM, Hank Nussbacher wrote:
> > Will Google have inverse working by June 8th?
>
> poking the tiger some... 'why?'
It's the network equivilent of holding open the door for someon
On Mon, Jun 6, 2011 at 8:53 AM, Hank Nussbacher wrote:
> At 08:45 06/06/2011 -0400, Christopher Morrow wrote:
>>
>> On Mon, Jun 6, 2011 at 1:19 AM, Hank Nussbacher
>> wrote:
>> > Will Google have inverse working by June 8th?
>> >
>>
>> poking the tiger some... 'why?'
>
> Just curious.
it occurs
On Mon, Jun 6, 2011 at 9:12 AM, STARNES, CURTIS
wrote:
> (2001:4860:800a::6a
I think this is a case of some ips have this, some don't... I think
all are SUPPOSED to...
-chris
ms 113.447 ms
12 yx-in-x6a.1e100.net (2001:4860:800a::6a) 113.500 ms 113.493 ms 113.881 ms
Curtis
-Original Message-
From: Hank Nussbacher [mailto:h...@efes.iucc.ac.il]
Sent: Monday, June 06, 2011 7:53 AM
To: Christopher Morrow
Cc: nanog@nanog.org
Subject: Re: Google and IPv6 inverse
At 08:45 06/06/2011 -0400, Christopher Morrow wrote:
On Mon, Jun 6, 2011 at 1:19 AM, Hank Nussbacher wrote:
> Will Google have inverse working by June 8th?
>
poking the tiger some... 'why?'
Just curious.
-Hank
> [hank@noc ~]$ traceroute6 ipv6.google.com
> traceroute to ipv6.l.google.com (
On Mon, Jun 6, 2011 at 1:19 AM, Hank Nussbacher wrote:
> Will Google have inverse working by June 8th?
>
poking the tiger some... 'why?'
> [hank@noc ~]$ traceroute6 ipv6.google.com
> traceroute to ipv6.l.google.com (2a00:1450:8001::68) from
> 2001:bf8:0:3:202:b3ff:feaf:f3fc, 30 hops max, 16 byte
12 matches
Mail list logo