All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: Whacky 2.6 network behaviour
Date: Thu, 19 Aug 2004 12:03:40 +1000	[thread overview]
Message-ID: <20040819020339.GA808@zip.com.au> (raw)

I have an SSH session across a 100mb network from my desktop to my
laptop. It's mostly ok but when I scroll line-by-line on a message
with mutt it can fo really fast for a bit and then slows down to
almost a line per second and keeps going after I take my finger off
the enter key. 

If I pingflood the laptop from the desktop things improve drastically
and I only get a few freezes here and there. If I pingflood with 60000
byte packets things get a little better but then a severe loss of
pings occurs. Each time the pings are lost my SSH connection also
freezes.

If I ping a different host from my desktop (like my gateway) I get no
pingloss with 60000 byte packets (though this doesn't help with the
scrolling issues. :)

If I ping my desktop from my laptop with 60000 byte packets, the freezes
are totally gone and I get no pingloss. If I ping my gateway from my
laptop with 60000 byte packets I also get no pingloss and the freezes
are also gone.

My desktop is using kernel 2.6.7, my laptop 2.6.8.1 and the gw 2.4.27.
Cards in use are: desktop: 3com 3c59x; laptop: e100 (intels); gw:
 e100 (intels). CPUs are: desktop: P3 600; laptop: P3 700; gw: p3 500.

(Hmm. Spoke too soon. There is still SOME packet loss but it's more a
freak thing rather then a repeated occurance - I've only seen it once
for the last two cases and I've been flood pinging for the laptop for
the majority of this message).

I'll be more then happy to do any debugging/diag but I need to know
what is needed and, if need be, how to get it so if any help is requried
please shout and I'll get on it ASAP.

-- 
    Red herrings strewn hither and yon.

                 reply	other threads:[~2004-08-19  2:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040819020339.GA808@zip.com.au \
    --to=cat@zip.com.au \
    --cc=linux-kernel@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.