Contacting DHCP servers is a task for a DHCP client, not a DHCP server. There are a number of scripts available which will send a request and listen to all responses (not just the first), generating an alert if any unexpected nodes responded. Google "rogue DHCP detect".
On Fri, Mar 9, 2012 at 3:25 AM, james garner <jamg...@googlemail.com> wrote: > Dear list, > > our DHCP requests are handled by dnsmasq on the main server. Every now and > then a technically illiterate person connects a device to the network that > by default acts as DHCP-server, may it be a print server or a switch. Is > there a way to tell dnsmasq to periodically scan for other DHCP-servers and > give a warning if necessary? > Thanks > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > >
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
