[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #1713] Out-of-sequence TCP segments should be timed ou
From: |
Jim Pettinato |
Subject: |
[lwip-devel] [bug #1713] Out-of-sequence TCP segments should be timed out |
Date: |
Fri, 23 Mar 2007 14:43:53 +0000 |
User-agent: |
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322) |
Follow-up Comment #1, bug #1713 (project lwip):
Noticed that this bug is still in the list... but browsing the code, it
appears that a patch has already been applied to address this (see below).
Perhaps this bug just needs a status update and closed? (I didn't go back and
browse the history to see when this was added... but it was in at least by
0.7.2 I think).
in tcp_slowtmr():
-----------------------------------------------------------
/* If this PCB has queued out of sequence data, but has been
inactive for too long, will drop the data (it will eventually
be retransmitted). */
#if TCP_QUEUE_OOSEQ
if (pcb->ooseq != NULL &&
(u32_t)tcp_ticks - pcb->tmr >=
pcb->rto * TCP_OOSEQ_TIMEOUT) {
tcp_segs_free(pcb->ooseq);
pcb->ooseq = NULL;
LWIP_DEBUGF(TCP_CWND_DEBUG, ("tcp_slowtmr: dropping OOSEQ queued
data\n"))
}
#endif /* TCP_QUEUE_OOSEQ */
------------------------------------------------------------
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?1713>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #1713] Out-of-sequence TCP segments should be timed out,
Jim Pettinato <=