Shadow doesn't send an RST response if server has no associated socket for incoming TCP packet #2162
Labels
Type: Bug
Error or flaw producing unexpected results
Milestone
If a host receives a TCP packet at a port that doesn't have a bound socket (no socket for the 5-tuple), the host just drops the packet without sending an RST packet.
shadow/src/main/host/network_interface.c
Lines 406 to 411 in d8481e5
This isn't super weird since normally a firewall will drop these packets, but in Shadow these are also dropped on localhost which is unexpected. In Shadow, a connect() on localhost to an unbound port will block forever (or until some timeout, I'm unsure which) since the connecting localhost socket will never receive a response.
Edit: Some discussion in #2679.
The text was updated successfully, but these errors were encountered: