On Jan 22, 2017, at 4:05 AM, ChoongHotmail Kim <concentric12@hotmail.com> wrote:
I've been having issues with my Windows 8.1 laptop as well as my Windows 10 laptop when trying to connect to my FreeRADIUS server via EAP-TTLS. My FreeRADIUS server is running on an Asus RT-AC68U router and was installed and configured per the instructions on https://github.com/RMerl/asuswrt-merlin/wiki/Setting-up-FreeRadius2-through-... . My problem is identical to the issue reported on http://lists.freeradius.org/pipermail/freeradius-users/2014-October/074177.h... , and unfortunately, the thread ended without any resolution.
The problem is Windows. What's going wrong with Windows? No idea... The logging in Windows is essentially non-existent. So all you get is either "success", or "fail".
I was hoping to find any advice with regards to resolving this particular use-case as I started as Mr. Rowe has by setting the "cipher-list" attribute to "ALL" as well as checking the installed status of my certificates. I am only having issues with the handshake when trying to connect with Windows 8.1 or Windows 10, but have none when connecting via Android. For reference, I've a sanitized version of the output for radius -XX when successfully connecting via my Android device. Thank you.
Showing a successful authentication doesn't help, unfortunately. Alan DeKok.