lwIP - A Lightweight TCP/IP stack - Bugs: bug #61558, Possibly faulty behaviour on...
You are not allowed to post comments on this tracker with your current authentication level.
bug #61558: Possibly faulty behaviour on receiving large payloads with mqtt+tls causing disconnect
Submitter: | evot1 | ||
Submitted: | Thu 25 Nov 2021 01:01:37 PM UTC | ||
Category: | pbufs | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Works For Me |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 2.1.0 |
Jump to the original submission
Tue 04 Jan 2022 07:55:23 AM UTC, comment #12: |
evot1 |
Wed 01 Dec 2021 10:27:06 AM UTC, comment #11: Is there some indication of when it will be fixed/looked at? It would be great if you could tell me how long it usually takes.
|
evot1 |
Mon 29 Nov 2021 08:26:35 AM UTC, comment #10: Ok in that case I agree with you that getting mqtt to handle this is is what needs to be fixed primarily.
|
evot1 |
Mon 29 Nov 2021 08:11:42 AM UTC, comment #9: I think I know what you mean. And maybe this can be fixed for this mqtt case by chaining packets together. However, it is perfectly valid for any mqtt server's TCP stack to send out responses in split packets.
|
Simon Goldschmidt <goldsimon> |
Mon 29 Nov 2021 08:00:33 AM UTC, comment #8: To clarify; the issue is that the a disconnect event is triggered in lwip mqtt, i.e before any function calls to our code.
|
evot1 |
Fri 26 Nov 2021 03:59:55 PM UTC, comment #7: Again, I'm not sure I understand what you mean.
|
Simon Goldschmidt <goldsimon> |
Fri 26 Nov 2021 02:53:27 PM UTC, comment #6: Ahh sorry, I understand what you mean now.
|
evot1 |
Fri 26 Nov 2021 02:28:24 PM UTC, comment #5: Yes, exactly this is what i see!
|
evot1 |
Fri 26 Nov 2021 02:13:00 PM UTC, comment #4: Ah, ok, I think I may know what's happening: First, the MQTT header is passed in one RX callback and only after that, a 2nd callback is made with only MQTT data (because the header has been passed in already, but in a separate call). Is this what you see?
|
Simon Goldschmidt <goldsimon> |
Fri 26 Nov 2021 01:15:13 PM UTC, comment #3: Thank you for your quick reply!
|
evot1 |
Fri 26 Nov 2021 12:26:49 PM UTC, comment #2: I'm not sure I understand the problem at hand. Can you describe it a bit more? Ideally with an example or a unit test config that shows what's going wrong for you? |
Simon Goldschmidt <goldsimon> |
Fri 26 Nov 2021 10:37:45 AM UTC, comment #1: Update: The patch solved the issues in mqtt but is causing issues for other applications using tls.
|
evot1 |
Thu 25 Nov 2021 01:01:37 PM UTC, original submission:
We are using
|
evot1 |
No files currently attached
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-01-04 | yarrick | Status | None | Works For Me | |
Open/Closed | Open | Closed | |||
2021-11-25 | evot1 | Carbon-Copy | - | Added -email is unavailable- | |
Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-f8d8.
Corresponding source code
After further investigation, with the information Simon provided we have concluded that this issue was caused by one of our own patches. Excuse the hassle.
Thank you for your support on the matter. This issue can be closed.