I threw in the towel and started adding the MACs to our controller blacklist to allow the APs to reject them at that level. Not as clean as you're suggesting, but diminishing returns..
thanks mike On 7/18/18 10:38 AM, John Kristoff wrote:
Friends, Over time there is some non-negligible number of devices and systems that attempt to connect and authenticate to an institution's WiFi network. Many of these seem to be from devices or systems that had been configured with a former employee, student, or affiliated user's credentials that are no longer valid if they ever were. Some of these forgotten clients might try to authenticate thousands of times a day. While they may not cause a significant operational problems hammering away, it would be nice to keep the airspace and auth logs as clean as possible. I've perused a couple of odd solutions that purport to do some form of triangulation, but before I dig too far done this road I thought I'd issue a query here. What do you do or do you recommend to locate and eradicate poorly managed and inspid WiFi clients? Thank you, John ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.
-- Mike Davis Systems Programmer V NSS - University of Delaware - 302.831.8756 Newark, DE 19716 Email da...@udel.edu ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.
