AD Authentication + radius + foundryAP
I followed the guide that was linked from http://wiki.freeradius.org/FreeRADIUS_Active_Directory_Integration_HOWTO because I'm running v2 of the radius server. After going to the guide I was still unable to authenticate to the AD though the wireless AP controller. This radius is running on Ubuntu 10.04 and is supposed to replace a free radius controller running v1 on Gentoo. The one running on Gentoo is working for the most part, just dies from time to time. So we are just upgrading and refreshing. For some reason I have not been able to get the radius server to do what I need it to do and that is work with MS-CHAP so that it will authenticate to AD. FreeRADIUS Version 2.1.8, for host i486-pc-linux-gnu, built on Jan 5 2010 at 02:49:11 Copyright (C) 1999-2009 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 v2. Starting - reading configuration files ... including configuration file /etc/freeradius/radiusd.conf including configuration file /etc/freeradius/proxy.conf including configuration file /etc/freeradius/clients.conf including files in directory /etc/freeradius/modules/ including configuration file /etc/freeradius/modules/cui including configuration file /etc/freeradius/modules/detail.log including configuration file /etc/freeradius/modules/mac2ip including configuration file /etc/freeradius/modules/attr_rewrite including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login including configuration file /etc/freeradius/modules/perl including configuration file /etc/freeradius/modules/smbpasswd including configuration file /etc/freeradius/modules/inner-eap including configuration file /etc/freeradius/modules/counter including configuration file /etc/freeradius/modules/echo including configuration file /etc/freeradius/modules/exec including configuration file /etc/freeradius/modules/acct_unique including configuration file /etc/freeradius/modules/radutmp including configuration file /etc/freeradius/modules/chap including configuration file /etc/freeradius/modules/wimax including configuration file /etc/freeradius/modules/sradutmp including configuration file /etc/freeradius/modules/attr_filter including configuration file /etc/freeradius/modules/ntlm_auth including configuration file /etc/freeradius/modules/detail.example.com including configuration file /etc/freeradius/modules/krb5 including configuration file /etc/freeradius/modules/detail including configuration file /etc/freeradius/modules/expiration including configuration file /etc/freeradius/modules/unix including configuration file /etc/freeradius/modules/logintime including configuration file /etc/freeradius/modules/linelog including configuration file /etc/freeradius/modules/sql_log including configuration file /etc/freeradius/modules/ldap including configuration file /etc/freeradius/modules/expr including configuration file /etc/freeradius/modules/pam including configuration file /etc/freeradius/modules/policy including configuration file /etc/freeradius/modules/files including configuration file /etc/freeradius/modules/realm including configuration file /etc/freeradius/modules/otp including configuration file /etc/freeradius/modules/smsotp including configuration file /etc/freeradius/modules/digest including configuration file /etc/freeradius/modules/mschap including configuration file /etc/freeradius/modules/etc_group including configuration file /etc/freeradius/modules/pap including configuration file /etc/freeradius/modules/mac2vlan including configuration file /etc/freeradius/modules/passwd including configuration file /etc/freeradius/modules/ippool including configuration file /etc/freeradius/modules/always including configuration file /etc/freeradius/modules/preprocess including configuration file /etc/freeradius/modules/checkval including configuration file /etc/freeradius/eap.conf including configuration file /etc/freeradius/policy.conf including files in directory /etc/freeradius/sites-enabled/ including configuration file /etc/freeradius/sites-enabled/inner-tunnel including configuration file /etc/freeradius/sites-enabled/default main { user = "freerad" group = "freerad" allow_core_dumps = no } including dictionary file /etc/freeradius/dictionary main { prefix = "/usr" localstatedir = "/var" logdir = "/var/log/freeradius" libdir = "/usr/lib/freeradius" radacctdir = "/var/log/freeradius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/var/run/rad2/rad2.pid" checkrad = "/usr/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 } } 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 = no 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 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 = "testing123" nastype = "other" } client foundryap { ipaddr = 192.168.103.10 require_message_authenticator = no secret = "testing123" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating expr Module: Linked to module rlm_expiration Module: Instantiating expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating chap Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = yes require_strong = yes with_ntdomain_hack = yes ntlm_auth = "/usr/bin/ntlm_auth --request-nt-key --username=%{mschap:User-Name:-None} --domain=%{%{mschap:NT-Domain}:-ATL.EXAMPLE.COM} --challenge=%{mschap:Challenge:-00} --nt-response=%{mschap:NT-Response:-00} --require-membership-of=ATL+wifi-secure" } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "peap" timer_expire = 60 ignore_unknown_eap_types = no 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_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } 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 pem_file_type = yes private_key_file = "/etc/freeradius/certs/server.key" certificate_file = "/etc/freeradius/certs/server.pem" CA_file = "/etc/freeradius/certs/ca.pem" private_key_password = "whatever" dh_file = "/etc/freeradius/certs/dh" random_file = "/etc/freeradius/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/etc/freeradius/certs/bootstrap" cache { enable = no lifetime = 24 max_entries = 255 } } 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 = yes use_tunneled_reply = yes proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating preprocess preprocess { huntgroups = "/etc/freeradius/huntgroups" hints = "/etc/freeradius/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 } Module: Linked to module rlm_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = yes } Module: Instantiating ntdomain realm ntdomain { format = "prefix" delimiter = "\" ignore_default = no ignore_null = yes } Module: Linked to module rlm_files Module: Instantiating files files { usersfile = "/etc/freeradius/users" acctusersfile = "/etc/freeradius/acct_users" preproxy_usersfile = "/etc/freeradius/preproxy_users" compat = "no" } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/var/log/freeradius/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: Linked to module rlm_attr_filter Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/etc/freeradius/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pam Module: Instantiating pam pam { pam_auth = "radiusd" } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating auth_log detail auth_log { detailfile = "/var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Instantiating detail detail { detailfile = "/var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/var/log/freeradius/radwtmp" } Module: Instantiating attr_filter.accounting_response attr_filter attr_filter.accounting_response { attrsfile = "/etc/freeradius/attrs.accounting_response" key = "%{User-Name}" } 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 = 1812 } listen { type = "acct" ipaddr = * port = 1813 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 192.168.103.10 port 32890, id=83, length=158 User-Name = "ATL\\user" NAS-IP-Address = 192.168.103.10 NAS-Port = 6145 Called-Station-Id = "00-90-0B-0A-81-96:radtest" Calling-Station-Id = "00-26-C7-6F-FF-64" Framed-MTU = 900 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 802.11g" EAP-Message = 0x020100110141544c5c7069706b696e5f6d Message-Authenticator = 0xf18704d104d0322078509df754b74003 +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] expand: %t -> Mon May 16 15:28:41 2011 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [ntdomain] Looking up realm "ATL" for User-Name = "ATL\user" [ntdomain] No such realm "ATL" ++[ntdomain] returns noop [eap] EAP packet type response id 1 length 17 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 83 to 192.168.103.10 port 32890 EAP-Message = 0x010200061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x880bd1788809c8ca896d5b23fad51f0e Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.103.10 port 32890, id=84, length=296 User-Name = "ATL\\user" NAS-IP-Address = 192.168.103.10 NAS-Port = 6145 Called-Station-Id = "00-90-0B-0A-81-96:radtest" Calling-Station-Id = "00-26-C7-6F-FF-64" Framed-MTU = 900 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 802.11g" EAP-Message = 0x0202008919800000007f160301007a0100007603014dd17b10f62607c3d64b96e5d9505d0180e01cb5bd8d86d43136a93b0805404a209e83189d67298bccdaa3ebde678430bac0f21f8fc6ae3786aa1efaadf9822f110018002f00350005000ac013c014c009c00a003200380013000401000015ff01000100000a0006000400170018000b00020100 State = 0x880bd1788809c8ca896d5b23fad51f0e Message-Authenticator = 0x013e8d6954e859caabbe5767cb033984 +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] expand: %t -> Mon May 16 15:28:41 2011 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [ntdomain] Looking up realm "ATL" for User-Name = "ATL\user" [ntdomain] No such realm "ATL" ++[ntdomain] returns noop [eap] EAP packet type response id 2 length 137 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS TLS Length 127 [peap] Length Included [peap] eaptls_verify returned 11 [peap] (other): before/accept initialization [peap] TLS_accept: before/accept initialization [peap] <<< TLS 1.0 Handshake [length 007a], ClientHello [peap] TLS_accept: SSLv3 read client hello A [peap] >>> TLS 1.0 Handshake [length 0031], ServerHello [peap] TLS_accept: SSLv3 write server hello A [peap] >>> TLS 1.0 Handshake [length 01c3], Certificate [peap] TLS_accept: SSLv3 write certificate A [peap] >>> TLS 1.0 Handshake [length 0004], ServerHelloDone [peap] TLS_accept: SSLv3 write server done A [peap] TLS_accept: SSLv3 flush data [peap] TLS_accept: Need to read more data: SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 84 to 192.168.103.10 port 32890 EAP-Message = 0x0103020d190016030100310200002d03014dd17ae914ae79001cc53a10e9b7b1412d0c045d04221287bb1e07feb8d1656a00002f000005ff0100010016030101c30b0001bf0001bc0001b9308201b53082011e020900e959fd943dab9ed7300d06092a864886f70d0101050500301f311d301b06035504031314726164322e61746c2e616972327765622e636f6d301e170d3131303531323133313131395a170d3231303530393133313131395a301f311d301b06035504031314726164322e61746c2e616972327765622e636f6d30819f300d06092a864886f70d010101050003818d0030818902818100cdc310525259fed19d90dee18c44f2f8d8 EAP-Message = 0x6656c42938adcb2543a6f9b2756cc72ea5c7a23101ca2a9c20ffbb66fcde9b418d01310914e7a4bc382d33a38efcf1e58eb1d4bd669914cac1703da10b0c06cf6142b05887f4165ad77c1a2ca5fe53d154000a14db83505be59ab4fab339755fb0fbfb2392d92242d6996819e0527b0203010001300d06092a864886f70d01010505000381810080ec9a66411b895c708ae2ed324bd3e4757c052fc199bc3049f95dcca2f4817c3ae94691c13bc8c7101456d5ccf9a1d5809d20dad828fe922f315fa5c01a11598f616c12e54bd95f3198f87ee8c02130d0f23ebd2ca008f7ef0c82b583de3b995477b59731c4497d56c8943af00aee48efc7ad76276e EAP-Message = 0x3336e1804d16833ff8b416030100040e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x880bd1788908c8ca896d5b23fad51f0e Finished request 1. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.103.10 port 32890, id=85, length=165 User-Name = "ATL\\user" NAS-IP-Address = 192.168.103.10 NAS-Port = 6145 Called-Station-Id = "00-90-0B-0A-81-96:radtest" Calling-Station-Id = "00-26-C7-6F-FF-64" Framed-MTU = 900 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 802.11g" EAP-Message = 0x020300061900 State = 0x880bd1788908c8ca896d5b23fad51f0e Message-Authenticator = 0xada9d2724210731e12da1c6d2f3f0926 +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] expand: %t -> Mon May 16 15:28:41 2011 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [ntdomain] Looking up realm "ATL" for User-Name = "ATL\user" [ntdomain] No such realm "ATL" ++[ntdomain] returns noop [eap] EAP packet type response id 3 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 85 to 192.168.103.10 port 32890 EAP-Message = 0x010400061900 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x880bd1788a0fc8ca896d5b23fad51f0e Finished request 2. Going to the next request Waking up in 4.9 seconds. Invalid packet code 4 sent to authentication port from client foundryap port 32770 : IGNORED Waking up in 4.3 seconds. Invalid packet code 4 sent to authentication port from client foundryap port 32770 : IGNORED Waking up in 3.8 seconds. Invalid packet code 4 sent to authentication port from client foundryap port 32770 : IGNORED Waking up in 3.6 seconds. rad_recv: Access-Request packet from host 192.168.103.10 port 32890, id=88, length=158 User-Name = "ATL\\user" NAS-IP-Address = 192.168.103.10 NAS-Port = 6145 Called-Station-Id = "00-90-0B-0A-81-96:radtest" Calling-Station-Id = "00-26-C7-6F-FF-64" Framed-MTU = 900 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 802.11g" EAP-Message = 0x020100110141544c5c7069706b696e5f6d Message-Authenticator = 0x26e0f9d13ab7787bf244db77d342326d +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] expand: %t -> Mon May 16 15:28:43 2011 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [ntdomain] Looking up realm "ATL" for User-Name = "ATL\user" [ntdomain] No such realm "ATL" ++[ntdomain] returns noop [eap] EAP packet type response id 1 length 17 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 88 to 192.168.103.10 port 32890 EAP-Message = 0x010200061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x457c467c457e5f9ed7afaf432a46c660 Finished request 3. Going to the next request Waking up in 3.6 seconds. rad_recv: Access-Request packet from host 192.168.103.10 port 32890, id=89, length=165 User-Name = "ATL\\user" NAS-IP-Address = 192.168.103.10 NAS-Port = 6145 Called-Station-Id = "00-90-0B-0A-81-96:radtest" Calling-Station-Id = "00-26-C7-6F-FF-64" Framed-MTU = 900 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 802.11g" EAP-Message = 0x020200060311 State = 0x457c467c457e5f9ed7afaf432a46c660 Message-Authenticator = 0xad2eebc61c93e9f242fc51bf2dafe2c0 +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] expand: %t -> Mon May 16 15:28:43 2011 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [ntdomain] Looking up realm "ATL" for User-Name = "ATL\user" [ntdomain] No such realm "ATL" ++[ntdomain] returns noop [eap] EAP packet type response id 2 length 6 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP NAK [eap] EAP-NAK asked for EAP-Type/leap [eap] processing type leap rlm_eap_leap: Stage 2 rlm_eap_leap: Issuing AP Challenge rlm_eap_leap: Successfully initiated ++[eap] returns handled Sending Access-Challenge of id 89 to 192.168.103.10 port 32890 EAP-Message = 0x0103001c11010008765dcad2513ca14941544c5c7069706b696e5f6d Message-Authenticator = 0x00000000000000000000000000000000 State = 0x457c467c447f579ed7afaf432a46c660 Finished request 4. Going to the next request Waking up in 3.6 seconds. rad_recv: Access-Request packet from host 192.168.103.10 port 32890, id=90, length=203 User-Name = "ATL\\user" NAS-IP-Address = 192.168.103.10 NAS-Port = 6145 Called-Station-Id = "00-90-0B-0A-81-96:radtest" Calling-Station-Id = "00-26-C7-6F-FF-64" Framed-MTU = 900 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 802.11g" EAP-Message = 0x0203002c1101001887b03ee7af25d8731fec4765958f0f4b0775fd12760ca7a341544c5c7069706b696e5f6d State = 0x457c467c447f579ed7afaf432a46c660 Message-Authenticator = 0xcc373dbaa966a554c5a5a842877f7fed +- entering group authorize {...} ++[preprocess] returns ok [auth_log] expand: /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] /var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/freeradius/radacct/192.168.103.10/auth-detail-20110516 [auth_log] expand: %t -> Mon May 16 15:28:43 2011 ++[auth_log] returns ok ++[chap] returns noop ++[mschap] returns noop [ntdomain] Looking up realm "ATL" for User-Name = "ATL\user" [ntdomain] No such realm "ATL" ++[ntdomain] returns noop [eap] EAP packet type response id 3 length 44 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/leap [eap] processing type leap rlm_eap_leap: No Cleartext-Password or NT-Password configured for this user [eap] Handler failed in EAP/leap [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> ATL\user attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 5 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 5 Sending Access-Reject of id 90 to 192.168.103.10 port 32890 EAP-Message = 0x04030004 Message-Authenticator = 0x00000000000000000000000000000000 Flame on! Seriously though.. I'm going to keep working at this, just didn't know if someone would be able to help me out. Thanks. Mark PIpkin Systems Administrator Air2Web Office: +1 404 942 5365 E-mail: mark.pipkin@air2web.com Mobilize your business. Find out how at www.air2web.com Follow us on Twitter @a2wmobile This message contains privileged and confidential information. If received in error, please delete immediately.
Mark Pipkin wrote:
I followed the guide that was linked from http://wiki.freeradius.org/FreeRADIUS_Active_Directory_Integration_HOWTO because I'm running v2 of the radius server.
After going to the guide I was still unable to authenticate to the AD though the wireless AP controller. This radius is running on Ubuntu 10.04 and is supposed to replace a free radius controller running v1 on Gentoo. The one running on Gentoo is working for the most part, just dies from time to time. So we are just upgrading and refreshing.
For some reason I have not been able to get the radius server to do what I need it to do and that is work with MS-CHAP so that it will authenticate to AD.
Post the debugging output into the form at: http://networkradius.com/freeradius.html And read the highlighted lines. It should be obvious what's going on. You need to tell the server how to authenticate the user. Also read my Active Directory guide at: http://deployingradius.com/documents/configuration/active_directory.html It contains detailed documentation and explanations for how to get this to work. Alan DeKok.
Post the debugging output into the form at:
And read the highlighted lines. It should be obvious what's going on.
Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/etc/freeradius/attrs.access_reject" was highlighted in read. To you it might be obvious what this means. To me, I don't really understand it, except that later one in the debug I get : Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> ATL\pipkin_m I don't know much about FreeRadius. I have never had to work with a radius server of any type before. I do apologize, but while this stuff might be obvious to someone that created it or works in radius servers every day of the week, I am not that person. So to me, the only obvious thing is that I get rejected at leap, while another radius server that is running FreeRadius 1.x on Getoo is working just find with mschapv2.
Also read my Active Directory guide at:
http://deployingradius.com/documents/configuration/active_directory.htm l
It contains detailed documentation and explanations for how to get this to work.
I did follow this how-to the first time around and it got me to this point. That is in my first statement in asking for help.
Mark Pipkin wrote:
was highlighted in read. To you it might be obvious what this means. To me, I don't really understand it, except that later one in the debug I get :
You're supposed to read the output. Only looking at *part* of it means you can only solve *part* of the problem. Here's the key pieces of your original post: ... pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/leap [eap] processing type leap rlm_eap_leap: No Cleartext-Password or NT-Password configured for this user ... What does that look like to you? Are the debug messages helpful? Do they accurately describe the problem, and give you hints for the solution?
I don't know much about FreeRadius. I have never had to work with a radius server of any type before. I do apologize, but while this stuff might be obvious to someone that created it or works in radius servers every day of the week, I am not that person. So to me, the only obvious thing is that I get rejected at leap, while another radius server that is running FreeRadius 1.x on Getoo is working just find with mschapv2.
The PC is choosing LEAP, not FreeRADIUS. Configure the PC to use LEAP, as was suggested in *another* response to your post. Alan DeKok.
What does that look like to you?
Looks like it is trying to use PAP to authenticate with. Though PAP is local only, at least from what I can tell, and there is no local user/pass for this account. Then it looks like it rolls to a EAP/leap authentication method. At this point it fails.
Are the debug messages helpful?
If I truly understood more, then I'm sure that they would be. That are not as helpful for me; I have a lack of understanding at this point in time.
Do they accurately describe the problem, and give you hints for the solution?
I just see the problem as not working. I don't understand why it didn't even attempt mschapv2 when eap default was set to peap and peap default was set to mschapv2.
I don't know much about FreeRadius. I have never had to work with a radius server of any type before. I do apologize, but while this stuff might be obvious to someone that created it or works in radius servers every day of the week, I am not that person. So to me, the only obvious thing is that I get rejected at leap, while another radius server that is running FreeRadius 1.x on Getoo is working just find with mschapv2.
The PC is choosing LEAP, not FreeRADIUS.
I'm using Win7. Are you telling me that the PC is the one that is picking the security for the radius and not the Foundry Wireless AP controller?
Configure the PC to use LEAP, as was suggested in *another* response to your post.
I read that post. I thought the he was referring to the Foundry AP controller. You just told me that it was the fault of the PC though. Mark Pipkin
Mark Pipkin wrote:
What does that look like to you?
Looks like it is trying to use PAP to authenticate with.
i.e. you haven't *read* the warning message. You just saw "pap" and "WARNING", and stopped there. To be excruciatingly simple: RADIUS servers authenticate users by KNOWING what the correct password is. If the server doesn't have a KNOWN GOOD password, it can't authenticate the user. The message says that there is no *KNOWN GOOD* password, and therefore it likely will not be able to authenticate anyone.
Though PAP is local only, at least from what I can tell, and there is no local user/pass for this account. Then it looks like it rolls to a EAP/leap authentication method. At this point it fails.
No. The LEAP message has the same meaning as the PAP message. And you're again ignoring the *content* of the message. Why?
Are the debug messages helpful?
If I truly understood more, then I'm sure that they would be. That are not as helpful for me; I have a lack of understanding at this point in time.
Read them. It helps. Really.
Do they accurately describe the problem, and give you hints for the solution?
I just see the problem as not working. I don't understand why it didn't even attempt mschapv2 when eap default was set to peap and peap default was set to mschapv2.
My messages explained why.
The PC is choosing LEAP, not FreeRADIUS.
I'm using Win7. Are you telling me that the PC is the one that is picking the security for the radius and not the Foundry Wireless AP controller?
Did my message contain the phrase "Foundry Wireless AP"? Or did my message contain the acronym "PC"?
Configure the PC to use LEAP, as was suggested in *another* response to your post.
I read that post. I thought the he was referring to the Foundry AP controller. You just told me that it was the fault of the PC though.
Exactly. If you READ my messages, you get answers to questions. Like the question you asked above about "when you say PC, do you really mean PC?" Honestly, I fail to understand why there is *any* confusion here. Alan DeKok.
I don't like leaving things unresolved and just laying around like so many other post that I have ran across. I guess Alan DeKok scares them off with the "It's in plain view dumb ass" attitude. I'm sure after answering the questions over and over again, it is about the only response that someone can give who it just tired of the same old questions and wants a challenge. With that being said... On Ubuntu 10.04 w/ updates, FreeRadius 2.1.8, Windows XP/7, and W2K AD The wiki has a HowTo on AD http://wiki.freeradius.org/FreeRADIUS_Active_Directory_Integration_HOWTO At the very top of this page there is: Updated tutorial for freeradius 2.x is at: http://deployingradius.com/documents/configuration/active_directory.html This is all well and good, but I jumped straight to that link. There seems to be some information that is left out and that is important in the "Updated tutorial." With all of the frustration I nuked all of FreeRadius from the server using 'aptitude purge freeradius freeradius-common freeradius-utils'. This cleaned up all of my changes. Then I reinstalled FreeRadius.
From here I followed the "Updated tutorial" until I got to: Configuring FreeRADIUS to use ntlm_auth for MS-CHAP. When I reached this section, and I had everything working, I went back to the original HowTo and read though it. (note to self: don't just a head just because a HowTo seems to good to be true.
The "Updated tutorial" doesn't let you know anything about peap, with_ntdomain_hack, the default setting of eap, or setting up clients. So it is not, in my opinion a complete walk though. There is light though. Once you I got to the point where ntlm_auth was working for me, I started back on the wiki HowTo and went to the section 'Configuration of clients.conf'. Set the client up. Client foundryAP { Ipaddr = 192.168.0.1 Secret = testing123 } In the Configuration of radius.conf section (this parts seems more like the 1. Config) the 'with_ntdomain_hack = yes' this was found in the ~/modules/mschap file. You don't need 'auth-type = MS-CHAP'. For ntlm_auth I'm using: ntlm_auth = "/usr/bin/ntlm_auth --request-nt-key --username=%{mschap:User-Name} --challenge=%{mschap:Challenge:-00} --nt-response=%{mschap:NT-Response:-00} --require-membership-of=DOMAIN+group" The eap.conf section of the HowTo was spot on. I also set the clients up, this was pointed out to me earlier in this tread twice, so make sure your client is setup correctly as well. Currently everything is working. I'm able to authenticate though radius using Windows 2000 AD. Resolved.
Mark Pipkin wrote:
With all of the frustration I nuked all of FreeRadius from the server using 'aptitude purge freeradius freeradius-common freeradius-utils'. This cleaned up all of my changes. Then I reinstalled FreeRadius.
i.e. start from the default configuration.
From here I followed the "Updated tutorial" until I got to: Configuring FreeRADIUS to use ntlm_auth for MS-CHAP. When I reached this section, and I had everything working, I went back to the original HowTo and read though it. (note to self: don't just a head just because a HowTo seems to good to be true.
And then follow the documentation. It *will* work.
The "Updated tutorial" doesn't let you know anything about peap, with_ntdomain_hack, the default setting of eap, or setting up clients. So it is not, in my opinion a complete walk though.
Sure. It documents one piece of the server functionality. For the rest, documentation generally exists.
Currently everything is working. I'm able to authenticate though radius using Windows 2000 AD.
Resolved.
Exactly. The frustration I generally show is people (a) butchering the default configs, (b) refusing to follow the docs, and (c) arguing when told "don't do that". It's really not hard. Alan DeKok.
hi, a quick look at your output shows that your server is configured to have a defauly type of EAP that doesnt match what your client is trying to use. there is then a reattempt after the NAK - and your client is using LEAP. it fails at the LEAP stage in the EAP module - check your eap.conf.... or, if you arent supposed to be using LEAP then check your client! ;-) alan
participants (3)
-
Alan Buxey -
Alan DeKok -
Mark Pipkin