add
deny unknown-clients;
then define the macs you permit by defining a host:
host myhost{
hardware ethernet 00:11:22:33:44:55;
option host-name myhost;
}
On Fri, 16 Jul 2010 15:52:05 -0400, Tim Evans <[email protected]> wrote:
> A .EDU with insecure offices, network outlets, and labs, is trying to
> track down a rogue DHCP client on their network that also happens to be
> infected with conficker.
>
> They have a completely open DHCP setup:
>
> ddns-update-style ad-hoc;
> authoritative;
> subnet 192.168.9.0 netmask 255.255.255.0 {
> range 192.168.9.125 192.168.9.200;
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.9.255;
> option routers 192.168.9.1;
> option domain-name-servers 192.168.9.4;
> option domain-name "xxx.xxx.xxx";
> }
>
> Any connected machine can get an address from the range specified in the
> config file. Bouncing this one's lease merely results in it getting a
> new one.
>
> They know the rogue machine's MAC address, of course. Can they deny it
> a DHCP address based only on the MAC? How?
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
