Henrik Nordstrom wrote:
> If Linux could manage different IP stacks per interface this would not be
> a problem, but as it is today the same IP stack is used for all interfaces
> making dual homing (not routing) a bit troublesome when the same addresses
> may be in both networks..
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
and auto-configure both interfaces using DHCP to connect to hosts on
the internet as best as possible through all available interfaces.
There is absolutely no guarantee that I won't see a network or even
address conflict on the two interfaces, as they may be _separate_
networks each behind a NAT to the outside world over ADSL.
In fact, it's quite likely that DHCP for each interface will provide a
192.168.0.0/24 address, as that seems to be the typical setup of both
kinds of ADSL NAT router...
Any suggestion of asking customer-site to specially configure their
network rather defeats the point, which is a device which
automatically tries available connections, using DHCP, and routes its
traffic over whichever one works best at any time.
-- Jamie
-
: 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
