|Subject:||Re: [lwip-users] Sending to a non-local network without default netif set|
|Date:||Wed, 19 Nov 2014 09:04:40 +0000|
well yes. I was talking about the scenario you describe in 1).
Although my experience with the windows stack in this world has always been: “the last connected interface wins and is used for default gateway” which always sucked when my 100Mbit cable was detected first and the wireless connection last (when transferring big files).
The solution was to unplug/replug the Ethernet cable.
But yeah. The other scenario in my opinion is simply a misconfiguration and can never work in real life so we shouldn’t strive to support that at all.
I don’t see LwIP in a routing/switching context, so VLAN is also a topic that I would not expect to be covered by us. Normal clients don’t need to be aware of VLAN tagging as this is usually done between switches.
IP forwarding and “real” routing is also out of scope for LwIP imho.
But still. We do support multiple netifs, so we should make an effort to support configurations that come to mind easily, like two or more netifs on the same subnet.
“Trunking” or “bonding” or “link bundling” (e.g. LACP) is also out of scope for LwIP imho.
Hope you guys agree.
"we do have a setup with two netifs and we cannot determine what the customer will do with the device so we need to
also check for „same subnet“ scenarios."
|[Prev in Thread]||Current Thread||[Next in Thread]|