I’d like to validate my hostapd configuration by testing that I can login with a Windows 10 client. As a simple (?) test I thought I would use hostapd.eap_user. There are lots of nice entries pre-defined, but most of them don’t work with Windows 10. For example, Windows 10 no longer supports MD5 (out of the box). My knowledge of how to authenticate with Windows is fairly limited. Some help would be appreciated. I’ve tried several of the names and passwords in hostapd.eap_user but I have not been successful in authenticating. Do I need to configure Windows differently? Is there a different setting in hostapd.eap_user that I can use? $ hostapd -v hostapd v2.6 User space daemon for IEEE 802.11 AP management, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator Copyright (c) 2002-2016, Jouni Malinen <j@xxxxx> and contributors Windows Authentication * Enable IEEE 8021.1x Authentication * Microsoft: Protected EAP (PEAP) * Authentication Method: Secured Password (EAP-MSCHAP v2) * Enable Fast Reconnect — Selected * Authentication Mode: User authentication Thank you for tips for how to verify my configuration. …Duane Duane Murphy | Software Engineer | Mainspring | (c) 650-933-5438 _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
