192.88.99.1 (6to4 anycast) in Russia

[Frank Bulk]

There's a typo in your traceroute -- it should be 192.88.99.1.

Frank

-----Original Message-----
From: ipv6-ops-bounces+frnkblk=iname.com at lists.cluenet.de [mailto:ipv6-ops-bounces+frnkblk=iname.com at lists.cluenet.de] On Behalf Of Ivan Shmakov
Sent: Tuesday, November 08, 2011 4:50 AM
To: ipv6-ops at lists.cluenet.de
Subject: Re: 192.88.99.1 (6to4 anycast) in Russia

>>>>> Ignatios Souvatzis <ignatios at cs.uni-bonn.de> writes:
>>>>> On Fri, Nov 04, 2011 at 09:38:42PM +0700, Ivan Shmakov wrote:
>>>>> Ignatios Souvatzis <ignatios at cs.uni-bonn.de> writes:
>>>>> On Fri, Oct 21, 2011 at 03:20:46PM +0700, Ivan Shmakov wrote:

 >>>> I wonder, if anyone in Russia have successfully set up 6to4 using
 >>>> such an address, and what the AS it was in?

 >>> from a machine in AS2118 in St.Petersburg there is a path to
 >>> 192.88.99.1 (in its incarnation in AS6881). I'll hear later this
 >>> weekend whether this path actually works for 6to4.

 >> Any news on this?

 > Finally, yes. I was told a few minutes ago: "i'm told that yes, that
 > address should work".

	ACK, thanks.

	Unfortunately, it still doesn't work for the network in
	question.  Although # traceroute6 -I reveals a route ending
	(preasumably) at one of the CALREN routers posing as
	199.88.99.1:

# traceroute -n -I 199.88.99.1 
…
13  137.164.34.95  230.044 ms  230.034 ms  230.067 ms
14  137.164.13.122  229.565 ms  229.742 ms  231.010 ms
15  199.88.99.1  234.714 ms  234.300 ms  232.997 ms
16  * * *
…
# 

	the route itself (default via ::192.88.99.1 dev 6to4) doesn't
	seem to work.

-- 
FSF associate member #7257