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" <caoguangwei...@163.com> wrote:
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 happen only wait waitclose timer expire and
break up the connection.
This issue is by design ? or something I missed ?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13426): https://lists.fd.io/g/vpp-dev/message/13426
Mute This Topic: https://lists.fd.io/mt/32042003/21656
Mute #vnet: https://lists.fd.io/mk?hashtag=vnet&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
