[ milosbeo @ 11.06.2010. 08:10 ] @
Jel to smanjen ping do google.com 209.85.135.106
Izgleda da je nesto radjeno kod Telekoma.
Pozz

Code:


C:\Users\Milos>ping www.google.com

Pinging www.l.google.com [209.85.135.106] with 32 bytes of data:
Reply from 209.85.135.106: bytes=32 time=21ms TTL=56
Reply from 209.85.135.106: bytes=32 time=21ms TTL=56
Reply from 209.85.135.106: bytes=32 time=21ms TTL=56
Reply from 209.85.135.106: bytes=32 time=21ms TTL=56

Ping statistics for 209.85.135.106:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 21ms, Average = 21ms

[ djricky @ 14.06.2010. 08:59 ] @
ricky@master:~$ ping google.com
PING google.com (74.125.87.99) 56(84) bytes of data.
64 bytes from hb-in-f99.1e100.net (74.125.87.99): icmp_seq=1 ttl=56 time=9.82 ms
64 bytes from hb-in-f99.1e100.net (74.125.87.99): icmp_seq=2 ttl=56 time=9.84 ms
64 bytes from hb-in-f99.1e100.net (74.125.87.99): icmp_seq=3 ttl=56 time=9.45 ms
64 bytes from hb-in-f99.1e100.net (74.125.87.99): icmp_seq=4 ttl=56 time=9.49 ms

--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 9.451/9.655/9.842/0.193 ms


pusten direktan peering do Google-a, u Madjarskoj
[ optix @ 21.11.2010. 21:20 ] @
Evo, za sve koji vole da pinguju Google, sad je malo blize ;-)


[root@**** ~]# tracert 178.253.195.2
traceroute to 178.253.195.2 (178.253.195.2), 30 hops max, 40 byte packets
1 77.105.0.65 (77.105.0.65) 0.663 ms 0.644 ms 0.700 ms
2 cache.google.com (178.253.195.2) 0.612 ms 0.613 ms 0.610 ms
[root@**** ~]#


http://178.253.195.2

Have fun
[ djricky @ 22.11.2010. 08:19 ] @
daj bre pusti to kroz peering, bzvz da se gledamo kroz telekom


root@master:[~/POSAO_GLAVNI]: traceroute 178.253.195.2
traceroute to 178.253.195.2 (178.253.195.2), 30 hops max, 38 byte packets
1 vlan5.verat.net (217.26.xx.xxx) 0.396 ms 0.286 ms 0.202 ms
2 clint.noc.verat.net (62.108.96.77) 0.395 ms 0.552 ms 0.471 ms
3 195.178.34.125 (195.178.34.125) 0.996 ms 0.790 ms 0.870 ms
4 212.200.17.62 (212.200.17.62) 1.322 ms 0.958 ms 1.007 ms
5 212.200.232.93 (212.200.232.93) 0.968 ms 0.843 ms 0.797 ms
6 212.200.227.226 (212.200.227.226) 0.702 ms 0.985 ms 0.825 ms
7 SEZAMPRO-NET.telekom.yu (195.178.34.6) 0.792 ms 0.832 ms 0.821 ms
8 * * *

[ optix @ 22.11.2010. 09:07 ] @
Ne znaci ti nista previse jos uvek da to ide kroz peer-ing, posto se google cache masinama za sad oglasva samo deo orion opsega (za koje serviraju saobracaj direktno sa google/youtube-a).
Bice verovatno uskoro i jedno i drugo