Is there any sort of "Best Practices" paper for secure DHCP implementation?
For example with a standard DHCP setup, what is to prevent someone from
sneaking into an empty office, jacking in an AirPort Express, and sitting in
their car outside the building hacking away to their heart's content? That
seems like something any script kiddie can pull off with minimal effort.
If DHCP is just one big security risk, then what else is recommended? We're
thinking of making our regular nodes all fixed IPs (but still NAT, of
course), and then opening up a small DHCP pool for guests. Hopefully we can
then lock down that DHCP pool from having very much access to the network or
even the internet.
Has anyone done anything like this? Is there a walkthrough the issues
involved and the steps necessary under OS X Server? Would that pool need a
different subnet or even a different gateway?
Workgroup Manager's Computer Lists function isn't going to help, is it? My
primary need for guest access is for visitors, usually with PCs, who want
access to check their e-mail and other net stuff. I have no qualms about
having to authenticate them before they get access, if that's a possibility.
TIA!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
