Re: [lwip-users] Missing ACKs using LWIP 1.3.2

[Sergio R. Caprile]

I bet you won't find specific lwIP patches on this because it doesn't
seem to be an lwIP bug. Polling the ethernet controller every 10ms is a
very bad idea, unless you are absolutely sure there won't be more frames
arriving in that time frame than what can fit in its buffer. You should
interrupt and buffer/signal  and/or poll the controller as frequently as
you can.
Another common mistake is polling the controller for last frame only,
two or more consecutive frames arriving between polls cause only the
first one to be retrieved. My bet is that you are constantly losing
frames you don't care about, and once a day you lose an important one.

You can try fixing the code to be more responsive, or you can try
another port. Anyway, I suggest you check it for proper behavior by
running netio or something similar.

Porting lwIP is not as cumbersome as it might seem, I did.
You can try this ARM Coortex-M3 vendor-agnostic port here:

http://scaprile.ldir.com.ar/cms/category/os/lwip-port/

you can probably keep your link-layer driver. Let us know.

--