192.88.99.1 (6to4 anycast) in Russia

Ivan Shmakov oneingray at gmail.com
Wed Nov 9 09:07:55 CET 2011


>>>>> Frank Bulk <frnkblk at iname.com> writes:

[…]

 >> 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:

[…]

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

	Indeed, a silly mistake on my part.  Thanks!

# traceroute -n -I 192.88.99.1 
…
 4  87.245.233.134  24.630 ms  24.623 ms  24.614 ms
 5  192.88.99.1  25.834 ms  26.071 ms  26.063 ms
# 

	(I guess that this relay belongs to AS9002.)

	Moreover, there I've made a (different) mistake when I've tried
	to test 6to4 routing.  Now, it appears to work, too.

--- ipv6.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 124.641/124.803/124.911/0.311 ms

-- 
FSF associate member #7257
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20111109/8c0498aa/attachment.sig>


More information about the ipv6-ops mailing list