[lkml]   [2001]   [Dec]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: TCP LAST-ACK state broken in 2.4.17-pre2 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

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:14    [W:0.022 / U:6.956 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site