[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #65581] UDP Socket Bind Should Bind To Device
From: |
Matt Grochowalski |
Subject: |
[lwip-devel] [bug #65581] UDP Socket Bind Should Bind To Device |
Date: |
Wed, 10 Apr 2024 15:02:45 -0400 (EDT) |
URL:
<https://savannah.nongnu.org/bugs/?65581>
Summary: UDP Socket Bind Should Bind To Device
Group: lwIP - A Lightweight TCP/IP stack
Submitter: 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
Discussion Lock: Any
Planned Release: None
lwIP version: git head
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Wed 10 Apr 2024 07:02:45 PM UTC By: Matt Grochowalski <grochoge>
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.
Example usage:
1. bind() to 192.168.1.1
2. sendto() to 224.0.0.1
Result in Windows:
Packet is sent out over interface 192.168.1.1 to 224.0.0.1
Result in LWIP:
Send fails with ERR_RTE/EHOSTUNREACH
I see LWIP has the ability to bind to a specific interface, but does not do so
with a normal bind() call.
I believe an option should be added to do so in a normal bind() call,
returning an error if a netif with the bound address doesn't exist.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/bugs/?65581>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
- [lwip-devel] [bug #65581] UDP Socket Bind Should Bind To Device,
Matt Grochowalski <=