Ryan,
In our Cisco/Airespace environment, on each WLAN, we set the DHCP
address assignment to "required". This forces the controller to only
allow traffic to be forwarded for clients that obtained their DHCP lease
from a DHCP server that is behind the controller on our wired
infrastructure. This feature has worked very well for us in EECS. I
believe this will work for you.
Fred
Ryan Lininger wrote:
I have been having some issues recently with DHCP on the wireless
network. It really has been misconfigured laptops running internet
connection sharing so far (notion malicious) but we have been
experiencing outages because of it. We are a Cisco Switched
environment but our wireless network is a Cisco and 5G network with a
bluesocket captive portal. I have DHCP snooping running on all the
switches in our environment that can run it but that is the only way
that I have been able to battle this issue. Everything else is
manually hunt done the culprit and meet with them to fix their machine.
I would like to know how others have been battling the problem of
rogue systems serving DHCP on their wireless network? I wouldn't mind
hearing how people have battled this problem on the wired network
either (these solutions may port over).
Any help is appreciated.
Ryan.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
begin:vcard
fn:Fred Archibald
n:Archibald;Fred
org:University of California;Electrical Engineering and Computer Sciences
adr:;;319 Soda Hall;Berkeley;California;94720-1776;USA
email;internet:[EMAIL PROTECTED]
title:Network Manager
version:2.1
end:vcard
