Hello, i have a problem with EAP using TTLS. I set up a second Freeradius Server (1.04) with a valid certificate from TrustCenter (The certificate from the first FR-Server was selfsigning by openssl - it works very well) The certificate is installed and radiusd -X comes up with no error message. But when i want to authenticate with securew2 or odyssey Client the authentication stopps after the first Access-Request: --8<-- rad_recv: Access-Request packet from host 10.87.80.1:3072, id=151, length=117 User-Name = "anonymous" NAS-IP-Address = 10.87.80.1 NAS-Port = 16 Calling-Station-Id = "00:05:4e:43:f8:1c" NAS-Identifier = "Spielzimmer" NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0201000e01616e6f6e796d6f7573 Message-Authenticator = 0x494893f6addf1946ac5be4d35596f0f3 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "anonymous", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: EAP packet type response id 1 length 14 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 0 users: Matched entry DEFAULT at line 70 modcall[authorize]: module "files" returns ok for request 0 modcall: group authorize returns updated for request 0 rad_check_password: Found Auth-Type EAP auth: type "EAP" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 0 rlm_eap: EAP Identity rlm_eap: processing type md5 rlm_eap_md5: Issuing Challenge modcall[authenticate]: module "eap" returns handled for request 0 modcall: group authenticate returns handled for request 0 Sending Access-Challenge of id 151 to 10.87.80.1:3072 EAP-Message = 0x010200160410573ff27c2d0f1c3dbaa4362e694da04f Message-Authenticator = 0x00000000000000000000000000000000 State = 0xc3115a008d79ac992dfde255f0e7ea2a Finished request 0 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... rad_recv: Access-Request packet from host 10.87.80.1:3072, id=151, length=117 Sending duplicate reply to client lancom-ap:3072 - ID: 151 Re-sending Access-Challenge of id 151 to 10.87.80.1:3072 --8<-- After this, the Client sends the same packet with the same id to the Server; it goes in circles. The working FR-Server continues after the first Access-Request with a second Access-Request with different id and the authentication process proceeds. The configuration is the same as the working FR-Server with selfsigning certificates. Does anybody has a little help for this strange behavior, maybe is the Trustcenter certifacte wrong? Regards, Michael