lwIP - A Lightweight TCP/IP stack - Bugs: bug #64874, MDNS incomplete TXT passed to...
You are not allowed to post comments on this tracker with your current authentication level.
bug #64874: MDNS incomplete TXT passed to result_fn
Submitter: | Marek Láník <mlanik> | ||
Submitted: | Thu 09 Nov 2023 07:56:01 AM UTC | ||
Category: | apps | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | Planned Release: | None |
lwIP version: | 2.2.0 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
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.
No changes have been made to this item
Powered by Savane 3.13-aa77.
Corresponding source code
Using mdns_search_service
If the incomming DNS answer is in two pbufs and TXT record is split between them, then called function result_fn parameter varpart contains incomplete information.
suspicious line of code follows:
/* Direct call result_fn with varpart pointing in pbuf payload */
req->result_fn(&ans, (const char *)p->payload + offset, ans.rd_length, flags, req->arg);