Quote:
Originally Posted by csuetians
tHEN WHAT HAPPENED?
|
If two DHCP-Server share the same network the one who comes first, marks first. Say the one that faster gives out the answer for the request will win and set the ip of the client.
Quote:
Originally Posted by csuetians
The problem is that I am not really sure how can I configure the SERVER and clients of DHCP to select only ONE main DHCP Server for IPs,and no one canot make any DHCP Server so how can I configure them??
|
Thinking about it i don't come up with any configuration options that would prevent a rogue server to send out dhcp-offers. So the best way to keep people from setting up their own dhcp is to not give them
any administration privileges. Which can be quite hard if you have someone come along with their own labtop or similar.
there are a lot of tools now a days that check for rogue dhcp servers. Try arpwatch or similar.
Also consider that DHCP-Broadcast normaly stops at physical network boundries, namely switches (?HUBS?). If you have switches that use broadcast redirect you might also have the option to restrictid this redirect with a mac filter. That would keep the rogue server out of most network segments. BUt it still would linger around in one...
If you have some programming skil you might think about using a dhclient on the dhcp server and look if it gets the dhcp-offer from the right server. Whith the right configuration you should not get any ip through dhcp when no other dhcp is running.
There are definetly more solutions to this problem, but those are the ones that came to my mind. Just do a search with "rogue dhcp" and see if you find something useful for you.
Greetings Zhjim