Still happens on newer out-of-box devices as well (at least on my new MBP
before I properly configured it to disable unused EAP types). Can check timers
when I’m at a place to access the controller.
Lee Badman | Network Architect
Certified Wireless Network Expert (#200)
Information
Is this something you still see on the client-side, or was it a problem mainly
with older OS versions that aren’t around now?
What client exclusion timeout are you currently using?
Jeff
From: "wireless-lan@listserv.educause.edu"
on behalf of
Part of it is your EAP type, and whether users are forced to onboard to get
configured enough to use the WLAN (like w/ TLS). With PEAP/MS-CHAPv2, I’ve seen
many out of box, un-onboarded client device “auto connect” situations where OS
X or Windows does figure out what it needs for EAP type, but
Longer client exclusion times coupled with longer session timeouts mean the
clients most impacted are the troublesome clients i.e. it only feels broken
for the already broken clients.
I use a 60 second exclusion timeout with very long user session timeouts. The
longer exclusion timeouts are
Interesting, hopefully you get some relief. On this document about RADIUS
timers
https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/118703-technote-wlc-00.html
I can’t buy in to Client Exclusion being set to 120 seconds as a rule. Even at
60 it’s too long and makes
Brad,
If the IAPs are still available, I’d be willing to take those.
Thanks,
Rob Kobiske
University of Wisconsin – Stevens Point
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Brad Weldon
Sent: Wednesday, August 30, 2017
BTW, 8.2.161.0 just came out.
-H
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Wednesday, August 30, 2017 2:50 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Move In/Opening Week-