I am fairly new at this. I am leaning more towards a configuration issue in freeradius. The configuration needs to be adjusted to handle some difference in the HP AP vs the Cisco AP. root@Radius2:/usr/local/etc/raddb # radiusd -X radiusd: FreeRADIUS Version 2.2.5, for host i386-portbld-freebsd10.0, built on Jul 22 2014 at 12:54:06 Copyright (C) 1999-2013 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License. For more information about these matters, see the file named COPYRIGHT. Starting - reading configuration files ... including configuration file /usr/local/etc/raddb/radiusd.conf including configuration file /usr/local/etc/raddb/proxy.conf including configuration file /usr/local/etc/raddb/clients.conf including files in directory /usr/local/etc/raddb/modules/ including configuration file /usr/local/etc/raddb/modules/wimax including configuration file /usr/local/etc/raddb/modules/always including configuration file /usr/local/etc/raddb/modules/attr_filter including configuration file /usr/local/etc/raddb/modules/attr_rewrite including configuration file /usr/local/etc/raddb/modules/cache including configuration file /usr/local/etc/raddb/modules/chap including configuration file /usr/local/etc/raddb/modules/checkval including configuration file /usr/local/etc/raddb/modules/counter including configuration file /usr/local/etc/raddb/modules/cui including configuration file /usr/local/etc/raddb/modules/detail including configuration file /usr/local/etc/raddb/modules/detail.example.com including configuration file /usr/local/etc/raddb/modules/detail.log including configuration file /usr/local/etc/raddb/modules/dhcp_sqlippool including configuration file /usr/local/etc/raddb/sql/mysql/ippool-dhcp.conf including configuration file /usr/local/etc/raddb/modules/digest including configuration file /usr/local/etc/raddb/modules/dynamic_clients including configuration file /usr/local/etc/raddb/modules/echo including configuration file /usr/local/etc/raddb/modules/etc_group including configuration file /usr/local/etc/raddb/modules/exec including configuration file /usr/local/etc/raddb/modules/expiration including configuration file /usr/local/etc/raddb/modules/expr including configuration file /usr/local/etc/raddb/modules/files including configuration file /usr/local/etc/raddb/modules/inner-eap including configuration file /usr/local/etc/raddb/modules/ippool including configuration file /usr/local/etc/raddb/modules/krb5 including configuration file /usr/local/etc/raddb/modules/ldap including configuration file /usr/local/etc/raddb/modules/linelog including configuration file /usr/local/etc/raddb/modules/otp including configuration file /usr/local/etc/raddb/modules/logintime including configuration file /usr/local/etc/raddb/modules/mac2ip including configuration file /usr/local/etc/raddb/modules/mac2vlan including configuration file /usr/local/etc/raddb/modules/mschap including configuration file /usr/local/etc/raddb/modules/ntlm_auth including configuration file /usr/local/etc/raddb/modules/opendirectory including configuration file /usr/local/etc/raddb/modules/pam including configuration file /usr/local/etc/raddb/modules/pap including configuration file /usr/local/etc/raddb/modules/passwd including configuration file /usr/local/etc/raddb/modules/perl including configuration file /usr/local/etc/raddb/modules/policy including configuration file /usr/local/etc/raddb/modules/preprocess including configuration file /usr/local/etc/raddb/modules/radrelay including configuration file /usr/local/etc/raddb/modules/radutmp including configuration file /usr/local/etc/raddb/modules/realm including configuration file /usr/local/etc/raddb/modules/redis including configuration file /usr/local/etc/raddb/modules/rediswho including configuration file /usr/local/etc/raddb/modules/replicate including configuration file /usr/local/etc/raddb/modules/smbpasswd including configuration file /usr/local/etc/raddb/modules/smsotp including configuration file /usr/local/etc/raddb/modules/soh including configuration file /usr/local/etc/raddb/modules/sqlcounter_expire_on_login including configuration file /usr/local/etc/raddb/modules/sql_log including configuration file /usr/local/etc/raddb/modules/sradutmp including configuration file /usr/local/etc/raddb/modules/unix including configuration file /usr/local/etc/raddb/modules/acct_unique including configuration file /usr/local/etc/raddb/eap.conf including configuration file /usr/local/etc/raddb/policy.conf including files in directory /usr/local/etc/raddb/sites-enabled/ including configuration file /usr/local/etc/raddb/sites-enabled/control-socket including configuration file /usr/local/etc/raddb/sites-enabled/default including configuration file /usr/local/etc/raddb/sites-enabled/inner-tunnel main { user = "freeradius" group = "freeradius" allow_core_dumps = no } including dictionary file /usr/local/etc/raddb/dictionary main { name = "radiusd" prefix = "/usr/local" localstatedir = "/var" sbindir = "/usr/local/sbin" logdir = "/var/log/radius" run_dir = "/var/run/radiusd" libdir = "/usr/local/lib/freeradius-2.2.0" radacctdir = "/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/var/run/radiusd/radiusd.pid" checkrad = "/usr/local/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = no auth_badpass = no auth_goodpass = no } security { max_attributes = 200 reject_delay = 1 status_server = yes allow_vulnerable_openssl = no } } radiusd: #### Loading Realms and Home Servers #### proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 require_message_authenticator = yes zombie_period = 40 status_check = "status-server" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 coa { irt = 2 mrt = 16 mrc = 5 mrd = 30 } } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "Radius@dm1n" nastype = "other" } client 172.30.0.250 { require_message_authenticator = no secret = "Radius@dm1n" shortname = "Wireless_ap1" nastype = "other" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating module "exec" from file /usr/local/etc/raddb/modules/exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating module "expr" from file /usr/local/etc/raddb/modules/expr Module: Linked to module rlm_expiration Module: Instantiating module "expiration" from file /usr/local/etc/raddb/modules/expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating module "logintime" from file /usr/local/etc/raddb/modules/logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server { # from file e modules { Module: Creating Auth-Type = digest Module: Creating Post-Auth-Type = REJECT Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating module "pap" from file /usr/local/etc/raddb/modules/pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating module "chap" from file /usr/local/etc/raddb/modules/chap Module: Linked to module rlm_mschap Module: Instantiating module "mschap" from file /usr/local/etc/raddb/modules/mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no allow_retry = yes } Module: Linked to module rlm_digest Module: Instantiating module "digest" from file /usr/local/etc/raddb/modules/digest Module: Linked to module rlm_unix Module: Instantiating module "unix" from file /usr/local/etc/raddb/modules/unix unix { radwtmp = "/var/log/radius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating module "eap" from file /usr/local/etc/raddb/eap.conf eap { default_eap_type = "tls" timer_expire = 60 ignore_unknown_eap_types = yes cisco_accounting_username_bug = no max_sessions = 4096 } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_tls Module: Instantiating eap-tls tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 CA_path = "/etc/wireless" pem_file_type = yes private_key_file = "/etc/wireless/server_key.pem" certificate_file = "/etc/wireless/server_cert.pem" CA_file = "/etc/wireless/cacert.pem" private_key_password = "Radius@dm1n" dh_file = "/etc/wireless/dh" random_file = "/etc/wireless/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/usr/local/etc/raddb/certs/bootstrap" ecdh_curve = "prime256v1" cache { enable = no lifetime = 24 max_entries = 255 } verify { } ocsp { enable = no override_cert_url = yes url = "http://127.0.0.1/ocsp/" use_nonce = yes timeout = 0 softfail = no } } Module: Linked to sub-module rlm_eap_ttls Module: Instantiating eap-ttls ttls { default_eap_type = "md5" copy_request_to_tunnel = no use_tunneled_reply = no virtual_server = "inner-tunnel" include_length = yes } Module: Linked to sub-module rlm_eap_peap Module: Instantiating eap-peap peap { default_eap_type = "mschapv2" copy_request_to_tunnel = no use_tunneled_reply = no proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" soh = no } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no send_error = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating module "preprocess" from file /usr/local/etc/raddb/modules/preprocess preprocess { huntgroups = "/usr/local/etc/raddb/huntgroups" hints = "/usr/local/etc/raddb/hints" with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = no with_alvarion_vsa_hack = no } reading pairlist file /usr/local/etc/raddb/huntgroups reading pairlist file /usr/local/etc/raddb/hints Module: Linked to module rlm_realm Module: Instantiating module "suffix" from file /usr/local/etc/raddb/modules/realm realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating module "files" from file /usr/local/etc/raddb/modules/files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } reading pairlist file /usr/local/etc/raddb/users reading pairlist file /usr/local/etc/raddb/acct_users reading pairlist file /usr/local/etc/raddb/preproxy_users Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating module "acct_unique" from file /usr/local/etc/raddb/modules/acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, NAS-Identifier, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating module "detail" from file /usr/local/etc/raddb/modules/detail detail { detailfile = "/var/log/radius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Linked to module rlm_attr_filter Module: Instantiating module "attr_filter.accounting_response" from file /usr/local/etc/raddb/modules/attr_filter attr_filter attr_filter.accounting_response { attrsfile = "/usr/local/etc/raddb/attrs.accounting_response" key = "%{User-Name}" relaxed = no } reading pairlist file /usr/local/etc/raddb/attrs.accounting_response Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating module "radutmp" from file /usr/local/etc/raddb/modules/radutmp radutmp { filename = "/var/log/radius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Instantiating module "attr_filter.access_reject" from file /usr/local/etc/raddb/modules/attr_filter attr_filter attr_filter.access_reject { attrsfile = "/usr/local/etc/raddb/attrs.access_reject" key = "%{User-Name}" relaxed = no } reading pairlist file /usr/local/etc/raddb/attrs.access_reject } # modules } # server server inner-tunnel { # from file /usr/local/etc/raddb/sites-enabled/inner-tunnel modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Checking session {...} for more modules to load Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load } # modules } # server radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } listen { type = "control" listen { socket = "/var/run/radiusd/radiusd.sock" } } listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 } ... adding new socket proxy address * port 16653 Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /var/run/radiusd/radiusd.sock Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 172.30.0.250 port 32769, id=164, length=230 Acct-Session-Id = "15cc7112-00000075" NAS-Port = 118 NAS-Port-Type = Wireless-802.11 NAS-Identifier = "Wireless_ap1" NAS-IP-Address = 172.30.0.250 Framed-MTU = 1496 User-Name = "cgc" Calling-Station-Id = "00216a987bda" Called-Station-Id = "2880230d211c" Service-Type = Framed-User EAP-Message = 0x027a000801636763 Colubris-AVPair = "ssid=ssmic-new" Colubris-AVPair = "vsc-unique-id=1" Colubris-AVPair = "phytype=IEEE802dot11 " Colubris-Attr-250 = 0x00000000 Colubris-Attr-249 = 0x00000000 Message-Authenticator = 0x20a2e8eb7def88937a7d9d28ab63b966 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "cgc", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 122 length 8 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] = updated [files] users: Matched entry cgc at line 16 ++[files] = ok ++[expiration] = noop ++[logintime] = noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] = noop +} # group authorize = updated Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] EAP Identity [eap] processing type tls [tls] Requiring client certificate [tls] Initiate [tls] Start returned 1 ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 164 to 172.30.0.250 port 32769 Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "290" EAP-Message = 0x017b00060d20 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x1d02d5a51d79d8dae0925046e4e37e98 Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 172.30.0.250 port 32769, id=1, length=230 Acct-Session-Id = "daf79885-00000076" NAS-Port = 119 NAS-Port-Type = Wireless-802.11 NAS-Identifier = "Wireless_ap1" NAS-IP-Address = 172.30.0.250 Framed-MTU = 1496 User-Name = "cgc" Calling-Station-Id = "00216a987bda" Called-Station-Id = "2880230d211c" Service-Type = Framed-User EAP-Message = 0x027c000801636763 Colubris-AVPair = "ssid=ssmic-new" Colubris-AVPair = "vsc-unique-id=1" Colubris-AVPair = "phytype=IEEE802dot11 " Colubris-Attr-250 = 0x00000000 Colubris-Attr-249 = 0x00000000 Message-Authenticator = 0x137141fe627b78ed95690c6f8f786309 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "cgc", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 124 length 8 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] = updated [files] users: Matched entry cgc at line 16 ++[files] = ok ++[expiration] = noop ++[logintime] = noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] = noop +} # group authorize = updated Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] EAP Identity [eap] processing type tls [tls] Requiring client certificate [tls] Initiate [tls] Start returned 1 ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 1 to 172.30.0.250 port 32769 Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "290" EAP-Message = 0x017d00060d20 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xc389a266c3f4af0574a4f2011c6a5ca9 Finished request 1. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 172.30.0.250 port 32769, id=72, length=367 Acct-Session-Id = "daf79885-00000076" NAS-Port = 119 NAS-Port-Type = Wireless-802.11 NAS-Identifier = "Wireless_ap1" NAS-IP-Address = 172.30.0.250 Framed-MTU = 1496 User-Name = "cgc" Calling-Station-Id = "00216a987bda" Called-Station-Id = "2880230d211c" Service-Type = Framed-User EAP-Message = 0x027d00690d800000005f160301005a01000056030153d1046734f9e83fe1f74b6bd0da8c9480408c0fb7d26fec9aaaa3cc6520bab8000018002f00350005000ac013c014c009c00a003200380013000401000015ff01000100000a0006000400170018000b00020100 State = 0xc389a266c3f4af0574a4f2011c6a5ca9 Colubris-AVPair = "ssid=ssmic-new" Colubris-AVPair = "incoming-vlan-id=290" Colubris-AVPair = "vsc-unique-id=1" Colubris-AVPair = "phytype=IEEE802dot11 " Colubris-Attr-250 = 0x00000000 Colubris-Attr-249 = 0x00000000 Message-Authenticator = 0x86caf455eff5f43a9a1ea173045901e9 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "cgc", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 125 length 105 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] = updated [files] users: Matched entry cgc at line 16 ++[files] = ok ++[expiration] = noop ++[logintime] = noop ++[pap] = noop +} # group authorize = updated Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/tls [eap] processing type tls [tls] Authenticate [tls] processing EAP-TLS TLS Length 95 [tls] Length Included [tls] eaptls_verify returned 11 [tls] (other): before/accept initialization [tls] TLS_accept: before/accept initialization [tls] <<< TLS 1.0 Handshake [length 005a], ClientHello [tls] TLS_accept: SSLv3 read client hello A [tls] >>> TLS 1.0 Handshake [length 0031], ServerHello [tls] TLS_accept: SSLv3 write server hello A [tls] >>> TLS 1.0 Handshake [length 039e], Certificate [tls] TLS_accept: SSLv3 write certificate A [tls] >>> TLS 1.0 Handshake [length 008d], CertificateRequest [tls] TLS_accept: SSLv3 write certificate request A [tls] TLS_accept: SSLv3 flush data [tls] TLS_accept: Need to read more data: SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode [tls] eaptls_process returned 13 ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 72 to 172.30.0.250 port 32769 Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "290" EAP-Message = 0x017e04000dc00000046b16030100310200002d0301f61a02b4c5da13d072f5061976dac50c509809533d3af20e15eb53fe9bfcaf0c00002f000005ff01000100160301039e0b00039a0003970003943082039030820278a003020102020900a2ed549b6711ef20300d06092a864886f70d0101050500307b310b30090603550406130243413110300e06035504080c074f6e746172696f312a3028060355040a0c215361756c7420537465204d6172696520496e6e6f766174696f6e2043656e747265310e300c06035504030c0573736d6963311e301c06092a864886f70d010901160f67636f6f6b4073736d69632e636f6d301e170d313430373232 EAP-Message = 0x3137343435335a170d3139303732313137343435335a307b310b30090603550406130243413110300e06035504080c074f6e746172696f312a3028060355040a0c215361756c7420537465204d6172696520496e6e6f766174696f6e2043656e747265310e300c06035504030c0573736d6963311e301c06092a864886f70d010901160f67636f6f6b4073736d69632e636f6d30820122300d06092a864886f70d01010105000382010f003082010a028201010099edf0f438c5962febd166f3c1f4ceec2d64137dd432be8b99096de8ea93405dd5c57be12006ae1657a3aba0bed52a1cf53b3d9f7f78726cb807c5717dc8d797698a4a48f281112954 EAP-Message = 0x7f247a0dc8a89d2da4c15ffae37f67cf8b7a16a23a9a1a6a323ad9ea7264a6d024d87727054ffe687775aa010bcf5e6b46fa62d428d2da0b9000d59fe25b62157df0fa1fd08313b713f6ed5b8e64976bb0631d04f865a5554a24608f3e497fc2b0e33ab773c79e9b8fd1e1e41d269d53ee572fdce3f3bebe836fcfc0abdc6e8acdb06e70bf8fbb784cd908fa92adfb3f6f82cb23368518d0fcfe5414d56e2ef1b08dbe1d4f0b9ac9b3b7dd469270a17f52ff2a88a6b1330203010001a317301530130603551d25040c300a06082b06010505070301300d06092a864886f70d0101050500038201010048c4edbf95dfdb4b3dcc3842062c9151e7dc6065 EAP-Message = 0x350926303eae92459a61af5d5a995117b6362d08d6330d769486728e1bda4e6f37c9dc2039c83432a991f44ce814d510afc0794c43a75798e81223c444e7a7ba78fff51511726550b080fb2d2f85a5cfb299f343ab07763b91df7caf894d74c9817d28217d046a421b4e01541f98a3c5d346262b69ca4d64cac004c45b4525e9badc3d0418059c8788d1951c3d5a1c84ae5e6f33f1346868086db7256d8b204a75f2b527938f02562d00f9865de0b3d33cfdd3d7fba163db85cf8054c2b15b7346e7aac47b1e290b3f7190eecfcb91c5595c8178c27a401af3d3477b4a67210bb083981f6f1d32acbbe42913160301008d0d00008503010240007f007d EAP-Message = 0x307b310b3009060355040613 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xc389a266c2f7af0574a4f2011c6a5ca9 Finished request 2. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 172.30.0.250 port 32769, id=91, length=268 Acct-Session-Id = "daf79885-00000076" NAS-Port = 119 NAS-Port-Type = Wireless-802.11 NAS-Identifier = "Wireless_ap1" NAS-IP-Address = 172.30.0.250 Framed-MTU = 1496 User-Name = "cgc" Calling-Station-Id = "00216a987bda" Called-Station-Id = "2880230d211c" Service-Type = Framed-User EAP-Message = 0x027e00060d00 State = 0xc389a266c2f7af0574a4f2011c6a5ca9 Colubris-AVPair = "ssid=ssmic-new" Colubris-AVPair = "incoming-vlan-id=290" Colubris-AVPair = "vsc-unique-id=1" Colubris-AVPair = "phytype=IEEE802dot11 " Colubris-Attr-250 = 0x00000000 Colubris-Attr-249 = 0x00000000 Message-Authenticator = 0x83f0b0d687466c31929730e8175424d7 # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +group authorize { ++[preprocess] = ok ++[chap] = noop ++[mschap] = noop ++[digest] = noop [suffix] No '@' in User-Name = "cgc", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] = noop [eap] EAP packet type response id 126 length 6 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] = updated [files] users: Matched entry cgc at line 16 ++[files] = ok ++[expiration] = noop ++[logintime] = noop ++[pap] = noop +} # group authorize = updated Found Auth-Type = EAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +group authenticate { [eap] Request found, released from the list [eap] EAP/tls [eap] processing type tls [tls] Authenticate [tls] processing EAP-TLS [tls] Received TLS ACK [tls] ACK handshake fragment handler [tls] eaptls_verify returned 1 [tls] eaptls_process returned 13 ++[eap] = handled +} # group authenticate = handled Sending Access-Challenge of id 91 to 172.30.0.250 port 32769 Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "290" EAP-Message = 0x017f007f0d800000046b0243413110300e06035504080c074f6e746172696f312a3028060355040a0c215361756c7420537465204d6172696520496e6e6f766174696f6e2043656e747265310e300c06035504030c0573736d6963311e301c06092a864886f70d010901160f67636f6f6b4073736d69632e636f6d0e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xc389a266c1f6af0574a4f2011c6a5ca9 Finished request 3. Going to the next request Waking up in 4.9 seconds. Cleaning up request 0 ID 164 with timestamp +12 WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: !! EAP session for state 0x1d02d5a51d79d8da did not finish! WARNING: !! Please read http://wiki.freeradius.org/guide/Certificate_Compatibility WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Cleaning up request 1 ID 1 with timestamp +12 Cleaning up request 2 ID 72 with timestamp +12 Cleaning up request 3 ID 91 with timestamp +12 WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: !! EAP session for state 0xc389a266c1f6af05 did not finish! WARNING: !! Please read http://wiki.freeradius.org/guide/Certificate_Compatibility WARNING: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Ready to process requests. Gordon Cook -----Original Message----- From: freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org [mailto:freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Wednesday, July 23, 2014 9:03 PM To: FreeRadius users mailing list Subject: Re: HP M200 certificate authentication fails Gordon Cook wrote:

I have both access points using the same freeRadius2 server which is running FreeBSD 9

The client can authenticate using the certificate through the cisco.

The client can authenticate using PAP through the HP

What does that mean?

The client cannot authenticate using the certificate through the HP. ... I have looked through everything I can find and I can’t seem to get it to work.

Post the full debug log. Maybe there's something in that which will help. But nearly all of the time... the problem is in the end-user system or in the access point. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

What I mean by the configuration needs to adjusted. The client using the same credentials can authenticate through the cisco ap and not the HP AP. There is very few settings in the HP that can be set for the radius server. So what I am thinking is something needs to be changed, removed or added to the configuration files on the radius server to be able to work with the HP AP. I just can't find any documentation on using the HP AP with freeRadius although the specs for the AP says it should work. Gordon Cook Network Administrator Sault Ste Marie Innovation Centre Work: 705-942-6938 x3042 Cell:     705-971-3852 -----Original Message----- From: freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org [mailto:freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Friday, July 25, 2014 8:28 AM To: FreeRadius users mailing list Subject: Re: HP M200 certificate authentication fails Gordon Cook wrote:

I am fairly new at this. I am leaning more towards a configuration issue in freeradius.

When FreeRADIUS says this:

WARNING: !! EAP session for state 0xc389a266c1f6af05 did not finish!

It's because the supplicant (and/or the AP) just stopped doing EAP. There is little you can do to FreeRADIUS to make the supplicant continue, when it's decided to stop.

The configuration needs to be adjusted to handle some difference in the HP AP vs the Cisco AP.

That sounds magical. Perhaps you could explain exactly *what* you adjusted, and why? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

I apologize if I was not clear. I am not trying to be difficult. I had already gone through the website indicated in the response with no luck. I will try to be a lot clearer. I have a radius server running freebsd 9 and freeradius2 (radius1). I used openssl on the server to generate certificates to be used in windows called cacert and cgc. I then installed the certificates on all our windows laptops. I am using laptop1 for testing Originally I had a CISCO AP connected to the radius server and everything works. (wireless_ap1) We needed to upgrade our wireless and purchased an HP AP. (wireless_ap2) So Laptop1 <---------> wireless_ap1 <-----------> radius1 this works using the above certificates Laptop1 <---------> wireless_ap2 <-----------> radius1 this does not work using the above certificates Laptop1 <---------> wireless_ap2 <-----------> radius1 using EAP-TLS and PAP works. This is where I am confused. If it is the supplicant why would it work with wireless_ap1 and not wireless_ap2 using the same settings and credentials. This is what leads me to believe that the HP is doing something different with the packets than the the CISCO is and there is a setting in one of the config files on the radius server that needs to set or adjusted to handle the difference. I am currently running the eaphost trace again to see if there is something I missed. I hope this makes more sense. Gordon Cook Network Administrator Sault Ste Marie Innovation Centre Work: 705-942-6938 x3042 Cell:     705-971-3852 -----Original Message----- From: freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org [mailto:freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Friday, July 25, 2014 8:56 AM To: FreeRadius users mailing list Subject: Re: HP M200 certificate authentication fails Gordon Cook wrote:

What I mean by the configuration needs to adjusted.

The client using the same credentials can authenticate through the cisco ap and not the HP AP.

OK... that's what you said already, but sure.

There is very few settings in the HP that can be set for the radius server.

IP address and shared secret, usually.

So what I am thinking is something needs to be changed, removed or added to the configuration files on the radius server to be able to work with the HP AP.

Really? That is a horribly vague statement. And it doesn't agree with what you said earlier. You said previously you HAD changed something. I asked you what you had changed. Your reply now is you think something needs to be changed. I'm trying to help you, and you're giving vague and inconsistent answers. This is not just annoying, you're making it impossible for me to help you.

I just can't find any documentation on using the HP AP with freeRadius although the specs for the AP says it should work.

There is likely no documentation on "HP and FR". Because there doesn't need to be. HP documents how to configure the AP for RADIUS. FreeRADIUS documents how to add a client. That's it. The vendor doesn't matter. In any case, the problem is likely not with the AP. The supplicant is stopping the EAP conversation. As I said before. Fix the supplicant. The web page in the debug output describes the common problems, and how to fix them. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Thanks for the help. I do really appreciate it. Just to be clear. I am not blaming freeRadius. If anything I agree it is the AP. I just wanted to make sure that there wasn't a setting or something somewhere that would allow the two to talk to each other. Again being new to freeRadius I was not sure so wanted to ask. One of the reasons I picked HP was to try and stay with standards based equipment. I have a number of switches from HP and they all work great. This is the first real issue I have had with them. Gordon Cook Network Administrator Sault Ste Marie Innovation Centre Work: 705-942-6938 x3042 Cell:     705-971-3852 -----Original Message----- From: freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org [mailto:freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Friday, July 25, 2014 2:35 PM To: FreeRadius users mailing list Subject: Re: HP M200 certificate authentication fails Gordon Cook wrote:

I then installed the certificates on all our windows laptops. I am using laptop1 for testing

Originally I had a CISCO AP connected to the radius server and everything works. (wireless_ap1)

Then all of the things involved are proven to work.

We needed to upgrade our wireless and purchased an HP AP. (wireless_ap2)

So

Laptop1 <---------> wireless_ap1 <-----------> radius1 this works using the above certificates Laptop1 <---------> wireless_ap2 <-----------> radius1 this does not work using the above certificates Laptop1 <---------> wireless_ap2 <-----------> radius1 using EAP-TLS and PAP works.

Then the problem is the HP AP. You've already proven that FreeRADIUS works. When you change ONLY the AP, and EAP doesn't work... blame the AP.

This is where I am confused. If it is the supplicant why would it work with wireless_ap1 and not wireless_ap2 using the same settings and credentials. This is what leads me to believe that the HP is doing something different with the packets than the the CISCO is and there is a setting in one of the config files on the radius server that needs to set or adjusted to handle the difference.

That is entirely the wrong approach. "Changing something" is pretty much magical thinking. Instead, find the *cause* of the problem, and fix *that*. There is no magical setting in FreeRADIUS saying "work with HP". The default configuration should work with every standards-compliant RADIUS client.

I am currently running the eaphost trace again to see if there is something I missed.

Stop blaming FreeRADIUS. Throw the HP AP in the garbage, and buy an AP that works. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

I was just trying to say thank you and clarify what I was asking. I have the answer. Gordon Cook Network Administrator Sault Ste Marie Innovation Centre Work: 705-942-6938 x3042 Cell:     705-971-3852 -----Original Message----- From: freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org [mailto:freeradius-users-bounces+gcook=ssmic.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Friday, July 25, 2014 3:18 PM To: FreeRadius users mailing list Subject: Re: HP M200 certificate authentication fails Gordon Cook wrote:

Just to be clear. I am not blaming freeRadius. If anything I agree it is the AP.

You're asking what setting to change on FreeRADIUS.

I just wanted to make sure that there wasn't a setting or something somewhere that would allow the two to talk to each other.

I have already said that FreeRADIUS works with standards-compliant systems. Multiple times, IIRC. Asking the same question repeatedly is not helpful.

Again being new to freeRadius I was not sure so wanted to ask. One of the reasons I picked HP was to try and stay with standards based equipment. I have a number of switches from HP and they all work great. This is the first real issue I have had with them.

<shrug> If the setup works with the Cisco AP and not the HP one, then the HP equipment is at fault. Go ask HP how to make their equipment work with standards-compliant RADIUS servers. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

...

Again being new to freeRadius I was not sure so wanted to ask. One of the reasons I picked HP was to try and stay with standards based equipment. I have a number of switches from HP and they all work great. This is the first real issue I have had with them.

<shrug> If the setup works with the Cisco AP and not the HP one, then the HP equipment is at fault. Go ask HP how to make their equipment work with standards-compliant RADIUS servers.

Shout, loudly, repeatedly and often. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2