I missed a place that when all data acked, FIN is send out and the flag will be
removed, then if peer side ACK the FIN, the connection will step to FIN_WAIT_2,
So please ignore this.
At 2019-06-12 23:42:09, "guangwei" wrote:
From the code, when active close in tcp_connection_close, the
>From the code, when active close in tcp_connection_close, the TCP state will
>change to FIN_WAIT_1 and if there is TX data meanwhile, it will set TCP flag
>TCP_CONN_FINPNDG also,
but there is no method in the stack for this TCP to step into the FIN_WAIT_2
state, the only thing this TCP can happ
