Hi!
Using LFT:
root@debian:~# lft 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 172.28.1.1 (172.28.1.1) 0.798 ms 0.711 ms
2 10.16.0.2 (10.16.0.2) 0.414 ms 0.331 ms
3 41.200.16.1 (41.200.16.1) 11.400 ms 11.474 ms
4 172.17.2.25 (172.17.2.25) 10.184 ms 11.322 m
t: Thursday, December 08, 2011 11:40 PM
Subject: Re: Traceroute explanation
Hai!
Check with lft or mtr ...
Thanks,
Raymond Dijkxhoorn, Prolocation
Op 7 dec. 2011 om 20:56 heeft "Meftah Tayeb" het
volgende geschreven:
please tel me how to ?
i don't know astraceroute:)
-
t;
> To: "Meftah Tayeb"
> Cc: "Fred Baker" ;
> Sent: Thursday, December 08, 2011 11:33 PM
> Subject: Re: Traceroute explanation
>
>
> On Dec 7, 2011, at 2:51 08PM, Meftah Tayeb wrote:
>
>> big thank for that
>> but, i am testing that for o
aceroute or manually translate those addresses into AS#s?
> That is, might level3 and tinet be using multiple AS#s, in which case this
> isn't unreasonable?
>
>
>
>
>
>>
>>
>> - Original Message - From: "Fred Baker"
>> T
Another explanation could be load balancing. As Fred mentioned, traceroute
sends out different packets for different hops on the path and since these
packets have different headers, load balancers on the path may hash packets
with different TTL values on to different paths.
Check out http://www
please tel me how to ?
i don't know astraceroute:)
- Original Message -
From: "Steven Bellovin"
To: "Meftah Tayeb"
Cc: "Fred Baker" ;
Sent: Thursday, December 08, 2011 11:33 PM
Subject: Re: Traceroute explanation
On Dec 7, 2011, at 2:51 08PM,
nreasonable?
>
>
> - Original Message - From: "Fred Baker"
> To: "Meftah Tayeb"
> Cc:
> Sent: Thursday, December 08, 2011 11:23 PM
> Subject: Re: Traceroute explanation
>
>
> This is just a guess, but I'll bet the route changed while y
big thank for that
but, i am testing that for one day :)
- Original Message -
From: "Fred Baker"
To: "Meftah Tayeb"
Cc:
Sent: Thursday, December 08, 2011 11:23 PM
Subject: Re: Traceroute explanation
This is just a guess, but I'll bet the route changed whi
This is just a guess, but I'll bet the route changed while you were measuring
it.
Traceroute sends a request, awaits a response, sends a request, ... Suppose
that the route was
172.28.0.1 -> 10.16.0.2
-> 41.200.16.1
-> 172.17.2.25
-> 213.140.58.10
->
er 08, 2011 10:58 PM
Subject: Re: Traceroute explanation
Hi,
nothing surprises me from Tinet any more... at one time all my traffic
from Europe was routed through some Hong Kong router of theirs...
but, enough jokes...
this could be the path the packets are traversing through, nothing
wrong
Hi,
nothing surprises me from Tinet any more... at one time all my traffic
from Europe was routed through some Hong Kong router of theirs...
but, enough jokes...
this could be the path the packets are traversing through, nothing
wrong with it, as long as everything is working fine... ie. packet
11 matches
Mail list logo
