lwIP - A Lightweight TCP/IP stack - Bugs: bug #57710, Unable to reinitialize the TCP...
You are not allowed to post comments on this tracker with your current authentication level.
bug #57710: Unable to reinitialize the TCP connection
Submitter: | Praveen Kumar <praveen_embedded> | ||
Submitted: | Fri 31 Jan 2020 05:02:09 PM UTC | ||
Category: | TCP | Severity: | 3 - Normal |
Item Group: | Crash Error | Status: | Duplicate |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 2.0.3 |
Mon 03 Feb 2020 07:01:47 PM UTC, comment #5: |
Simon Goldschmidt <goldsimon> |
Mon 03 Feb 2020 12:29:11 PM UTC, comment #4: Hi Benjamin,
|
Praveen Kumar <praveen_embedded> |
Mon 03 Feb 2020 11:13:25 AM UTC, comment #3: First of all I suppose you are using IPv6? Since mld6_tmr should only be part if IPv6 is active i.e. LWIP_IPV6_MLD and LWIP_IPV6 is set in lwipopts.h
|
Benjamin K <bkausbk> |
Mon 03 Feb 2020 10:35:05 AM UTC, comment #2: Hi Benjamin,
|
Praveen Kumar <praveen_embedded> |
Mon 03 Feb 2020 07:09:38 AM UTC, comment #1: I had a similar problem for a long time, and I think I have fixed it now. In my case the reason was insufficient resources, but my MCU was not going to sleep, but the connection was interrupted because the WLAN device lost it's connection. I had a web server running on my system that was processing many asynchronous requests from a client. Once the connection became unstable and was about to be terminated, some TCP/IP responses could no longer be sent to the client. As a result, the PCBs from the pool were used up very quickly. But since the connection was never explicitly closed, they were never released. Because of that, I was forced to activate TCP_KEEPALIVE. For this purpose I have included in the file lwipopts.h
|
Benjamin K <bkausbk> |
Fri 31 Jan 2020 05:02:09 PM UTC, original submission:
Hi ,
|
Praveen Kumar <praveen_embedded> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-02-03 | goldsimon | Status | None | Duplicate | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed | |||
2020-01-31 | praveen_embedded | Attached File | - | Added LWIP_TCP_DataSentoutFirst.JPG, #48314 | |
Attached File | - | Added LWIPCommunicationIssue.JPG, #48315 | |||
Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-f8d8.
Corresponding source code
Sorry, I fail to follow those posts in detail, but let me just come back to what I think is the main question here:
No, currently there isn't.
However, there is bug #55598 to remind us that such a feature would be nice/wanted.
Being like that: closing this one as duplicate.
And for next time: if you just want to ask questions, please send a mail to the lwip-users list instead of starting a bug (unless you know it's a bug).