lwIP - A Lightweight TCP/IP stack - Bugs: bug #57346, TCP stop working
You are not allowed to post comments on this tracker with your current authentication level.
bug #57346: TCP stop working
Submitter: | Hubert Sack <hs4smd> | ||
Submitted: | Tue 03 Dec 2019 09:30:39 AM UTC | ||
Votes: | 90 | ||
Category: | TCP | Severity: | 3 - Normal |
Item Group: | None | Status: | Invalid |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Jump to the original submission
Tue 04 Feb 2020 09:17:06 PM UTC, comment #7: |
Simon Goldschmidt <goldsimon> |
Mon 20 Jan 2020 07:19:12 AM UTC, comment #6: I've actually I very similar problem. In my case I implemented a virtual network interface to send raw ethernet frames to an UART connected WLAN module. The module it self has no LwIP stack active, but sends out all the incoming data from the µC board and all received data are sent back to the LwIP stack.
|
Benjamin K <bkausbk> |
Fri 10 Jan 2020 07:47:57 PM UTC, comment #5: Last ping before closing as invalid... |
Simon Goldschmidt <goldsimon> |
Tue 03 Dec 2019 08:46:18 PM UTC, comment #4: OK, so you're using netconn API. That means you can have a bunch of problems when threading is done wrong.
|
Simon Goldschmidt <goldsimon> |
Tue 03 Dec 2019 08:33:01 PM UTC, comment #3: Yes, I'm sure that this is something in lwIP. Why? Because "ping" is not affected at all and I saw Dup ACK, Spurious Packets after returning the power of switch B.
|
Hubert Sack <hs4smd> |
Tue 03 Dec 2019 07:35:05 PM UTC, comment #2: How is this a crash error? How are you even sure this is a bug in lwIP?
|
Simon Goldschmidt <goldsimon> |
Tue 03 Dec 2019 02:11:26 PM UTC, comment #1: I did one more test and this discovered a huge problem:
|
Hubert Sack <hs4smd> |
Tue 03 Dec 2019 09:30:39 AM UTC, original submission:
The following text references the attached picture where my test environment is drawn. I did 6 tests - test 1 to 4 seems not to cause any problems. Test 5 and 6 results in stopping any further TCP traffic
|
Hubert Sack <hs4smd> |
Depends on the following items: None found
Items that depend on this one: None found
There are 90 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 12 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-02-04 | goldsimon | Status | Need Info | Invalid | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed | |||
2020-01-20 | bkausbk | Carbon-Copy | - | Added bkausbk | |
2020-01-10 | goldsimon | Status | None | Need Info | |
2019-12-03 | hs4smd | Attached File | - | Added main.c, #47980 | |
Attached File | - | Added main.h, #47981 | |||
Attached File | - | Added lwipopts.h, #47982 | |||
2019-12-03 | goldsimon | Item Group | Crash Error | None | |
2019-12-03 | hs4smd | Attached File | - | Added Errors.txt, #47974 | |
2019-12-03 | hs4smd | Attached File | - | Added Topology.png, #47971 | |
Attached File | - | Added WireShark.pdf, #47972 |
Powered by Savane 3.13-d3ae.
Corresponding source code
We need similiarities in "similar code", not similard as "it just doesn't work".
I'm closing this as invalid, please just continue posting here if anyone has valuable input on why this should be an lwIP bug (not a memory config error or whatever).