|Subject:||Re: [lwip-devel] [patch #9134] bind udp and tcp pcbs to a specific netif|
|Date:||Wed, 05 Oct 2016 10:29:29 +0200|
|User-agent:||AquaMail/18.104.22.168 (build: 27000209)|
While I understand your setup,
I just do not see it as a common use case to justify adding code for it.
Since lwip is open source, you're of course free to do this in your local sources.
Gesendet mit AquaMail für
Am 5. Oktober 2016 10:21:27 vorm. schrieb Alice Reichart <address@hidden>:
_______________________________________________Hello Simon,in our case the routing mechanism can be ambiguous.We have several devices in the internal network that have static ips. However the netmask/ip addresses of the external net are not known, it is likely they overlap.There are other ways to solve this, but I think binding pcbs to netifs is the clean one and can be beneficial in other setups with more than one interface.Also, as a user, you can route one time in the initialization of a pcb, bind it accordingly and thus save many calls to ip_route().On Tue, Oct 4, 2016 at 10:11 PM, Simon Goldschmidt <address@hidden> wrote:Update of patch #9134 (project lwip):
Status: None => Wont Do
Open/Closed: Open => Closed
Follow-up Comment #1:
I'm sorry to turn you down, but I won't integrate this one.
The standard way to achieve what you want is to bind to the netif's IP
address. That means you'll have to adopt to address changes, but with lwIP
this is easy to do.
lwip-devel mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|