PyTCP icon indicating copy to clipboard operation
PyTCP copied to clipboard

Don't reapond to rst with rst

Open shoham-b opened this issue 3 years ago • 1 comments

Currently, if a packet is sent to a port which is not in stack.sockets, then it is responded with rst.

The issue with such behaviour raises when a rst is received, instead of ignoring it, a rst is sent back (protocols/tcp/phrx.py:89).

This is especially problematic if you put two pytcp instances since they enter an infinite loop.

I'd love to fix that, just opening an issue to open it up for discussion.

shoham-b avatar Jan 17 '22 09:01 shoham-b

Valid point. Something i definitely overlooked. Please feel free to fix. Just make sure you use the PyTCP_2_6 branch. Thank you.

ccie18643 avatar Jan 17 '22 14:01 ccie18643