lwIP - A Lightweight TCP/IP stack - Bugs: bug #65581, UDP Socket Bind Should Bind To...
You are not allowed to post comments on this tracker with your current authentication level.
bug #65581: UDP Socket Bind Should Bind To Device
Submitter: | Matt Grochowalski <grochoge> | ||
Submitted: | Wed 10 Apr 2024 07:02:45 PM UTC | ||
Category: | UDP | Severity: | 3 - Normal |
Item Group: | Change Request | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | Planned Release: | None |
lwIP version: | git head |
Thu 11 Apr 2024 01:44:13 PM UTC, comment #3: |
Matthias Dietrich <matthiasdietrich> |
Wed 10 Apr 2024 08:40:20 PM UTC, comment #2: Linux behaves the same way.
|
Matt Grochowalski <grochoge> |
Wed 10 Apr 2024 08:09:58 PM UTC, comment #1: Windows Sockets can sometimes behave in a very unique way. We are trying to follow the opengroup sockets standards. Linux follows them better than Windows, can you please test how Linux behaves in this situation? |
Simon Goldschmidt <goldsimon> |
Wed 10 Apr 2024 07:02:45 PM UTC, original submission:
I'm porting an existing application that sends multicast traffic via the Berkley socket API (in this case on Windows) and running into an issue.
|
Matt Grochowalski <grochoge> |
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.
Powered by Savane 3.13-caa5.
Corresponding source code
I happen to have an application that also sends multicast traffic. It does bind() but also sets the socket option IP_MULTICAST_IF before calling sendto(). That requires having LWIP_MULTICAST_TX_OPTIONS set.
That might be a more "standard" workaround than using LWIP_HOOK_IP4_ROUTE_SRC.