Enet channel bonding + DHCP server = ?

Michael O'Donnell mod+gnhlug at std.com
Tue Jan 21 13:48:01 EST 2003


>>dhcpd is unhappy - it complains about multiple interfaces on the same
>>subnet, even thoughI've told dhcpd to use bond0 instead of the
>>"real" interfaces eth0 and eth1, as if it's gone and ferreted out
>>the other interfaces and is secretly listening >on them, too.
>[...snip...]
>>Before I get too far into analyzing this I figured I'd ask the
>>gathered multitudes to smack me with a clue-bat - is there some
>>reason in principle such a rig can't work?
>
> I've never seen dhcpd complain about interfaces before, usually
> it just complains that you don't have a clause for each network
> currently configured.


Heh.  I'm guessing you've not seen such behavior
because this is a fairly unusual setup - who tries
to serve DHCP from a box with bonded NICs?  I just
now grabbed the sources for dhcpd and hacked 'em a
bit - I've got some other stuff to tend to but I'll
test it soon and see what happens.

I definitely have a clause for every network that's
configured; that's not the problem.  The problem is
that DHCP is unhappy about seeing packets from the
same subnet arriving on two different interfaces
because (I speculate) it's run off and "discovered"
all the interfaces and doesn't know that it's OK
for this to be happening because bonded interfaces
do in fact have the same MAC and IP.




More information about the gnhlug-discuss mailing list