From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Random ping jumps
Date: Wed, 07 Jan 2004 23:25:00 +0000 [thread overview]
Message-ID: <00c401c3d575$78fa37e0$030aa8c0@t> (raw)
In-Reply-To: <3FFC7969.1040103@h2o.pieva.net>
I think it is your privider fault, Isnt your provider litnet? and you
connected with some wlan card
to debug it trace the patch (with traceroute or tracert) and try to ping the
most near routers, this way you will easy find the problem
> Hello,
>
> I've got this problem. There is an linux server with 2.4.24 kernel
> and pinging from him to internet (or from lan) ping randomly jumps up:
>
> 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq87 ttlY
time0.0 ms
> 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq88 ttlY
time2.6 ms
> 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq89 ttlY
time4.9 ms
> 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq90 ttlY
time\x198 ms
> 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq91 ttlY
time@7 ms
> 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq92 ttlY
time@7 ms
> 64 bytes from fortas.ktu.lt (193.219.160.131): icmp_seq93 ttlY
timeC0 ms
_______________________________________________
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-07 23:25 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 [this message]
2004-01-08 15:28 ` Artūras Šlajus
2004-01-08 18:15 ` R. Steve McKown
2004-01-08 20:01 ` Artūras Šlajus
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='00c401c3d575$78fa37e0$030aa8c0@t' \
--to=roy@xxx.lt \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.