[lkml]   [2001]   [Dec]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectTCP LAST-ACK state broken in 2.4.17-pre2

    I came across the following behavior (sorry, no tcpdump but this should
    be easy to reproduce with the right tools):

    hostA hostB
    --------ACK-------X (packet lost)
    <-----data+FIN--------- (retransmit)
    <-----data+FIN--------- (retransmit)
    <-----data+FIN--------- (retransmit)
    <-----data+FIN--------- (retransmit)

    HostA is running Linux 2.4.17-pre2. HostB is running Symbian OS. All the
    sequence numbers pan out.

    Either LAST-ACK is completely broken or Linux just cannot handle a
    FIN-ACK that is piggybacked on a data segment, when received in LAST-ACK
    state. It should be acked as an out-of-window segment, as usual.
    Finally, the LAST-ACK state times out and Linux responds to the FIN
    segment with an RST.


    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:18    [W:0.031 / U:1.880 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site