You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To start with, I'm not sure this is indeed a bug:
Given two TCP sockets in listening state, each receives a SYN. Afterwards, the remote client sends a RST to each socket. After processing the first RST, one socket falls back to LISTEN. The second RST might be accepted by that socket as well, even if it is actually destined to the second socket. The second socket will be stuck in SynReceived and will be trying to send SYN+ACKs.
I was able to fix this behaviour by ignoring such packets in smoltcp::socket::tcp::Socket::accepts but this might not be the most elegant way.
The text was updated successfully, but these errors were encountered:
To start with, I'm not sure this is indeed a bug:
Given two TCP sockets in listening state, each receives a SYN. Afterwards, the remote client sends a RST to each socket. After processing the first RST, one socket falls back to LISTEN. The second RST might be accepted by that socket as well, even if it is actually destined to the second socket. The second socket will be stuck in SynReceived and will be trying to send SYN+ACKs.
I was able to fix this behaviour by ignoring such packets in
smoltcp::socket::tcp::Socket::accepts
but this might not be the most elegant way.The text was updated successfully, but these errors were encountered: