Closed apsun closed 2 years ago
Terminal 1: nc -l 127.0.0.1 1111 Terminal 2: nc 127.0.0.1 1111 < random
nc -l 127.0.0.1 1111
nc 127.0.0.1 1111 < random
Socket manages to send some data, then aborts the connection. Adding TCP_DEBUG_PRINT=1 interestingly makes it work fine, so this could be something related to TCP windows or ne2k capacity.
TCP_DEBUG_PRINT=1
No idea why I thought ne2k had anything to do with it, this is loopback
Fixed in 0efea08fab38bd9d96e7278d4fd9a4ed9abf13f0
Terminal 1:
nc -l 127.0.0.1 1111
Terminal 2:nc 127.0.0.1 1111 < random
Socket manages to send some data, then aborts the connection. Adding
TCP_DEBUG_PRINT=1
interestingly makes it work fine, so this could be something related to TCP windows or ne2k capacity.