On Thu, Feb 25, 1999 at 06:23:35PM +0100, Luca Olivetti wrote:
> long TCP timeout. "RST-provoking" means that the kernel recognizes that the
> packets have the wrong IP address and fakes a "RST" packet as a reply, so the
> connection terminates immediately (RST=Reset, I think).
Almost, but not quite. What happens is that the kernel
changes the IP address on packets going out. This has
two effects. One is that we now send out packets with
our correct new address, instead of the old incorrect
one, so we get any answers. The other effect is that the
TCP connection info is now incorrect. The remote server
gets a packet that appears to come from an existing TCP
connection,but from a client it never heard of before
(it only heard from the old address). According to the
TCP specs if you get a packet belonging to a connection
you don't know anything about you should send a RST packet
(reset), which will close down the remote socket without
further ado. That's what usually happens.
--
Erik Corry [EMAIL PROTECTED] Ceterum censeo, Microsoftem esse delendam!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
