Well, this seems to be half the story. If I remove the close() and
let server bleed file descriptors, the RST goes away. If I add a
read() on the socket after sending all the data, the RST goes away.
However, there's NO DATA on the socket. read() returns zero until
the client closes the socket.
> Looks like the application on the Linux system is issuing a close() on
> the socket before reading all of the available data. That always
> causes a RST to be sent.
Here's some stripped down code to generate bogus (I think) TCP
resets on 2.2.14-17.
The RST is generated when the server closes
I've been trying to get xsane-win32 working with a linux server.
It keeps failing because read() on the win95 box returns an error
just before the data transfer is complete.
Dumping the conversation, I see linux sending a TCP RST:
00:26:29.260171 > porky.cisco.com.1034 > scan.1029: P 2185689:21
3 matches
Mail list logo
