From: "Artūras Šlajus" <x11@h2o.pieva.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Random ping jumps
Date: Thu, 08 Jan 2004 15:28:01 +0000 [thread overview]
Message-ID: <3FFD7701.6000905@h2o.pieva.net> (raw)
In-Reply-To: <3FFC7969.1040103@h2o.pieva.net>
Roy wrote:
> I think it is your privider fault, Isnt your provider litnet? and you
> connected with some wlan card
no. my provider is Lithuania telecom. And i'm on DSL 320/128.
> 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
i'll try using mrt.
_______________________________________________
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 15:28 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 [this message]
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=3FFD7701.6000905@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