I like this idea. I guess I should read up on bridging. Tyrion
David Brown wrote: > I wouldn't expect any problems with normal basic protocols. It might > cause > problems with UDP or things that want reverse connections (active-mode > ftp). It will also increase latency. > > But, it might not even be necessary to do this, if the WIFI source is > willing to hand out multiple IP addresses to the same MAC. If you > WIFIðernet machine is configured as a bridge, when clients request > DHCP, > they will go directly to the WIFI router and get the request. > Essentially, > each machine will act as if it were on the WIFI network. > > I'm not sure what distribution you're running, since that will affect > bridging mode. Basically, you need to bring up the two network > interfaces, > say eth0, and eth1, and then bring up the bridge interface. At that > point, > you run dhcp on that machine on br0, and pretend as if eth0 and eth1 > don't > really exist. Something like this: > > brctl addbr br0 > brctl addif br0 eth0 > brctl addif br0 eth1 > dhcpcd br0 > > The utility may be brcfg in an older distribution. It is likely your > distribution will have convenient configuration files to set this up. > > You'll also need to make sure that 802.1d Ethernet Bridging is enabled in > the kernel (or the 'bridge' module loaded). > > The bridge interface supports the spanning tree protocol, so should deal > with whatever the WIFI router is doing. > > David > > -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
