EAP-TTLS with Windows 10 issue

[Alan DeKok]

> On Dec 29, 2020, at 4:17 PM, André <netriver at gmail.com> wrote:
> I skipped that part.
> 
> ...
> (5) Sent Access-Challenge Id 145 from 192.168.31.183:1812 to
> 192.168.31.238:32772 length 0
> (5)   EAP-Message =
> 0x0108003d1580000000331403030001011603030028c34857c0f20068606675d9b046e010de603f0002f64bfe4325c7d774f64ade3bbc0322de50bd6530
> (5)   Message-Authenticator = 0x00000000000000000000000000000000
> (5)   State = 0xfc04b034f90ca583ae24f21be9755ad5
> (5) Finished request
> Waking up in 4.8 seconds.
> (0) Cleaning up request packet ID 140 with timestamp +61
> (1) Cleaning up request packet ID 141 with timestamp +61
> (2) Cleaning up request packet ID 142 with timestamp +61
> (3) Cleaning up request packet ID 143 with timestamp +61
> (4) Cleaning up request packet ID 144 with timestamp +61
> (5) Cleaning up request packet ID 145 with timestamp +61
> Ready to process requests

  And... nothing.

  If you wait a bit and then send another packet, the server will print a link to this page:

https://wiki.freeradius.org/guide/Certificate%20Compatibility

  The problem is that the Windows system is not configured correctly.  It doesn't like the servers certificate.

  Fix this by using and configuring the correct certificates.

  Alan DeKok.