From: Alex Bennee <kernel-hacker@bennee.com>
To: "Maciej Sołtysiak" <solt@dns.toxicfilms.tv>
Cc: Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Networking gets extremely laggy after a random amount of time.
Date: Wed, 26 Nov 2003 12:10:05 +0000 [thread overview]
Message-ID: <1069848605.5514.6.camel@cambridge.braddahead.com> (raw)
In-Reply-To: <001c01c3b40c$3e7666a0$0e25fe0a@pysiak>
On Wed, 2003-11-26 at 10:58, Maciej Sołtysiak wrote:
<snip>
> Networking gets extremely laggy after a random amount of time.
> Sometimes it is 5 minutes, sometimes 30hours, sometimes 5 days.
>
> By laggy, I mean that each connection that is established from or to
> the linux box (even on the same LAN) is very slow and jitters.
<snip>
> It propably is NIC related, but I do not know how to investigate
> this. I have two 3com 3c905c-tx NICs. One of them is connected
> to the LAN, and the other is connected to a hub and is sometimes
> used to listen in promiscous mode to investigate traffic.
>
> I would appreciate any pointers on where to look for problems.
Whenever I've come across problems with multiple NIC systems the first
thing I check is the routing is what I expect. Use "route -n" and check
that your WAN traffic really does go straight to the WAN and your LAN
traffic is as you expect.
Is your local LAN connections laggy as well? If not it could be your
problems are at the WAN end (BB connection?).
--
Alex, homepage: http://www.bennee.com/~alex/
Lazlo's Chinese Relativity Axiom:
No matter how great your triumphs or how tragic your defeats --
approximately one billion Chinese couldn't care less.
prev parent reply other threads:[~2003-11-26 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 10:58 Maciej Sołtysiak
2003-11-26 12:10 ` Alex Bennee [this message]
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=1069848605.5514.6.camel@cambridge.braddahead.com \
--to=kernel-hacker@bennee.com \
--cc=linux-kernel@vger.kernel.org \
--cc=solt@dns.toxicfilms.tv \
/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
all inboxes | Powered by JetHome®