|
||||||||
Actually, in a large network, multiple DHCP servers in a single logical subnet can be desirable for fail-over purposes. The trick is to set up multiple scopes that don't overlap, even though they may be in the same subnet. That way, if one of the DHCP servers fail, at least some clients will be assigned addresses, and you'll already have a second server up and configured for adding another scope to quickly if the first server is going to be out of commission for awhile. That said, I doubt the network in question is that large :) ________________________________ From: Lee Sharp [mailto:leesharp at hal dash pc dot org] Sent: Fri 9/29/2006 4:44 PM To: m0n0wall at lists dot m0n0 dot ch Subject: Re: [m0n0wall] DHCP server On Fri, 29 Sep 2006 11:57:21 -0600 "Aaron Cherman" <aaronc at morad dot ab dot ca> wrote: >> I have in my network a dhcp server running in a linux machine, >>everything >> was going on !! Then i installed the monowall as a dhcp server too, >>and i >> m in both dhcp servers using deny known clients and putting mac >>address to >> share ip. But it happens that when the monowall dhcp server is >>running, he >> down the other dhcp server !! > > Seems to me that it is poor network design to have more than one >DHCP server on a single logical subnet. Worse than that. It is like two people trying to drive the same car. Whatever my girlfriend thinks, it just doesn't work. :-) Lee --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch |