On Thu, 10 Mar 2005, Jamie Lokier wrote:
Indeed, I have exactly the same problem with a device that must simultaneously connect to:
- the local customer-site ethernet - the local customer-site 802.11 wireless
Assuming you don't really need to talk to hosts on these networks, just route via them then this isn't that big problem... just a matter of proper route policies to select which traffic goes to which gateway on which interface. There is big problems only if the local IP assigned in one network is the same as the gateway IP in the other, but even this can be dealt with to some extent.
Ugly problems mainly arises in the IP stack if you need to talk directly to hosts on multiple networks with conflicting addresses. With some hacking it can be made to work most of the time, but somewhat racy on conflicts.
Regards Henrik - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
