public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anuradha Ratnaweera <anuradha@gnu.org>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Anuradha Ratnaweera <anuradha@gnu.org>,
	"Jeffrey H. Ingber" <jhingber@ix.netcom.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Other computers HIGHLY degrading network performance (DoS?)
Date: Sat, 27 Oct 2001 09:37:29 +0600	[thread overview]
Message-ID: <20011027093729.B2651@bee.lk> (raw)
In-Reply-To: <20011026101313.A18310@bee.lk> <Pine.LNX.4.21.0110261555450.8307-100000@tux.rsn.bth.se>
In-Reply-To: <Pine.LNX.4.21.0110261555450.8307-100000@tux.rsn.bth.se>; from gandalf@wlug.westbo.se on Fri, Oct 26, 2001 at 04:01:29PM +0200

On Fri, Oct 26, 2001 at 04:01:29PM +0200, Martin Josefsson wrote:
> On Fri, 26 Oct 2001, Anuradha Ratnaweera wrote:
> 
> > > One machine begins an intensive downloading job.  How can this degrade the
> > > network performance even for ICMP packets between another machine and the
> > > router?  Notice that this can't be collitions because the download goes at
> > > 64kbps and the local network is 100 Mbps.  Something funny is going on to
> > > stop other people's packets.
> > 
> > Just found out that this is _not_ a problem of the "download accelerator", but
> > something to do with queuing algorithm of the router.  Even a normal wget
> > process or a big mail has a big impart on the network.  Hopefully an iptables
> > firewall would solve the problem.
> 
> I'd advice you to seriously look over your network, are you 100% sure you
> don't have a duplex-issue anywhere?

I will double check.  I wonder if this is the cause, because the network is 100
Mbps, but the router is switching only at 64kbps.

> I've been running linuxrouters for quite a while and right now I have a few
> linuxrouters routing 100Mbit/s internetconnections. We have never had any
> problems like the one you describe so my first guess would be that you have a
> duplexproblem, probably between the linuxrouter and the switch it's connected
> to on the inside, that's usually where it's located.

We have a hub, and not a switch.  Can this be the reason?  BTW, how come that a
duplex issue can result in such huge degradations?

> I seriously doubt that this a problem with the networking in linux.

Not in linux, may be the way they have _used_ linux on the router ;-)

Anuradha

-- 

Debian GNU/Linux (kernel 2.4.13)

[FORTRAN] will persist for some time -- probably for at least the next decade.
		-- T. Cheatham


  reply	other threads:[~2001-10-27  3:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-26  2:43 Other computers HIGHLY degrading network performance (DoS?) Anuradha Ratnaweera
2001-10-26  2:55 ` Jeffrey H. Ingber
2001-10-26  3:05   ` Anuradha Ratnaweera
2001-10-26  4:13     ` Anuradha Ratnaweera
2001-10-26 10:56       ` Paul P Komkoff Jr
2001-10-27  3:28         ` Anuradha Ratnaweera
2001-10-27 10:06           ` Paul P Komkoff Jr
2001-10-28  6:11             ` Anuradha Ratnaweera
2001-10-26 14:01       ` Martin Josefsson
2001-10-27  3:37         ` Anuradha Ratnaweera [this message]
2001-10-27  8:40           ` Martin Josefsson
2001-10-26 12:53 ` Alan Cox
2001-10-27  3:06   ` Anuradha Ratnaweera

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=20011027093729.B2651@bee.lk \
    --to=anuradha@gnu.org \
    --cc=gandalf@wlug.westbo.se \
    --cc=jhingber@ix.netcom.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox