1 Sep 2011 03:52
What's the reason for "OpenSSL: openssl_handshake - SSL_connect error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher"
2008 vpn <vpn2008 <at> gmail.com>
2011-09-01 01:52:48 GMT
2011-09-01 01:52:48 GMT
I'm try eap-fast method.
But error happens:
4c e8 59 6b 27
EAP-FAST: server_random - hexdump(len=32): 4e 5d da af 1f eb a8 e0 fa c6 27
89 e5 70 a3 fb 11 19 7a 4c c6 20 77 69 de 4b cd 38 b9 d8 40 dd
EAP-FAST: master_secret - hexdump(len=48): [REMOVED]
SSL: (where=0x4008 ret=0x228)
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:handshake
failure
SSL: (where=0x2002 ret=0xffffffff)
SSL: SSL_accept:error in SSLv3 read client hello C
OpenSSL: openssl_handshake - SSL_connect error:1408A0C1:SSL
routines:SSL3_GET_CLIENT_
HELLO:no shared cipher
SSL: 7 bytes pending from ssl_out
SSL: Failed - tls_out available to report error
EAP-FAST: TLS processing failed
EAP-FAST: PHASE1 -> FAILURE
EAP: EAP entering state SELECT_ACTION
EAP: getDecision: method failed -> FAILURE
EAP: EAP entering state FAILURE
EAP: Building EAP-Failure (id=116)
What does this mean? Is my config wrong?
My Config file is as following:
interface=eth2
driver=wired
logger_stdout=-1
logger_stdout_level=1
debug=2
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ieee8021x=1
eap_server=1
eap_user_file=/home/test/work/eap-fast/hostapd/hostapd-0.7.3/hostapd/hostapd.eap_user.wired
eap_reauth_period=3600
dh_file=/etc/hostapd/hostapd.dh.pem
use_pae_group_addr=1
pac_opaque_encr_key=000102030405060708090a0b0c0d0e0f
eap_fast_a_id=201112131415161718191a1b1c1d1e1f
eap_fast_a_id_info=test server
eap_fast_prov=3
pac_key_lifetime=604800
pac_key_refresh_time=86400
##### RADIUS configuration
####################################################
# for IEEE 802.1X with external Authentication Server, IEEE 802.11
# authentication with external ACL for MAC addresses, and accounting
# The own IP address of the access point (used as NAS-IP-Address)
own_ip_addr=127.0.0.1
# RADIUS authentication server
auth_server_addr=127.0.0.1
auth_server_port=1812
auth_server_shared_secret=radius*
And the content of hostapd.eap_user.wired is:
# Phase 1 users
"user" MD5 "password"
"test user" MD5 "secret"
"FAST-000102030405" FAST
# Phase 2 (tunnelled within EAP-PEAP or EAP-TTLS) users
"t-md5" MD5 "password" [2]
"DOMAIN\t-mschapv2" MSCHAPV2 "password" [2]
"t-gtc" GTC "password" [2]
"not anonymous" MSCHAPV2 "password" [2]
"user" MD5,GTC,MSCHAPV2 "password" [2]
"test user" MSCHAPV2 hash:000102030405060708090a0b0c0d0e0f [2]
"ttls-user" TTLS-PAP,TTLS-CHAP,TTLS-MSCHAP,TTLS-MSCHAPV2
"password" [2]
Config for wpa_supplicant is:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=root
ap_scan=0
fast_reauth=1
network={
ssid=""
scan_ssid=0
key_mgmt=IEEE8021X
eap=FAST
identity="user"
password="password"
anonymous_identity="FAST-000102030405"
phase1="fast_provisioning=1"
pac_file="/etc/wpa_supplicant.eap-fast-pac"
}
I noticed we should config certificate file for EAP-TLS/PEAP/TTLS.
But do we need config certificate file for EAP-FAST?
Best Regards.
SSL: 7 bytes pending from ssl_out
SSL: Failed - tls_out available to report error
EAP-FAST: TLS processing failed
EAP-FAST: PHASE1 -> FAILURE
EAP: EAP entering state SELECT_ACTION
EAP: getDecision: method failed -> FAILURE
EAP: EAP entering state FAILURE
EAP: Building EAP-Failure (id=116)
What does this mean? Is my config wrong?
My Config file is as following:
interface=eth2
driver=wired
logger_stdout=-1
logger_stdout_level=1
debug=2
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ieee8021x=1
eap_server=1
eap_user_file=/home/test/work/eap-fast/hostapd/hostapd-0.7.3/hostapd/hostapd.eap_user.wired
eap_reauth_period=3600
dh_file=/etc/hostapd/hostapd.dh.pem
use_pae_group_addr=1
pac_opaque_encr_key=000102030405060708090a0b0c0d0e0f
eap_fast_a_id=201112131415161718191a1b1c1d1e1f
eap_fast_a_id_info=test server
eap_fast_prov=3
pac_key_lifetime=604800
pac_key_refresh_time=86400
##### RADIUS configuration
####################################################
# for IEEE 802.1X with external Authentication Server, IEEE 802.11
# authentication with external ACL for MAC addresses, and accounting
# The own IP address of the access point (used as NAS-IP-Address)
own_ip_addr=127.0.0.1
# RADIUS authentication server
auth_server_addr=127.0.0.1
auth_server_port=1812
auth_server_shared_secret=radius*
And the content of hostapd.eap_user.wired is:
# Phase 1 users
"user" MD5 "password"
"test user" MD5 "secret"
"FAST-000102030405" FAST
# Phase 2 (tunnelled within EAP-PEAP or EAP-TTLS) users
"t-md5" MD5 "password" [2]
"DOMAIN\t-mschapv2" MSCHAPV2 "password" [2]
"t-gtc" GTC "password" [2]
"not anonymous" MSCHAPV2 "password" [2]
"user" MD5,GTC,MSCHAPV2 "password" [2]
"test user" MSCHAPV2 hash:000102030405060708090a0b0c0d0e0f [2]
"ttls-user" TTLS-PAP,TTLS-CHAP,TTLS-MSCHAP,TTLS-MSCHAPV2
"password" [2]
Config for wpa_supplicant is:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=root
ap_scan=0
fast_reauth=1
network={
ssid=""
scan_ssid=0
key_mgmt=IEEE8021X
eap=FAST
identity="user"
password="password"
anonymous_identity="FAST-000102030405"
phase1="fast_provisioning=1"
pac_file="/etc/wpa_supplicant.eap-fast-pac"
}
I noticed we should config certificate file for EAP-TLS/PEAP/TTLS.
But do we need config certificate file for EAP-FAST?
Best Regards.
_______________________________________________ HostAP mailing list HostAP <at> lists.shmoo.com http://lists.shmoo.com/mailman/listinfo/hostap
>
> I have another question now...I notice that if the supplicant
> processes a disassociation or deauth, we call
> wpa_supplicant_event_disassoc() (in blacklist.c), which then adds that
> BSSID to a blacklist. Then, the supplicant can no longer roam to that
> BSSID, even if it is a better choice.
>
> In our use case, we have a large number of access points and they can
> drop offline for maintenance periodically. What would folks recommend
> we do to keep these BSSID's from becoming permanently blacklisted just
> because they needed to reboot?
>
Seems this is true. Blacklist will be cleared if "No APs found".
In case of our implementation we don't hit this problem. We have
additional CQM signal - beacon_miss - from our driver (nl80211). Count
of beacon_miss is configurable from supplicant when bgscan starts. Our
firmware support this beacon_miss detection - so, it is usefull - we
can roam before deauthenitcation in case someone will switch off AP or
we loose connection.
I think we will push this CQM cfg80211/nl80211 compat-wireless +
hostap implementation soon.
So, in case someone will switch off AP, before we will get
deauthentication we get this beacon_miss event and we have chance to
roam to another APs. If there isn't another APs blacklist will be
cleared because of "No APs found".
BR
Janusz
RSS Feed