Conferences & Events
Events for all Levels and InterestsStay
Jump Start Your Career GrowthStay
Get on the Higher Ed IT MapStay
Uncommon Thinking for the Common Good™Stay
Hunting down rogue DHCP servers as well as allowing them.
Message from firstname.lastname@example.org
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Upon coming back from a nice break from work, we ended up having issues with a Rogue DHCP server spewing out 192.168.x.x addresses on our student VLAN. The way our network is setup right now is that we are allowing any and all traffic over our employee VLAN and our student VLAN. Yes we have plans to clamp this down to truly segment the traffic but this led me to ask the question to the listserv on how do people deal with the rogue DHCP servers? Also, do you have a plan in place that allows students to have a WAP on the student VLAN without any disruption to the other students’ network access?
So the tl;dr :
- How do you address/find/monitor for rogue DHCP servers?
- How do you deal with them once found? (Like best troubleshooting steps once the MAC address is found)
- How do you allow or disallow NAT’ed WAP’s interference with normal network operations?
This message is intended for the sole use of the individual to whom it is addressed. It may contain information that is privileged, confidential or exempt from disclosure under applicable laws. If you are not the intended addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone this message or any information contained within this message. If you have received this message in error, please immediately advise the sender by replying to this email and delete this message.