Thanks Joel. In case you find that bug, could you inform me.
--
View this message in context:
http://lwip.100.n7.nabble.com/zero-window-probe-causes-duplicated-byte-to-be-received-tp29221p29223.html
Sent from the lwip-users mailing list archive at Nabble.com.
__
There was a bug where send_nxt was not advanced during the zero window probe
and thus the zero window probe ACK caused LwIP to send back another ACK,
creating an ACK storm. This has been fixed on master. I can dig up the bug
report if you need it (away from git history at the moment)
Even with
Hi,
I am using Stable 1.4.1 in my device. This device sends 4MB of TCP data to a
Windows laptop. I am using netcomm API.
1. When Windows is about to use up its TCP buffer, it sends a packet (P1)
with rwnd = 0 and ACK to, say, 2M.
2. Within 0.12s after receiving P1, lwip sends a packet (P2) with s
> On Apr 1, 2017, at 7:25 AM, Mohamed Hnezli wrote:
>
> Thank you for support,
> Are there any way to change this, such as 1 ack for 5 TCP segments sent from
> client (lwip)
What you referring to is a stretch ACK (where the ACK covers more than 1 full
sized segment). This is not configurab
Thank you for support,
Are there any way to change this, such as 1 ack for 5 TCP segments sent
from client (lwip)
On 31 March 2017 at 19:10, goldsi...@gmx.de wrote:
> Mohamed Hnezli wrote:
>
>>
>> I am using lwip ontop of FreeRTOS to send data to a server. I am trying
>> to maximize the data flo
http://serverfault.com/questions/152363/bridging-wlan0-to-eth0
Ciao
Dirk
>
> https://lists.nongnu.org/mailman/listinfo/lwip-users
>
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
