F5/unison
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

tcp: MaxRxSequence is sometimes too large

Browse Source
This commit is contained in:
Christoph Döpmann
2017-02-06 13:28:12 +01:00
parent ead564e9dd
commit 6d930cd65c
2 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
RELEASE_NOTES
View File

@@ -78,6 +78,7 @@ Bugs fixed
- Bug 2604 - QosData frames with Block Ack policy should be separated by SIFS as long as they belong to the same TXOP
- Bug 2605 - A HT/VHT station transmitting to a legacy access point results in a null throughput
- Bug 2606 - Ideal rate manager does not work correctly when a HT/VHT station is transmitting to a legacy access point
- Bug 2613 - MaxRxSequence () is sometimes too large
- Bug 2607 - Minstrel HT manager results in an endless loop when a 802.11ac station is transmitting to a 802.11a access point
- Bug 2614 - RIP header version should be set to 2
- Bug 2627 - Ipv6RawSocket does not honor the bound interface when sending packets

2
src/internet/model/tcp-rx-buffer.cc
View File

@@ -114,7 +114,7 @@ TcpRxBuffer::MaxRxSequence (void) const
{ // No data allowed beyond FIN
return m_finSeq;
}
else if (m_data.size ())
else if (m_data.size () && m_nextRxSeq > m_data.begin ()->first)
{ // No data allowed beyond Rx window allowed
return m_data.begin ()->first + SequenceNumber32 (m_maxBuffer);
}