[Seaside] Seaside Ports getting tied up (was WAKom not
responding to requests)
Brian Brown
rbb at techgame.net
Mon Apr 7 10:16:16 CEST 2003
On Monday 07 April 2003 09:44 am, Derek Brans wrote:
> then again later when I try to access seaside again.
> netstat -an | grep 8002
> tcp 500 0 127.0.0.1:8002 127.0.0.1:2017 ESTABLISHED
> tcp 0 0 127.0.0.1:2017 127.0.0.1:8002 ESTABLISHED
> tcp 501 0 127.0.0.1:8002 127.0.0.1:2015 CLOSE_WAIT
> tcp 0 0 127.0.0.1:2015 127.0.0.1:8002 FIN_WAIT2
> tcp 0 0 0.0.0.0:8002 0.0.0.0:* LISTEN
Well, that FIN_WAIT2 means that the server socket is waiting for the client to finish
a packet... this used to be a TCP denial of service technique by flooding a server
with tcp packets that were incomplete, thus creating a boatload of open sockets in
the FIN_WAIT state. IIRC, that is. That is why it isn't responding to any more
requests.. it will stay there indefinitely waiting for the TCP transaction to
complete...
Anybody else remember more accurately... I could be completely wrong ;)
Brian
More information about the Seaside
mailing list