Hello! Iliya Peregoudov <iperegudov@cboss.ru> wrote:
Hello Andreas,
Your supplicant have rejected EAP-MD5 method proposed by freeradius and have requested for EAP-TTLS method. freeradius have sent EAP-TTLS/Start request. But your supplicant have never replied. The problem seems to be in supplicant (AP is transparent for EAP methods anyway). What supplicant do you use?
Thanks for the info! Well, yesterday I tried with NetworkManager only. After installing the new version of freeradius tonight I tried with NetworkManager again with no luck. Then I decided to use Yast of the openSUSE I use and that made it. With the NetworkManager I had this compatibilityproblems described for Windows OIDs. The NetworkManager didn't like the server.
Andreas Meyer wrote:
Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP NAK [eap] EAP-NAK asked for EAP-Type/ttls [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 4 to 192.168.1.254 port 2048 EAP-Message = 0x010200061520 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x4fb647db4eb45230423119a23041222a
Andreas