[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] lwip_close(), keep getting new socket (index) on subseq
|
From: |
Sergio R. Caprile |
|
Subject: |
Re: [lwip-users] lwip_close(), keep getting new socket (index) on subsequent lwip_socket() call |
|
Date: |
Fri, 4 May 2018 10:46:57 -0300 |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
Hi Johan,
similar issues have been asked in the list, and in some responses there
have been pointers to great texts where it is explained that due to
parallel paths and retransmissions and etcetera, sockets must remain
open for some time after the user wants them closed.
This is normal behaviour in all well-behaved networking stacks.
Perhaps there is a #define you can tweak to shorten this time. Search
the list, as I'm almost sure this has already been answered.
PD: Espressif has a modified "1.5" (aka non-existent), a git head
somewhere after 1.4 with lots of their patches and mods on top. No
longer lwIP...