On Tue, Jun 17, 2003 at 07:24:16AM -0400, Matt Grogan spoke thusly: >If you want to go further than that, like stop someone from getting their >information from DHCP and then statically defining it and keeping that >address, it gets a little more involved. Maybe reducing the lease time and >scripting to check that all the stations in the DHCP range are also in the >list of DHCP clients on the server would help. A slightly different angle, which just came up on the redhat-users ML a couple of days ago; which might work is : -> All DHCP leases get an account created on your internal DNS resolver. -> Your firewall refreshes your ruleset by only allowing a range of DHCP IP ranges, which have a corresponding DNS forward && reverse entry. This is similar to Win2K functionality whereby all DHCP addresses get an automatic DNS entry created. Someone mentioned that ISC's DHCP package supports such functionality, you might want to take a look. There will be some scripting involved, as Matt has already allured to. (snip rest)
