Messages in this thread | | | Date | Mon, 10 Dec 2001 20:54:54 +0200 | From | Mika Liljeberg <> | Subject | Re: TCP LAST-ACK state broken in 2.4.17-pre2 |
| |
kuznet@ms2.inr.ac.ru wrote: > Well, you can just add one line to tcp_input.c to repair this.
Thanks, that was quick! :)
> Duh, do specs say something about segments with seqs > above fin? I do not remember.
I don't think they do, aside from that LAST-ACK is a synchronized state. I.e., if you set RCV.WND to zero after receiving a FIN, any subsequent out-of-window (below or above) segment will be acked. However, I don't think it matters much, since above-window packets would in this case always be caused by a bug in the sender.
> Alexey
MikaL - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |