On Fri, 28 May 1999, Andrew Macks wrote:
>
>
> On Tue, 25 May 1999, Derrick J Brashear wrote:
>
> > The machine in question has bridging enabled, and eth1 is set up as
> > 127.0.0.1/255.0.0.0;
>
> First things first, why are you using 127.0.0.1? This is the local host
> address, this should never ever be used on a LAN.
It doesn't (or shouldn't) matter, but I can change it if need be.
>
> You should be using 192.168.xxx.xxx and/or 10.xxx.xxx.xxx
By the time I send this message it will be 10.0.0.1. It's not going to
help the rest, though...
> You could quite easily setup the two networks in different class C's and
> use your machine as the bridge between both, this is not a problem.
Well, that defeats the point; Right now I have a single class C which is
being shared by the wired and wireless networks, and it's not NAT; The IP
addresses are real, and visible to the outside world. A single DHCP server
running on a machine on the wired network serves both the wired and
wireless hosts, and there is no reason a wireless host can't move to the
wired network and keep its IP address, or vice versa, *except* that hosts
on the wireless side can't talk to the IP corresponding to the wired
interface on the bridge/router.
After more thought I came up with 2 potential solutions:
a) add another network card to the bridge/router. bridge between eth0
(wired) and eth1 (wireless), route betweeen eth2 (wired) and ppp0(modem).
i'm not sure how bitter the machine would be about having 2 interfaces on
the wired network.
b) explicitly setting a host route out eth1 for hosts on the wireless
network makes everything happy, but eliminates the ability to migrate
addresses. Howwever, the bridge code "learns" what's where, so having a
way for the bridge to let a userspace daemon know and maintain routes
would help this. The bridge code mentiosn under "todo" a netlink
interface. So the right way may be a netlink notifier and a userlevel
daemon which listens for it and using /proc/net/bridge and arp entries,
adds or deletes host routes on eth1 (the wireless interface)
I don't like either of these, but given that I'm unwilling to put the DHCP
server on the bridge/router and subnet, they appear to be my only choices.
-D
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
