Is there any progress with this problem?

Yep, same problem here as emiX is having. At first I was getting "no proposal chosen" errors, but after setting PFS group to "none" (which is kinda moronic default in Windows, but you can "conveniently" change that via PowerShell), it "established" the connec...

@maw as it was mentioned many times before, "username" that you see is not username but local-id on the client. Actual username and password used for authentication is in EAP message. Okay. Would it be possible for you to provide a config example of a working setup with EAP-Radius to Wind...

We are still receiving client IP address as username when radius request is sent to NPS on Windows after upgrade to v6.39RC17.

We are experiencing exactly the same. Radius to Windows Server 2016 Network Policy Server and IKEv2 client is a Windows 10 machine. 6.39rc12 and 6.38.1 are both still sending through an IP address (the road warrior's local IP) as the "Username" attribute in RADIUS. Isn't this meant to be t...

I'm trying to set up eap-radius with Windows NPS, but i keep getting these errors on my windows radius server: An Access-Request message was received from RADIUS client 192.168.xx.xx with an Extensible Authentication Protocol (EAP) message but no Message-Authenticator attribute. Anyone know how to s...

Hello,
When we try using EAP-radius we get an error saying it fails at requesting radius service=ipsec.
And the only services we can provide with radius is ppp, hotspot, dhcp, login and wireless.

Can anyone tell me how to configure this properly?