Hi Jozsef, Huge thanks for the excellent explanation =), I believe I understand it all now. I was a bit confused at first with the possible traversing from state NONE to TIME_WAIT, ESTABLISHED or CLOSE, but I believe I understood it now.
Just to make sure that I'm not wrong, I assume that we traverse from state NONE to TIME_WAIT in case we pick up an already established and running connection which is just about to close. In such case, we go from NONE to TIME_WAIT or CLOSE, correct me if I'm wrong? Have a nice day, Oskar Andreasson http://www.boingworld.com http://people.unix-fu.org/andreasson/ mailto: [EMAIL PROTECTED] ----- Original Message ----- From: "Jozsef Kadlecsik" <[EMAIL PROTECTED]> To: "Oskar Andreasson" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, May 02, 2002 8:21 AM Subject: Re: ip_ct_tcp_timeout_listen and none > On Tue, 30 Apr 2002, Jozsef Kadlecsik wrote: > > > The NONE state is the initial one when the conntrack entry is created. > > Depending on the flags of the packet (which triggered creating the > > conntrack entry) the state changes at once to SYN_SENT, SYN_RECEIVED, > > ESTABLISHED, TIME_WAIT or CLOSE (default conntrack). > > Oops, I must correct myself: the SYN_RECEIVED state is of course illogical > and the first packet cannot lead to this state. Sorry for the mistake. > > Regards, > Jozsef > - > E-mail : [EMAIL PROTECTED], [EMAIL PROTECTED] > WWW-Home: http://www.kfki.hu/~kadlec > Address : KFKI Research Institute for Particle and Nuclear Physics > H-1525 Budapest 114, POB. 49, Hungary > > >
