We did see this in beta testing and for us it was caused by SHA1 radius
certificate. We had a 10year cert so didn’t have to update and so got caught
out with a SHA1(relevant to other discussion). We ended up updating to SHA2
before IOS 11 was released.
We didn’t see issues for different radius
On Wed, 1 Nov 2017, James Andrewartha wrote:
> One distinction about using a private CA is that you can have an
> extremely long root CA, and then have shorter lived certificates signed
> by that CA that are rotated. However, without onboarding to install the
> CA for the SSID vs just trusting
Dear All
Thank you for your information. The problem can be fixed by the new release
today, IOS11.1
Have a nice day.
Yours,
Linchuan Yang (Antony)
MEng, ACMP
Wireless Networking Analyst
Network Assessment and Integration,
IITS-Concordia University
Tel: (514)848-2424 ext. 7664
From: The
All,
We have been battling this issue with EAP-MSCHAPv2/PEAP on our BYOD network
since September just after the iOS 11.0.0 release. We never had issues before
with onboarding any iOS 10.x versions. We have a few Cisco TAC cases open on
the issue and have gone down the path of it being it being
