lkml.org 
[lkml]   [1997]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectBUG: SYN protection causes stuck socket??

Hi,

I think I may have narrowed down the cause of sockets stuck in
2.0.30/31/probably 32 too. Basically, very rarely, sockets appear stuck in
state CLOSE.

Currently, we have one in such a state; the timer endlessly cycles from
10s down to 0s. The port number in question appears in the kernel logs
like this:

ferret kernel: Warning: possible SYN flood from x.x.x.x on
163.1.138.204:7186. Sending cookies.
ferret kernel: validated proble(x.x.x.x:20, 163.1.138.204:7186, -<big
number>)

From netstat after this event:

tcp 0 0 ferret.lmh.ox.ac.uk:7186 *.* CLOSE on (8.12/0)


I'm guessing that narrowing the problem down to SYN protection code thus,
will enable the bug to be fixed easily? Any more info wanted, just ask...

Cheers
Chris


\
 
 \ /
  Last update: 2005-03-22 13:40    [W:0.029 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site