On Sun, May 3, 2009 at 12:46 PM, Nicolas de Pesloüan < [email protected]> wrote:
> Jochen Hebbrecht wrote: > > Nicolas de Pesloüan schreef: > >> > >> Can you also explain why you are trying to use bridge ? > > > Nicolas, > > > > I'm not sure that bonding is the thing I need. I'll explain what I want > > to do. > > > > Please check this image: http://www.jochus.be/brol/networking.png > > * Purple lines: wired (UTP) > > * Blue (dashed) lines: wireless > > > > So in this building, there are 2 locations. Location A and B. There's no > > possibility to link them using a wired cable, and I don't like the net > > adapters who transmits packets using the 50Hz channel. > > > > In location A, there's a desktop and a notebook a. In location B, > > there's a notebook, a server which maintains e-mails, backup, > > Subversion, Archiva, ... and there's also printer (a network printer). > > Ok, now we understand what you are trying to do. In particular, I assume > the DHCP server is on the subnet of location B (or behind a router > connected on this subnet), so the expected DHCP offer will come from the > wire interface (eth0) and definitely not from the wireless interface > (eth1). Looking at "router" in the provided diagram, plus the placement of A and B, I am led to believe that location A is the primary network providing DHCP and outbound access. Furthermore, Jochen was getting a DHCP assignment over his wireless interface before he tried to enable bridging. Your suggestion of configuration as a router could work. But NAT would not if A is the primary location, because the printer would no longer have a address visible to location A.
_______________________________________________ Bridge mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/bridge
