Went as far as to turn STP off for the bridge. Upgrading to 2.4.17 after reading some snippits that implied that there was some bridge-related stuff fixed recently helped. I was successfully able to bind dhcpd to the bridge device.
Dan On Sat, 2 Feb 2002, Lennert Buytenhek wrote: > Have you tried setting the stp timers to small values? Try something > like: > > # brctl setfd br0 0 > > > cheers --Lennert > > > On Fri, Jan 25, 2002 at 05:21:02PM -0800, Daniel M. DiPasquo wrote: > > > > > Has anyone successfully attached dhcpd to a bridge device (e.g. bridge0) > > or an interface that's in the bridge (e.g. eth1 in bridge0)? Mailing list > > archives sort of hint at it, but I haven't found any confirmation that it > > can be done. > > > > If I attach dhcpd to bridge0, dhcpd doesn't see any DHCPDISCOVER probes > > that should be going across the bridge. > > > > If I attach dhcpd to eth1, which is in bridge0, dhcpd reports seeing > > DCHPDISCOVER packets, and sending out DHCPDOFFER packets in response, but > > the client never receives them and eventually times out. > > > > I have been trying for much of this week to no avail, and I haven't found > > any documentation on doing so or if it is known to be possible or > > impossible. My attempts to locate where the break is are difficult > > because tcpdump (even tcpdump 3.7.1) gives me very little information on > > traffic "in the bridge". Any help would be greatly appreciated. > > > > Thanks, > > > > Dan > > > _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
