G+_James Berry Posted January 24, 2014 Share Posted January 24, 2014 RE: DHCP in Episode 77. My thoughts are to limit my network nodes/available IP addresses to my established/expected (DHCP/static) nodes plus 1-2 for flexibility to limit unauthorized access from people who don't belong on it. I've had the unsecured network before (apartment environment) and people took 3 "hints" (read: forced disconnects) to get off/stay off of it and then the next day rinse/repeat. Limiting the overall number also means that you will know exactly is on the network. Guest networks are wonderful too :).? Link to comment Share on other sites More sharing options...
G+_Fr. Robert Ballecer, SJ Posted January 25, 2014 Share Posted January 25, 2014 Me... I enjoy a good DeAuth attack every once in a while. :) Link to comment Share on other sites More sharing options...
G+_Tom DiGianvittorio Jr. Posted January 26, 2014 Share Posted January 26, 2014 Statics are good to know where stuff is but the vast majority of my users have to use static IPs as there are no DHCP servers available and it can be a pain explaining to someone on the phone how to set an IP when most of my terminology goes over their head. Also, they're all on the company domain and usually don't have network admin rights. That makes it even more fun trying to get them logged in as a local account in Win7 that does have network admin rights. Link to comment Share on other sites More sharing options...
G+_Ben Tyger Posted February 2, 2014 Share Posted February 2, 2014 You could be really sneaky. Setup up your DHCP server with reservations for all or devices or give the devices a static IP. Then make your DHCP server give out incompatible network information to any non-reserved device. Link to comment Share on other sites More sharing options...
Recommended Posts