[lwip-devel] [bug #34517] persist timer is started although there is unacked data

[Simon Goldschmidt]

URL:
  <http://savannah.nongnu.org/bugs/?34517>

                 Summary: persist timer is started although there is unacked
data
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: goldsimon
            Submitted on: Mo 10 Okt 2011 07:50:11 GMT
                Category: TCP
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 
            lwIP version: CVS Head

    _______________________________________________________

Details:

Is it correct that the persist timer is started although there is unacked
data? I thought that this timer is responsible to prevent losing ACKs that
open the window and I would have assumed that in the case where the window is
not 0, the normal RTO-timeout retransmission would take place.

Like it is now (e.g. when the complete window is unacked), the persist timer
retransmits 1 byte of the oldest unacked segment instead of transmitting 1
byte out-of-window or retransmitting the complete oldest unacked segment.




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?34517>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/