On Mon, Dec 29, 2008 at 06:05:37PM -0500, Brian A. Seklecki wrote: > > e bridge solves the problem. Am I trying to do something > > fundamentally wrong or just unsupported ? Any plan to support something like > > this ? > > No, that sounds like a very standard / expected configuration. There is something a little amiss with dhcp client and bridging, I haven't really taken the time to investigate in detail and see what is happening. I reasonably often use bridge(4) to share one desk-port between a couple of laptops, or to sniff "in-line" on some other machine's traffic. If I want the bridging machine to run dhclient, I have to use dhclient on the "upstream" interface - when in theory I would expect it to work on any member of the bridge. In other circumstances, especially with agr, or where usb interfaces may come and go, this can be a pain since you may not know which interface is "upstream". I forget if my attempt to use a tap(4) member to work around this was successful or not, but you might try that too. -- Dan.
Attachment:
pgpau_dYueLaB.pgp
Description: PGP signature