From: "Artūras Šlajus" <x11@h2o.pieva.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Random ping jumps
Date: Thu, 08 Jan 2004 20:01:28 +0000 [thread overview]
Message-ID: <3FFDB718.7080303@h2o.pieva.net> (raw)
In-Reply-To: <3FFC7969.1040103@h2o.pieva.net>
R. Steve McKown wrote:
> Can you provide some more detail on your network configuration? I'm unclear
> if the linux server is your internet router or just another client computer
> on your local LAN
It's network router.
> , where the test pings to "the internet" are going (i.e.
> nexthop router, etc.), and if/where CIPE tunnels are involved in the
> equation. Perhaps a small network map would be helpful.
No CIPE (whatever is that ;-). Nexthop? You mean gateway?
eth0:1 Link encap:Ethernet HWaddr 00:50:22:B1:67:6D
inet addr:81.7.84.36 Bcast:81.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
Interrupt:10 Base address:0xd000
gateway: 81.7.84.1
Map is at http://h2o.pieva.net/net.png
> I'm also unclear about the pings that you've tried. After you've shown the
> network map, perhaps you can identify the two machines (and interfaces)
> involved in each of the different ping tests you've performed.
The machine is totaly random.
x11@rasnet:~$ traceroute fortas.ktu.lt
traceroute to fortas.ktu.lt (193.219.160.131), 30 hops max, 38 byte packets
1 adsl-213-190-40-129.takas.lt (213.190.40.129) 26.269 ms 23.333 ms 25.156 ms
2 fe22-acc0-tai.kns.telecom.lt (212.59.7.233) 63.079 ms 33.146 ms 26.117 ms
3 telecom-gw.is.lt (193.219.13.99) 35.978 ms 26.476 ms 103.138 ms
4 litnet-gw.is.lt (193.219.13.98) 22.715 ms 24.531 ms 209.984 ms
5 cat6506-p2-1.kttc.litnet.lt (193.219.62.125) 52.826 ms 98.040 ms 81.609 ms
6 ktu-lan.litnet.lt (193.219.61.252) 38.696 ms 182.582 ms 241.836 ms
7 fortas.ktu.lt (193.219.160.131) 215.523 ms 126.815 ms 29.217 ms
x11@rasnet:~$ traceroute cs.mes.lt
traceroute to cs.mes.lt (193.219.67.253), 30 hops max, 38 byte packets
1 adsl-213-190-40-129.takas.lt (213.190.40.129) 748.174 ms 66.331 ms 135.586 ms
2 fe22-acc0-tai.kns.telecom.lt (212.59.7.233) 21.645 ms 21.588 ms 24.597 ms
3 telecom-gw.is.lt (193.219.13.99) 30.584 ms 31.065 ms 29.612 ms
4 litnet-gw.is.lt (193.219.13.98) 24.602 ms 143.212 ms 143.096 ms
5 cat6506-p2-1.kttc.litnet.lt (193.219.62.125) 292.196 ms 163.870 ms 84.549 ms
6 ktu-lan.litnet.lt (193.219.61.252) 84.982 ms 54.801 ms 69.143 ms
7 diz.ktu.lt (193.219.67.253) 33.831 ms 29.877 ms 30.005 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq=5 ttlY time4.8 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq=6 ttlY time2.6 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq=7 ttlY time3.1 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq=8 ttlY time24 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq=9 ttlY timeƒ6 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x10 ttlY time…0 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x11 ttlY time21 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x12 ttlY time\x147 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x13 ttlY time\x115 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x14 ttlY time\x118 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x15 ttlY time\x107 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x16 ttlY time\x107 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x17 ttlY time'2 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x18 ttlY time12 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq\x19 ttlY time\x102 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq ttlY time\x107 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq! ttlY time\x114 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq" ttlY time‰.8 ms
64 bytes from diz.ktu.lt (193.219.67.253): icmp_seq# ttlY time‘.2 ms
x11@rasnet:~$ traceroute cs.bbd.lt
traceroute to cs.bbd.lt (193.219.184.7), 30 hops max, 38 byte packets
1 adsl-213-190-40-129.takas.lt (213.190.40.129) 23.803 ms 24.813 ms 56.163 ms
2 fe22-acc0-tai.kns.telecom.lt (212.59.7.233) 171.425 ms 21.174 ms 24.321 ms
3 telecom-gw.is.lt (193.219.13.99) 27.882 ms 30.782 ms 26.219 ms
4 litnet-gw.is.lt (193.219.13.98) 22.842 ms 23.025 ms 24.079 ms
5 cat6506-p2-1.kttc.litnet.lt (193.219.62.125) 24.201 ms 25.130 ms 27.256 ms
6 ktu-lan.litnet.lt (193.219.61.252) 26.811 ms 27.362 ms 27.785 ms
7 193.219.184.7 (193.219.184.7) 27.928 ms 29.185 ms 28.067 ms
x11@rasnet:~$ ping cs.bbd.lt
PING cs.bbd.lt (193.219.184.7) 56(84) bytes of data.
64 bytes from 193.219.184.7: icmp_seq=1 ttl\x123 time\x133 ms
64 bytes from 193.219.184.7: icmp_seq=2 ttl\x123 time\x122 ms
64 bytes from 193.219.184.7: icmp_seq=3 ttl\x123 time\x118 ms
64 bytes from 193.219.184.7: icmp_seq=4 ttl\x123 time\x109 ms
64 bytes from 193.219.184.7: icmp_seq=5 ttl\x123 timer5 ms
64 bytes from 193.219.184.7: icmp_seq=6 ttl\x123 timef8 ms
64 bytes from 193.219.184.7: icmp_seq=7 ttl\x123 time\x120 ms
64 bytes from 193.219.184.7: icmp_seq=8 ttl\x123 time\x102 ms
64 bytes from 193.219.184.7: icmp_seq=9 ttl\x123 time‘.5 ms
64 bytes from 193.219.184.7: icmp_seq\x10 ttl\x123 time‘.7 ms
> I had a similar problem recently. Interestingly, it
> turned out to be bad hardware.
Another person told me that bad hw could be reason. But it works for
LAN perfectly.
> Moved the boot media to an identically
> configured machine and the problem went away. Returned the boot media to the
> original machine and the problem returned.
Sad, but i can't do that :(
My /etc/network/interfaces:
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
autho eth0:1
iface eth0:1 inet static
address 81.7.84.36
netmask 255.0.0.0
gateway 81.7.84.1
mtu 1492
I hadn't set mtu before. After setting it ping times decreased. (afterall it's dsl).
Also, what exatcly net/ipv4/tcp_low_latency = 1 in sysctl do?
--
Sincerely, Artūras Šlajus
ICQ: 157929934
Jabber: arturaz@akl.lt
Oh, and please'o'please use UTF-8! :-)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-01-08 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 21:26 [LARTC] Random ping jumps Artūras Šlajus
2004-01-07 23:25 ` Roy
2004-01-08 15:28 ` Artūras Šlajus
2004-01-08 18:15 ` R. Steve McKown
2004-01-08 20:01 ` Artūras Šlajus [this message]
2004-01-09 2:43 ` R. Steve McKown
2004-01-09 7:07 ` Artūras Šlajus
2004-01-09 7:23 ` Artūras Šlajus
2004-01-17 4:59 ` vica_s
2004-01-17 9:58 ` Jurrie Overgoor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FFDB718.7080303@h2o.pieva.net \
--to=x11@h2o.pieva.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox