public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anuradha Ratnaweera <anuradha@gnu.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Anuradha Ratnaweera <anuradha@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: Other computers HIGHLY degrading network performance (DoS?)
Date: Sat, 27 Oct 2001 09:06:39 +0600	[thread overview]
Message-ID: <20011027090639.A2053@bee.lk> (raw)
In-Reply-To: <20011026084328.A14814@bee.lk> <E15x6U0-0008Hs-00@the-village.bc.nu>
In-Reply-To: <E15x6U0-0008Hs-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Oct 26, 2001 at 01:53:08PM +0100

On Fri, Oct 26, 2001 at 01:53:08PM +0100, Alan Cox wrote:
> 
> Turning off byte range support in the web server works suprisingly well for
> it.

But won't it affect retry features of other `good' software such as wget?  At
any rate, people are downloading from web/ftp sites on the Internet, which are
beyond our control, and apache hacks are anyway impossible.  However, I am
thinking of setting up a transparent proxy (squid/iptables) on the firewall and
let it handle the bandwidth limiting and the like.

> Another non hacking code approach would be to set up CBQ or other bandwidth
> limiters so that the users of download accelerator get no benefit.

I don't mind hacking approaches.  Otherwise, I won't be reading the LKML ;-)

> The advantage of the apache hacks is that you can make them actually suffer

That is a wonderful idea.  Trying to exploit features on the Internet should be
a punishable offence ;)

Regards,

Anuradha

-- 

Debian GNU/Linux (kernel 2.4.13)

Exhilaration is that feeling you get just after a great idea hits you,
and just before you realize what is wrong with it.


      reply	other threads:[~2001-10-27  3:07 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
2001-10-27  8:40           ` Martin Josefsson
2001-10-26 12:53 ` Alan Cox
2001-10-27  3:06   ` Anuradha Ratnaweera [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=20011027090639.A2053@bee.lk \
    --to=anuradha@gnu.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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