| To: | Nivedita Singhvi <niv@xxxxxxxxxx> |
|---|---|
| Subject: | Re: High number of concurrent connections causes 2.6.4 to go berserk |
| From: | Christopher Chan <cchan@xxxxxxxxxxxx> |
| Date: | Fri, 02 Apr 2004 12:00:35 +0800 |
| Cc: | netdev@xxxxxxxxxxx, Yusuf Goolamabbas <yusufg@xxxxxxxxxxxx> |
| In-reply-to: | <406CDDF5.4070500@xxxxxxxxxx> |
| References: | <406CBA60.50103@xxxxxxxxxxxx> <406CDDF5.4070500@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 |
Nivedita Singhvi wrote: Christopher Chan wrote:When tcp_max_syn_backlog is set to 4096 and route.max_size = 131072 route.gc_thresh = 65536the 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 = 65536Did 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: High number of concurrent connections causes 2.6.4 to go berserk, Nivedita Singhvi |
|---|---|
| Next by Date: | Re: High number of concurrent connections causes 2.6.4 to go berserk, Christopher Chan |
| Previous by Thread: | Re: High number of concurrent connections causes 2.6.4 to go berserk, Nivedita Singhvi |
| Next by Thread: | Re: High number of concurrent connections causes 2.6.4 to go berserk, Christopher Chan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |