f



traceroute question, where do the tim differences come from?

I have setup a system with network like this:

luuk@ubuntu1:~$ route
Kernel IP routing table
Destination  Gateway         Genmask     Flags Metric Ref    Use Iface
default      192.168.178.2   0.0.0.0     UG    0      0        0 eth0
10.0.1.0     *               255.255.255.0 U     0      0        0 eth1
192.168.178.0 *              255.255.255.0 U     0      0        0 eth0

And created a script like this:

luuk@ubuntu1:~$ cat doit.sh
#!/bin/bash

i="0"

while [ $i -lt 4 ]
do
         traceroute 192.168.178.250
         sleep $1
         i=$[$i+1]
done


Why dooes traceroute behave bad with shor pauses?:
luuk@ubuntu1:~$ ./doit.sh 4
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.937 ms  1.316 ms  1.695 ms
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.917 ms  1.329 ms  1.741 ms
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.980 ms  1.406 ms  1.820 ms
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.892 ms  1.324 ms  1.731 ms
luuk@ubuntu1:~$ ./doit.sh 1
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.932 ms  1.355 ms  1.773 ms
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.608 ms * *
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.879 ms  1.301 ms  1.712 ms
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.804 ms * *
luuk@ubuntu1:~$

and it gets awfull with 0:
luuk@ubuntu1:~$ ./doit.sh 0
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  192.168.178.250 (192.168.178.250)  0.658 ms  1.073 ms  1.481 ms
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  * * *
  2  * * *
  3  * * *
  4  * * *
  5  * * *
  6  * 192.168.178.250 (192.168.178.250)  0.735 ms  1.145 ms
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  * * *
  2  * * *
  3  * * *
  4  * * *
  5  * * *
  6  * 192.168.178.250 (192.168.178.250)  0.766 ms  1.184 ms
traceroute to 192.168.178.250 (192.168.178.250), 30 hops max, 60 byte 
packets
  1  * * *
  2  * * *
  3  * * *
  4  * * *
  5  * * *
  6  * 192.168.178.250 (192.168.178.250)  1.301 ms  1.704 ms
luuk@ubuntu1:~$

luuk@ubuntu1:~$ uname -a
Linux ubuntu1 4.2.0-41-generic #48~14.04.1-Ubuntu SMP Fri Jun 24 
17:09:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
luuk@ubuntu1:~$

0
Luuk
7/8/2016 1:01:01 AM
comp.os.linux.networking 15677 articles. 0 followers. Post Follow

4 Replies
240 Views

Similar Articles

[PageSpeed] 35

On 08-07-16 19:44, Luuk wrote:
> Why dooes traceroute behave bad with short pauses?:

disabling eth1 did not do the trick...

0
Luuk
7/8/2016 5:47:16 PM
Luuk <luuk@invalid.lan> wrote:
> Why dooes traceroute behave bad with shor pauses?:

Perhaps 192.168.178.250 is rate-limiting its ICMP responses to the
packets being sent by traceroute.  You might consider checking the
statistics on 192.168.178.25 (perhaps it keeps a stat, perhaps a
logging entry), and taking packet traces on it, and your sending
system.

rick jones
-- 
oxymoron n, commuter in a gas-guzzling luxury SUV with an American flag
these opinions are mine, all mine; HPE might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hpe.com but NOT BOTH...
0
Rick
7/8/2016 6:10:42 PM
On Fri, 8 Jul 2016 19:44:38 +0200, Luuk wrote:
> I have setup a system with network like this:
>
> luuk@ubuntu1:~$ route
> Kernel IP routing table
> Destination  Gateway         Genmask     Flags Metric Ref    Use Iface
> default      192.168.178.2   0.0.0.0     UG    0      0        0 eth0
> 10.0.1.0     *               255.255.255.0 U     0      0        0 eth1
> 192.168.178.0 *              255.255.255.0 U     0      0        0 eth0
>
> And created a script like this:
>
> luuk@ubuntu1:~$ cat doit.sh
> #!/bin/bash
>
> i="0"
>
> while [ $i -lt 4 ]
> do
>          traceroute 192.168.178.250
>          sleep $1
>          i=$[$i+1]
> done
>
>
> Why dooes traceroute behave bad with shor pauses?:

Because that node has been setup to not return your inquiry.

It may help somewhat if you add the -In switch to traceroute.
     traceroute -In 192.168.178.250

0
Bit
7/8/2016 6:20:19 PM
On 08-07-16 20:20, Bit Twister wrote:
> On Fri, 8 Jul 2016 19:44:38 +0200, Luuk wrote:
>> I have setup a system with network like this:
>>
>> luuk@ubuntu1:~$ route
>> Kernel IP routing table
>> Destination  Gateway         Genmask     Flags Metric Ref    Use Iface
>> default      192.168.178.2   0.0.0.0     UG    0      0        0 eth0
>> 10.0.1.0     *               255.255.255.0 U     0      0        0 eth1
>> 192.168.178.0 *              255.255.255.0 U     0      0        0 eth0
>>
>> And created a script like this:
>>
>> luuk@ubuntu1:~$ cat doit.sh
>> #!/bin/bash
>>
>> i="0"
>>
>> while [ $i -lt 4 ]
>> do
>>          traceroute 192.168.178.250
>>          sleep $1
>>          i=$[$i+1]
>> done
>>
>>
>> Why dooes traceroute behave bad with shor pauses?:
>
> Because that node has been setup to not return your inquiry.
>
> It may help somewhat if you add the -In switch to traceroute.
>      traceroute -In 192.168.178.250
>

This works (the '-I' option)
Still have to do some reading about the cause of this ;)

Thanks
0
Luuk
7/8/2016 6:58:47 PM
Reply: