Are you sure the problem is with LWIP and not the web code doing the periodic call?
I had a web server which did a timeout call to update data from the embedded server every second. However when the server took more than a second to respond (bad wifi link, slow network, etc) then it would trigger a second request before the first was done. This resulted in eventually using all the LWIP buffers. I had to change the javascript code such that it only made another request one second after the first was received. This simple change fixed the bug... A good way to debug a website is to use developer tools in chrome. They will allow you to see when requests are made, how many are waiting, etc. Also you can throttle the web pages for different network speeds and see what happens. This was very powerful for figuring out my problems. Trampas On Wed, Sep 22, 2021 at 9:56 AM Info <i...@winformatik.ch> wrote: > Am 22.09.21 um 12:04 schrieb goldsi...@gmx.de: > > > > Sorry, I don't have an idea what's wrong here. > > > > Regards, > > Simon > > Thank you Simon (for your honest answer 😉 )... > > I made a new Wireshark capture file and logged the corresponding debug > output from the lwIP (I stripped down the capturing and logging, so it's > not huge). For the logging output the following debug macros were > activated: > TCP_DEBUG > TCP_INPUT_DEBUG > TCP_OUTPUT_DEBUG > > Maybe this will bring new insights where the problem might be. > > Kind regards, > Roland > > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
