netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Chan <cchan@outblaze.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: netdev@oss.sgi.com, Yusuf Goolamabbas <yusufg@outblaze.com>
Subject: Re: High number of concurrent connections causes 2.6.4 to go berserk
Date: Fri, 02 Apr 2004 12:00:35 +0800	[thread overview]
Message-ID: <406CE563.5090105@outblaze.com> (raw)
In-Reply-To: <406CDDF5.4070500@us.ibm.com>

Nivedita Singhvi wrote:
> Christopher Chan wrote:
> 
>> When tcp_max_syn_backlog is set to 4096 and
>> route.max_size = 131072
>> route.gc_thresh = 65536
>>
>> the box goes berserk almost immediately after bootup due to a bounce 
>> flood hitting the box.
> 
> 
>> The below values seem to workaround whatever problem the kernel has.
>>
>> tcp_max_syn_backlog = 2048
>> route.max_size = 1048576
>> route.gc_thresh = 65536
> 
> 
> Did you try just one of the first two and see which
> one actually made a difference? I'm assuming the first,
> but that might not be the case..

Another box that has less traffic but sometimes gets ddosed by bounces 
has default settings

tcp_max_syn_backlog = 1024
route.max_size = 131072
route.gc_thresh = 8192

This box's 2.6.4 also went berserk during the ddos.

I'll try your suggestion and get back to you.

> 
> thanks,
> Nivedita
> 
> 
> 

  reply	other threads:[~2004-04-02  4:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02  0:57 High number of concurrent connections causes 2.6.4 to go berserk Christopher Chan
2004-04-02  3:28 ` Nivedita Singhvi
2004-04-02  4:00   ` Christopher Chan [this message]
2004-04-02 16:37   ` Christopher Chan

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=406CE563.5090105@outblaze.com \
    --to=cchan@outblaze.com \
    --cc=netdev@oss.sgi.com \
    --cc=niv@us.ibm.com \
    --cc=yusufg@outblaze.com \
    /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;
as well as URLs for NNTP newsgroup(s).