Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #3802 > unrolled thread

traceroute question, where do the tim differences come from?

Started byLuuk <luuk@invalid.lan>
First post2016-07-08 19:44 +0200
Last post2016-07-08 20:58 +0200
Articles 5 — 3 participants

Back to article view | Back to comp.os.linux.networking

Contents

  traceroute question, where do the tim differences come from? Luuk <luuk@invalid.lan> - 2016-07-08 19:44 +0200
    Re: traceroute question, where do the tim differences come from? Luuk <luuk@invalid.lan> - 2016-07-08 19:47 +0200
    Re: traceroute question, where do the tim differences come from? Rick Jones <rick.jones2@hpe.com> - 2016-07-08 18:10 +0000
    Re: traceroute question, where do the tim differences come from? Bit Twister <BitTwister@mouse-potato.com> - 2016-07-08 18:20 +0000
      Re: traceroute question, where do the tim differences come from? Luuk <luuk@invalid.lan> - 2016-07-08 20:58 +0200

#3802 — traceroute question, where do the tim differences come from?

FromLuuk <luuk@invalid.lan>
Date2016-07-08 19:44 +0200
Subjecttraceroute question, where do the tim differences come from?
Message-ID<577fe667$0$5811$e4fe514c@news.xs4all.nl>
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:~$

[toc] | [next] | [standalone]

#3803

FromLuuk <luuk@invalid.lan>
Date2016-07-08 19:47 +0200
Message-ID<577fe705$0$5811$e4fe514c@news.xs4all.nl>
In reply to#3802
On 08-07-16 19:44, Luuk wrote:
> Why dooes traceroute behave bad with short pauses?:

disabling eth1 did not do the trick...

[toc] | [prev] | [next] | [standalone]

#3804

FromRick Jones <rick.jones2@hpe.com>
Date2016-07-08 18:10 +0000
Message-ID<nloqb2$21o$1@news.hpeswlab.net>
In reply to#3802
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...

[toc] | [prev] | [next] | [standalone]

#3805

FromBit Twister <BitTwister@mouse-potato.com>
Date2016-07-08 18:20 +0000
Message-ID<slrnnnvrn3.92d.BitTwister@wb.home.test>
In reply to#3802
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

[toc] | [prev] | [next] | [standalone]

#3806

FromLuuk <luuk@invalid.lan>
Date2016-07-08 20:58 +0200
Message-ID<577ff7c8$0$5845$e4fe514c@news.xs4all.nl>
In reply to#3805
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

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.networking

csiph-web