[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-talk] traceroute from Rossia, ROSTELECOM
2015-11-03 21:36 GMT-05:00 Vladimir Teplouhov <vladimir.teplouhov@xxxxxxxxx>:
> ÐÑÐÑÑÐÑÐÐÐÐ ÐÐÑÑÑÑÑÐ Ð google.com [212.20.34.187]
> q1. GOOGLE ÐÐÑÐÐÑÐÐ Ð ÐÐÑÑÐÑ Ð ÑÑÐÐ ÑÐÐÐÐÐÐÐ ÐÐÑÑÐÐÐÐÐÐÐ? ;)
Google has datacenters all over the world and uses GeoDNS
and other things to direct users there. You're also dealing with
peering / DMZ's where naming is hardly conclusive. It's normal.
> 2 3 ms 3 ms 4 ms bar-bbar3.ncc.sibirtelecom.ru [213.228.116.69]
> 3 5 ms 6 ms 3 ms
> ge-11-0-1.abn-bbar2.ncc.sibirtelecom.ru [213.228.107.14]
> 4 8 ms 7 ms 8 ms 188.128.106.45
> 5 10 ms 10 ms 7 ms google.com [212.20.34.162]
> q2. ÐÐÑÑÐÐÐÐÐÐÑ ÑÐÐ ÑÐÐÐÐÑÑ ÐÑÐÐÑÑÐÑÑ ÑÐÐÑÐÑÑÑ ÑÐÐÑÐ?..
This happens, it's normal routing stuff, no time to explain it.
Use something like mtr and the averages over
time can make a bit more sense.
Too bad tor still only supports TCP, otherwise you could
trace from anywhere in the world.
And exits running VPN terminators for tor users was
suggested a few times but who knows if operators
are running any.
--
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk