Hi, there are two connection setups in this scenario:
- EAP-TTLS authentication of client carol is successful because the passwords on the client and RADIUS side match. - EAP-TTLS authentication of client dave fails because the passwords on the client and RADIUS side differ. Best regards Andreas On 22.02.2016 10:32, yukou katori wrote:
Hi, It says "Passed" but it looks "fail" in the log: 205 rw-eap-ttls-radius <https://www.strongswan.org/uml/testresults/ikev2/rw-eap-ttls-radius/index.html> passed <https://www.strongswan.org/uml/testresults/ikev2/rw-eap-ttls-radius/console.log> https://www.strongswan.org/uml/testresults/ikev2/rw-eap-ttls-radius/console.log log: sending packet: from 192.168.0.200[4500] to 192.168.0.1[4500] (76 bytes) establishing connection 'home' failed No leaks detected, 1 suppressed by whitelist If you have PASS configuration and result, please forward to us kindly. Regards, _______________________________________________ Dev mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/dev
-- ====================================================================== Andreas Steffen [email protected] strongSwan - the Open Source VPN Solution! www.strongswan.org Institute for Internet Technologies and Applications University of Applied Sciences Rapperswil CH-8640 Rapperswil (Switzerland) ===========================================================[ITA-HSR]==
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Dev mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/dev
