- Freeradius-Users - lists.freeradius.org

Upgrade to v2.1.9 - ntdomain logon issues
by Extra Fu 08 Sep '10

08 Sep '10

Hello, We've recently upgraded FreeRADIUS from v1.1.8 to v2.1.9. We use it together with Cisco AP to do WPA2 Enterprise using PEAP. All users and machines accounts are stored in LDAP (OpenLDAP) and Samba v3.0 is being used to provide a NT domain to Windows users. OpenLDAP contains the ntPassword and lmPassword attributes for all users and machines. Prior the update, everything was working fine - that is: Windows machine authentication (after it boots), standalone logon and domain logon. After the update to v2.1.9, the domain login now fails constantly (Windows machine authentication and standalone logon work as expected). When domain logon fails, we keep seeing in the logs "[eap] Identity does not match User-Name, setting from EAP Identity.". We do not do any User-Name rewrite. With tried with and without with_ntdomain_hack in the mschap module, with and without the inner-tunnel. We also tried to define a realm with the "nostrip" option w/o success. Any insights would be appreciated. Here is our FreeRADIUS configuration followed by the Accept-Request we get which fails during domain logon : radiusd -fX FreeRADIUS Version 2.1.9, for host i686-redhat-linux-gnu, built on Sep 1 2010 at 17:25:13 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/raddb/radiusd.conf including configuration file /etc/raddb/proxy.conf including configuration file /etc/raddb/clients.conf including files in directory /etc/raddb/modules/ including configuration file /etc/raddb/modules/passwd including configuration file /etc/raddb/modules/logintime including configuration file /etc/raddb/modules/detail including configuration file /etc/raddb/modules/cui including configuration file /etc/raddb/modules/files including configuration file /etc/raddb/modules/sqlcounter_expire_on_login including configuration file /etc/raddb/modules/etc_group including configuration file /etc/raddb/modules/smsotp including configuration file /etc/raddb/modules/pap including configuration file /etc/raddb/modules/sradutmp including configuration file /etc/raddb/modules/exec including configuration file /etc/raddb/modules/linelog including configuration file /etc/raddb/modules/realm including configuration file /etc/raddb/modules/counter including configuration file /etc/raddb/modules/mschap including configuration file /etc/raddb/modules/acct_unique including configuration file /etc/raddb/modules/unix including configuration file /etc/raddb/modules/pam including configuration file /etc/raddb/modules/always including configuration file /etc/raddb/modules/wimax including configuration file /etc/raddb/modules/attr_filter including configuration file /etc/raddb/modules/detail.log including configuration file /etc/raddb/modules/expr including configuration file /etc/raddb/modules/smbpasswd including configuration file /etc/raddb/modules/chap including configuration file /etc/raddb/modules/preprocess including configuration file /etc/raddb/modules/detail.example.com including configuration file /etc/raddb/modules/ldap including configuration file /etc/raddb/modules/digest including configuration file /etc/raddb/modules/mac2vlan including configuration file /etc/raddb/modules/inner-eap including configuration file /etc/raddb/modules/checkval including configuration file /etc/raddb/modules/perl including configuration file /etc/raddb/modules/mac2ip including configuration file /etc/raddb/modules/otp including configuration file /etc/raddb/modules/ippool including configuration file /etc/raddb/modules/attr_rewrite including configuration file /etc/raddb/modules/radutmp including configuration file /etc/raddb/modules/policy including configuration file /etc/raddb/modules/echo including configuration file /etc/raddb/modules/sql_log including configuration file /etc/raddb/modules/expiration including configuration file /etc/raddb/eap.conf including configuration file /etc/raddb/policy.conf including files in directory /etc/raddb/sites-enabled/ including configuration file /etc/raddb/sites-enabled/default including configuration file /etc/raddb/sites-enabled/control-socket main { user = "radiusd" group = "radiusd" allow_core_dumps = no } including dictionary file /etc/raddb/dictionary main { prefix = "/usr" localstatedir = "/var" logdir = "/var/log/radius" libdir = "/usr/lib/freeradius" 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/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 } radiusd: #### Loading Clients #### client wireless_aps { ipaddr = 10.0.0.0 netmask = 8 require_message_authenticator = no secret = "SECRET" shortname = "foo-network" } client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } 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 { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_attr_rewrite Module: Instantiating copy.user-name attr_rewrite copy.user-name { attribute = "Stripped-User-Name" searchfor = "" searchin = "packet" replacewith = "%{User-Name}" append = no ignore_case = yes new_attribute = yes max_matches = 10 } Module: Instantiating add-dollar-sign attr_rewrite add-dollar-sign { attribute = "Stripped-User-Name" searchfor = "^(host/.*)" searchin = "packet" replacewith = "%{1}$" append = no ignore_case = yes new_attribute = no max_matches = 10 } Module: Instantiating strip-realm-name attr_rewrite strip-realm-name { attribute = "Stripped-User-Name" searchfor = "^(.*[\/]+)" searchin = "packet" replacewith = "" append = no ignore_case = yes new_attribute = no max_matches = 1 } Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = yes require_strong = no with_ntdomain_hack = no } 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 = 2048 } 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/raddb/certs/foo/foo.key" certificate_file = "/etc/raddb/certs/foo/foo.crt" CA_file = "/etc/raddb/certs/food/DigiCertCA.crt" dh_file = "/etc/raddb/certs/dh" random_file = "/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no make_cert_command = "/etc/raddb/certs/bootstrap" cache { enable = no lifetime = 24 max_entries = 255 } } 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 } 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/raddb/huntgroups" hints = "/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 } Module: Linked to module rlm_files Module: Instantiating files files { usersfile = "/etc/raddb/users" acctusersfile = "/etc/raddb/acct_users" preproxy_usersfile = "/etc/raddb/preproxy_users" compat = "no" } Module: Linked to module rlm_ldap Module: Instantiating ldap ldap { server = "foo.bar.zot" port = 389 password = "PASSWORD" identity = "uid=samba_user,ou=application,dc=foo,dc=bar,dc=baz" net_timeout = 1 timeout = 4 timelimit = 3 tls_mode = no start_tls = no tls_require_cert = "allow" basedn = "dc=foo,dc=bar,dc=baz" filter = "(uid=%{Stripped-User-Name})" base_filter = "(objectclass=radiusprofile)" auto_header = no access_attr_used_for_allow = yes groupname_attribute = "cn" groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))" dictionary_mapping = "/etc/raddb/ldap.attrmap" ldap_debug = 0 ldap_connections_number = 5 compare_check_items = no do_xlat = yes set_auth_type = yes } rlm_ldap: Registering ldap_xlat with xlat_name ldap rlm_ldap: Over-riding set_auth_type, as there is no module ldap listed in the "authenticate" section. rlm_ldap: reading ldap<->radius mappings from file /etc/raddb/ldap.attrmap rlm_ldap: LDAP radiusCheckItem mapped to RADIUS $GENERIC$ rlm_ldap: LDAP radiusReplyItem mapped to RADIUS $GENERIC$ rlm_ldap: LDAP radiusAuthType mapped to RADIUS Auth-Type rlm_ldap: LDAP radiusSimultaneousUse mapped to RADIUS Simultaneous-Use rlm_ldap: LDAP radiusCalledStationId mapped to RADIUS Called-Station-Id rlm_ldap: LDAP radiusCallingStationId mapped to RADIUS Calling-Station-Id rlm_ldap: LDAP lmPassword mapped to RADIUS LM-Password rlm_ldap: LDAP ntPassword mapped to RADIUS NT-Password rlm_ldap: LDAP radiusExpiration mapped to RADIUS Expiration rlm_ldap: LDAP radiusNASIpAddress mapped to RADIUS NAS-IP-Address rlm_ldap: LDAP radiusServiceType mapped to RADIUS Service-Type rlm_ldap: LDAP radiusFramedProtocol mapped to RADIUS Framed-Protocol rlm_ldap: LDAP radiusFramedIPAddress mapped to RADIUS Framed-IP-Address rlm_ldap: LDAP radiusFramedIPNetmask mapped to RADIUS Framed-IP-Netmask rlm_ldap: LDAP radiusFramedRoute mapped to RADIUS Framed-Route rlm_ldap: LDAP radiusFramedRouting mapped to RADIUS Framed-Routing rlm_ldap: LDAP radiusFilterId mapped to RADIUS Filter-Id rlm_ldap: LDAP radiusFramedMTU mapped to RADIUS Framed-MTU rlm_ldap: LDAP radiusFramedCompression mapped to RADIUS Framed-Compression rlm_ldap: LDAP radiusLoginIPHost mapped to RADIUS Login-IP-Host rlm_ldap: LDAP radiusLoginService mapped to RADIUS Login-Service rlm_ldap: LDAP radiusLoginTCPPort mapped to RADIUS Login-TCP-Port rlm_ldap: LDAP radiusCallbackNumber mapped to RADIUS Callback-Number rlm_ldap: LDAP radiusCallbackId mapped to RADIUS Callback-Id rlm_ldap: LDAP radiusFramedIPXNetwork mapped to RADIUS Framed-IPX-Network rlm_ldap: LDAP radiusClass mapped to RADIUS Class rlm_ldap: LDAP radiusSessionTimeout mapped to RADIUS Session-Timeout rlm_ldap: LDAP radiusIdleTimeout mapped to RADIUS Idle-Timeout rlm_ldap: LDAP radiusTerminationAction mapped to RADIUS Termination-Action rlm_ldap: LDAP radiusLoginLATService mapped to RADIUS Login-LAT-Service rlm_ldap: LDAP radiusLoginLATNode mapped to RADIUS Login-LAT-Node rlm_ldap: LDAP radiusLoginLATGroup mapped to RADIUS Login-LAT-Group rlm_ldap: LDAP radiusFramedAppleTalkLink mapped to RADIUS Framed-AppleTalk-Link rlm_ldap: LDAP radiusFramedAppleTalkNetwork mapped to RADIUS Framed-AppleTalk-Network rlm_ldap: LDAP radiusFramedAppleTalkZone mapped to RADIUS Framed-AppleTalk-Zone rlm_ldap: LDAP radiusPortLimit mapped to RADIUS Port-Limit rlm_ldap: LDAP radiusLoginLATPort mapped to RADIUS Login-LAT-Port rlm_ldap: LDAP radiusReplyMessage mapped to RADIUS Reply-Message rlm_ldap: LDAP radiusTunnelType mapped to RADIUS Tunnel-Type rlm_ldap: LDAP radiusTunnelMediumType mapped to RADIUS Tunnel-Medium-Type rlm_ldap: LDAP radiusTunnelPrivateGroupId mapped to RADIUS Tunnel-Private-Group-Id conns: 0x8919620 Module: Linked to module rlm_perl Module: Instantiating pf perl pf { module = "/etc/raddb/rlm_perl_pf.pl" func_authorize = "authorize" func_authenticate = "authenticate" func_accounting = "accounting" func_preacct = "preacct" func_checksimul = "checksimul" func_detach = "detach" func_xlat = "xlat" func_pre_proxy = "pre_proxy" func_post_proxy = "post_proxy" func_post_auth = "post_auth" func_recv_coa = "recv_coa" func_send_coa = "send_coa" } 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: Linked to module rlm_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating detail detail { detailfile = "/var/log/radius/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/radius/radwtmp" } Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/var/log/radius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Linked to module rlm_attr_filter Module: Instantiating attr_filter.accounting_response attr_filter attr_filter.accounting_response { attrsfile = "/etc/raddb/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 Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/etc/raddb/attrs.access_reject" key = "%{User-Name}" } } # 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" } } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /var/run/radiusd/radiusd.sock Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 10.99.28.105 port 1645, id=70, length=168 User-Name = "SMB001\\bob" Framed-MTU = 1400 Called-Station-Id = "0024.97f5.9ef1" Calling-Station-Id = "0019.d2b9.32d3" Service-Type = Login-User Message-Authenticator = 0x9da634498f98816bf7fdaacf1baa8817 EAP-Message = 0x0202001601534d423034305c65383431303037363332 NAS-Port-Type = Wireless-802.11 NAS-Port = 465 NAS-Port-Id = "465" NAS-IP-Address = 10.99.28.105 NAS-Identifier = "FOO-AP-CADM-28.105" +- entering group authorize {...} [copy.user-name] expand: %{User-Name} -> SMB001\bob copy.user-name: Added attribute Stripped-User-Name with value 'SMB001\bob' ++[copy.user-name] returns ok [add-dollar-sign] expand: ^(host/.*) -> ^(host/.*) add-dollar-sign: Does not match: Stripped-User-Name = SMB001\bob ++[add-dollar-sign] returns ok [strip-realm-name] expand: ^(.*[\/]+) -> ^(.*[\/]+) strip-realm-name: Changed value for attribute Stripped-User-Name from 'SMB001\bob' to 'bob' ++[strip-realm-name] returns ok ++[preprocess] returns ok [eap] EAP packet type response id 2 length 22 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated [files] users: Matched entry DEFAULT at line 143 ++[files] returns ok [ldap] performing user authorization for SMB001\bob [ldap] expand: (uid=%{Stripped-User-Name}) -> (uid=bob) [ldap] expand: dc=foo,dc=bar,dc=zot -> dc=foo,dc=bar,dc=zot rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in dc=foo,dc=bar,dc=zot, with filter (uid=bob) [ldap] looking for check items in directory... rlm_ldap: ntPassword -> NT-Password == 0x3633303143414331303145383143384643443739373931373734443636343535 rlm_ldap: lmPassword -> LM-Password == 0x3845353442393133393441333246394641414433423433354235313430344545 [ldap] looking for reply items in directory... WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? [ldap] user SMB001\bob authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 ++[ldap] returns ok rlm_perl: Added pair NAS-Port-Type = Wireless-802.11 rlm_perl: Added pair Service-Type = Login-User rlm_perl: Added pair Calling-Station-Id = 0019.d2b9.32d3 rlm_perl: Added pair Called-Station-Id = 0024.97f5.9ef1 rlm_perl: Added pair Message-Authenticator = 0x9da634498f98816bf7fdaacf1baa8817 rlm_perl: Added pair User-Name = SMB001\\bob rlm_perl: Added pair NAS-Identifier = FOO-AP-CADM-28.105 rlm_perl: Added pair EAP-Message = 0x0202001601534d423034305c65383431303037363332 rlm_perl: Added pair EAP-Type = Identity rlm_perl: Added pair Stripped-User-Name = bob rlm_perl: Added pair NAS-IP-Address = 10.99.28.105 rlm_perl: Added pair NAS-Port = 465 rlm_perl: Added pair NAS-Port-Id = 465 rlm_perl: Added pair Framed-MTU = 1400 rlm_perl: Added pair Tunnel-Private-Group-ID = 228 rlm_perl: Added pair Tunnel-Type = 13 rlm_perl: Added pair Tunnel-Medium-Type = 6 rlm_perl: Added pair NT-Password = 0x3633303143414331303145383143384643443739373931373734443636343535 rlm_perl: Added pair LM-Password = 0x3845353442393133393441333246394641414433423433354235313430344545 rlm_perl: Added pair Ldap-UserDn = uid=bob,ou=Employee,ou=Person,dc=foo,dc=bar,dc=zot rlm_perl: Added pair Auth-Type = EAP ++[pf] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Identity does not match User-Name, setting from EAP Identity. [eap] Failed in handler ++[eap] returns invalid Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> SMB001\\bob attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 12 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 12 Sending Access-Reject of id 70 to 10.99.28.105 port 1645 Waking up in 4.9 seconds. Thanks,

2 3

RE: freeradius authentication stops working after some time...
by Korosi, Nick 08 Sep '10

08 Sep '10

I was wondering if anybody had any more information with this topic. Winbind authentication works every time during testing of ntlm_auth, but PEAP will only work once after a reboot and then fails every time. I can see a difference in the EAP-Message when running in debug mode once it gets Request 3's Access-Request packet. >> When Successful: rad_recv: Access-Request packet from host 172.20.1.99 port 65288, id=212, length=522 User-Name = " MYDOMAIN\\myuser" NAS-Port = 68 State = 0xbdba4064bfb959ed871d7a760f4a6189 EAP-Message = 0x02030150198000000146160301010610000102010041edfd5ca690a35d3f2b0852c9b0018961373e600fa0f7d65fd7b37580cd527e634e4eba1fcf9ac1103146b7520c7d273f43d6698c3ce14a6d7650d6a1deaa28bc9d3156ffa21d627d91d6b7da5b229abfcab7a73b083fdb79e43a49dc98f0d20c497600cd96f2fe13587bb0d5e59f49c32cb36a0ee8efe471e77f4d128bfa815336b198e84a3d3549f1eaf2a7cce6b0ddc0c1d01b2685f34d23d8170f8e657ebfa9b33e5c95ba5e1fc1bf83f49a1031b228272d2f21af93c904cfc31a9689a3028ccd4f8eb0eed67d54b07459deef5618bff59d2ba2a6fe801868ddaa6b321200824fd6d2011a5f EAP-Message = 0x640caaf2df40538fd91c1da8c2189b89d9d59e66b40f816d14030100010116030100303628b50481fc50a51db0c5315a5898ada3f498ed9385706e9b165e322cdb655704b73380d527cfa1966359f43e23b54a Message-Authenticator = 0xe0435af614c2b43a52ab07911e607257 Acct-Session-Id = "8O2.1x8155007a0006d0e1" NAS-Port-Id = "ge-0/0/1.0" Calling-Station-Id = "00-21-86-a0-d5-b6" Called-Station-Id = "00-1f-12-35-a3-40" NAS-IP-Address = 172.20.1.99 NAS-Identifier = "CL-SW-SPARE-P48-1" NAS-Port-Type = Ethernet .... [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS TLS Length 326 [peap] Length Included [peap] eaptls_verify returned 11 [peap] <<< TLS 1.0 Handshake [length 0106], ClientKeyExchange [peap] TLS_accept: SSLv3 read client key exchange A [peap] <<< TLS 1.0 ChangeCipherSpec [length 0001] [peap] <<< TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 read finished A [peap] >>> TLS 1.0 ChangeCipherSpec [length 0001] [peap] TLS_accept: SSLv3 write change cipher spec A [peap] >>> TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 write finished A [peap] TLS_accept: SSLv3 flush data [peap] (other): SSL negotiation finished successfully SSL Connection Established [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 212 to 172.20.1.99 port 65288 EAP-Message = 0x01040041190014030100010116030100304722cf0ba4ff47b05d93e56d91e9f7fb385859f4517e96acb6f13887cee6d51e2e786637fb3a783ce362542c4004da32 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xbdba4064bebe59ed871d7a760f4a6189 >> When Fails: rad_recv: Access-Request packet from host 172.20.1.99 port 60566, id=62, length=190 User-Name = "MYDOMAIN\\myuser" NAS-Port = 68 State = 0x98b30a269ab013ceb4bf9c4f43040953 EAP-Message = 0x020300061900 Message-Authenticator = 0x20ce44a84dc4391f888de907003c74b8 Acct-Session-Id = "8O2.1x81c3024a00011abf" NAS-Port-Id = "ge-0/0/1.0" Calling-Station-Id = "00-21-86-a0-d5-b6" Called-Station-Id = "00-1f-12-35-a3-40" NAS-IP-Address = 172.20.1.99 NAS-Identifier = "CL-SW-SPARE-P48-1" NAS-Port-Type = Ethernet .... [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 62 to 172.20.1.99 port 60566 EAP-Message = 0x010400061900 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x98b30a269bb713ceb4bf9c4f43040953 >From what I can see, I'm getting a TLS ACK and no SSL connection established when it fails. I generated my server certificate from our internal Microsoft Certificate Authority and installed them on the server. I'm pretty sure everything is okay since my Windows 2007 computer authenticates every time if configured to use certificate authentication rather than PEAP. Also, if I use Microsoft IAS as my radius server PEAP works every time, therefore I don't believe my network equipment is having any problems. Any additional ideas would be greatly appreciated. Thanks, Nick

2 1

Enabling Session Resumption in FreeRadius
by Panagiotis Georgopoulos 08 Sep '10

08 Sep '10

Hello all, I have a client that uses EAP-TTLS to authenticate to a FreeRadius (2.1.8) over different access networks. After some handovers from one network to another, I see in my FR log that session resumption fails, and specifically I see : Debug: SSL Connection Established Debug: SSL Application Data Info: [ttls] eaptls_process returned 3 Info: [ttls] Skipping Phase2 due to session resumption Info: [ttls] FAIL: *Forcibly stopping session resumption as it is not allowed* Info: [eap] Freeing handler Info: ++[eap] returns reject Info: Using Post-Auth-Type Reject Then a full EAP-TTLS exchange follows from the beginning that succeeds. However, the failure message above "Forcibly stopping session resumption as it is not allowed" implies that there is somewhere in the FR a setting that will allow it? Am I assuming rightly? If yes, where is this setting? If no, does anyone know why session resumption fails ? Thanks a lot in advance, Panos

3 3

Fwd: ldap group lookup help
by Walter Gould 08 Sep '10

08 Sep '10

I never saw a reply to my below e-mail. Would anybody have any thoughts or ideas on why our ldap group lookups fail after some period of time...? If it would help to send debug output, I can... Just for my information, are many folks out there using ldap/AD group lookups on large FR installs? Thanks in advance, Walter -------- Original Message -------- Subject: ldap group lookup help Date: Thu, 02 Sep 2010 09:49:02 -0500 From: Walter Gould <gouldwp(a)auburn.edu> To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Group, We are having problems with ldap group lookups... Here's our environment. Using Freeradius 2.1.8 to authenticate wireless users against our AD servers and perform ldap group membership lookups. Using WPA2-AES-PEAP-MSCHAPv2. When radiusd is started, initially the lookups work fine and we see successful auth's in our radius logs. But, after some period of time, we eventually begin to see bunches of "Invalid user:" radius logs. The only thing that seems to fix this is to remove the ldap group lookups from the freeradius config. In our ldap module, the basedn we specify is dc=auburn,dc=edu (as we have multiple user ou's). Not sure if that might be causing an issue or not..? One thing I have noticed is there are 3 ldap group lookups that each say "rlm_ldap::ldap_groupcmp: User found in group xxxx". I have read posts about configuring the ldap module to us the inner-tunnel - which I have done. Is there anyway to reduce the number of group lookups to only one? Not sure if the extra lookups are causing unneeded traffic which may be causing issues? Also, I see 10 Access-Request packets and about the same number of Access-Challenge packets.. Is this normal? Just wondering if excessive unneeded traffic is what is overloading the AD/ldap servers? Any help or suggestions will be appreciated. Thanks, Walter Gould Auburn University

1 0

Wrong Vlan assignment by freeradius, threading issue?!
by Jan Zacharias 08 Sep '10

08 Sep '10

Hi Folks, I'm running into some very bad issue: when running freeradius in threaded mode (default) it's mixing up CONCURRENT requests resulting in a wrong vlan assignment. Here are the logs of two clients (OSX and Ubuntu). The Ubuntu supplicant (wpa-suppl.) always fails the first login try, but this is normal. This is with reauthentification interval of 10 seconds, so requests seem to overlap: Tue Sep 7 16:45:36 2010 : Auth: Login incorrect: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50037 cli 00-1C-25-A2-10-3C) Tue Sep 7 16:45:38 2010 : Auth: Login OK: [jan/<via Auth-Type = mschap>] (from client swba1-00-test port 0 via TLS tunnel) Tue Sep 7 16:45:38 2010 : Auth: Login OK: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50037 cli 00-1C-25-A2-10-3C) Tue Sep 7 16:45:39 2010 : Auth: Login OK: [jan/<via Auth-Type = mschap>] (from client swba1-00-test port 0 via TLS tunnel) Tue Sep 7 16:45:41 2010 : Auth: Login OK: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50039 cli 00-16-CB-AA-0F-CB) Tue Sep 7 16:45:44 2010 : Error: Discarding duplicate request from client swba1-00-test port 1645 - ID: 208 due to unfinished request 267 Tue Sep 7 16:45:53 2010 : Auth: Login incorrect: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50037 cli 00-1C-25-A2-10-3C) Tue Sep 7 16:45:56 2010 : Auth: Login OK: [jan/<via Auth-Type = mschap>] (from client swba1-00-test port 0 via TLS tunnel) Tue Sep 7 16:45:56 2010 : Auth: Login OK: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50037 cli 00-1C-25-A2-10-3C) Tue Sep 7 16:45:56 2010 : Auth: Login OK: [jan/<via Auth-Type = mschap>] (from client swba1-00-test port 0 via TLS tunnel) Tue Sep 7 16:45:59 2010 : Auth: Login OK: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50039 cli 00-16-CB-AA-0F-CB) Tue Sep 7 16:46:01 2010 : Error: Discarding duplicate request from client swba1-00-test port 1645 - ID: 232 due to unfinished request 291 Now let's check what Vlans got assigned (this is the vmps log, vmps gets only this MAC via rad2vmps and looks up the vlan in a mysql db): ALLOW: 00:16:cb:aa:0f:cb -> Management, switch swba1-00-test.sb.dfki.de [172.16.0.24] port Gi0/39 ALLOW: 00:16:cb:aa:0f:cb -> Management, switch swba1-00-test.sb.dfki.de [172.16.0.24] port Gi0/39 ALLOW: 00:16:cb:aa:0f:cb -> Management, switch swba1-00-test.sb.dfki.de [172.16.0.24] port Gi0/39 ALLOW: 00:16:cb:aa:0f:cb -> Management, switch swba1-00-test.sb.dfki.de [172.16.0.24] port Gi0/39 So freeradius takes the MAC of the OSX client and inserts it into the request that is associated with the Ubuntu client - VERY BAD. Now I only changed the reauthentification interval to 20 seconds, so the requests do not overlap anymore for sure. Tue Sep 7 16:46:50 2010 : Auth: Login incorrect: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50037 cli 00-1C-25-A2-10-3C) Tue Sep 7 16:46:53 2010 : Auth: Login OK: [jan/<via Auth-Type = mschap>] (from client swba1-00-test port 0 via TLS tunnel) Tue Sep 7 16:46:53 2010 : Auth: Login OK: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50037 cli 00-1C-25-A2-10-3C) Tue Sep 7 16:46:57 2010 : Auth: Login OK: [jan/<via Auth-Type = mschap>] (from client swba1-00-test port 0 via TLS tunnel) Tue Sep 7 16:46:57 2010 : Auth: Login OK: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50039 cli 00-16-CB-AA-0F-CB) Tue Sep 7 16:47:17 2010 : Auth: Login incorrect: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50037 cli 00-1C-25-A2-10-3C) Tue Sep 7 16:47:20 2010 : Auth: Login OK: [jan/<via Auth-Type = mschap>] (from client swba1-00-test port 0 via TLS tunnel) Tue Sep 7 16:47:20 2010 : Auth: Login OK: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50037 cli 00-1C-25-A2-10-3C) Tue Sep 7 16:47:25 2010 : Auth: Login OK: [jan/<via Auth-Type = mschap>] (from client swba1-00-test port 0 via TLS tunnel) Tue Sep 7 16:47:25 2010 : Auth: Login OK: [jan/<via Auth-Type = EAP>] (from client swba1-00-test port 50039 cli 00-16-CB-AA-0F-CB) Vmps log: ALLOW: 00:1c:25:a2:10:3c -> FBIB, switch swba1-00-test.sb.dfki.de [172.16.0.24] port Gi0/37 ALLOW: 00:16:cb:aa:0f:cb -> Management, switch swba1-00-test.sb.dfki.de [172.16.0.24] port Gi0/39 ALLOW: 00:1c:25:a2:10:3c -> FBIB, switch swba1-00-test.sb.dfki.de [172.16.0.24] port Gi0/37 ALLOW: 00:16:cb:aa:0f:cb -> Management, switch swba1-00-test.sb.dfki.de [172.16.0.24] port Gi0/39 The short reauthentification interval is just to simulate a few more clients for stresstesting purposes. Can anyone help? The operating system is FreeBSD 8.1-RELEASE i386 and always las load averages of 0.00, 0.00, 0.00 Switch hardware is cisco WS-C3560G-48PS with firmware (12.2(53)SE2 C3560-IPSERVICESK9-M). Best, Jan

2 6

Freeradius not unescaping \ and "
by Murray Long 07 Sep '10

07 Sep '10

I have the following setup: CoovaChilli accepts user login requests and sends radius packets to freeradius freeradius then proxies the requests (based on realm) onto a second freeradius server. If I attempt a login with username "A\" The first freeradius server recieves packets with UserName atribute = "A\\" and sends a packet to the sencond radius server with username attribute = "A\\\\" (as reported by wireshark) So it looks like freeradius is not correctly unescaping the username attribute. (Or incorrectly re-escaping) before the proxy. How is freeradius expected to behave when escaping backslash and quote characters before proxying? And is it possible to alter this behavior though configuration? Thanks, Murray

3 9

Best Authentication Method for Various Supplicant
by homyang cha 07 Sep '10

07 Sep '10

Hello I am running freeradius-2.17 on CentOS-5.5 box with mysql-5.0.77 as backend and daloradius-0.9-8 as the web management. I have successfully configured an tested EAP-MD5, PEAP and PAP authentication using windows 7 as supplicant with wired 802.1x authentication (no certificates used) and NAS as a Huawei Switch (Quidway S5600 Series) and seems to be working fine. Now my issues are: in my networks there are various kinds of OS running for supplicants. To name a few are Windows XP (SP2, SP3), Windows Vista, Windows 7, Fedora, CentOS, Ubuntu and Mac OS X. I have to configure AAA applicants systems in such a way all this systems are supported. Can someone help me suggest or have any idea/experience on this. What could be the best authentiation method that I can use so that all this supplicants using different OS are supported. Also I use wired connection as well as wireless connection in the network. Does anybody throw some light on this matter? Thanks in Advance -- homyang (aka puran)

2 3

FreeRADIUS expertise in Switzerland
by Steudler, Oliver 07 Sep '10

07 Sep '10

Hello, I hope this is not too Off Topic, but I am looking for a company with FreeRADIUS expertise for a substantial Project in Switzerland ? Would greatly appreciate it if someone could recommend a reliable and competent partner for this. Regards Oliver Steudler steudler (at) netcloud (dot) ch +41 79 214 97 82

1 0

Problem with rlm_perl
by Nasser Heidari 07 Sep '10

07 Sep '10

Dear Folks, I'm using a perl module to record and save clients MAC address to DB. In situations that cisco-av-pair is not included in RADIUS packet, I'm replacing it with 0000.0000.0000. Everything is working just fine in test environment but when running on production servers the recorded MAC address for those clients without cisco-av-pair attribute in their packet is not 0000.0000.0000 but it's a wrong MAC which belongs to another packet received seconds ago. We even captured all the RADIUS traffic sent form NASes and replayed it in our test environment but I wanted to capture users mac address, so I've added a perl module , and after parsing cisco-av-pair attribute , I save it to DB. In normal situation everything works like a charm , but in some cases, If NAS doesn't send mac-address attribute, I expect to save a 0000.0000.0000 mac address in DB , but no success. There is a condition that I check if mac-address attribute exists in request or not, if exist it's ok , if not it should update request with a 0000.0000.0000 mac address.

2 3

EAP-MD5 testing with radeapclient and eapol_test
by Chidanand Gangur 07 Sep '10

07 Sep '10

Hi All, I have a proxy setup ( proxy server 192.168.6.134) where users are proxied to home server (192.168.7.40). Host IP address = 192.168.6.181 FreeRADIUS version 2.1.9 User authentication using radclient works fine when I issue following command echo "User-Name=raduser(a)mytest.com,Password=pass123" | radclient 192.168.6.134 auth testing123 I get following response on my proxy server rad_recv: Access-Accept packet from host 192.168.7.40 port 1812, id=104, length=68 Proxy-State = 0x3737 Framed-Protocol = PPP Service-Type = Framed-User Class = 0x52a505b1000001370001c0a8072801cb4d87ddbf246a0000000000000016 I try the same test to work out with EAP using following command: echo "User-Name=raduser(a)mytest.com ,Password=pass123,EAP-Code=Response,EAP-Id=210,EAP-Type-Identity= raduser(a)mytest.com" | radeapclient -x 192.168.6.134 auth testing123 I see following output on proxy server: rad_recv: Access-Request packet from host 192.168.6.181 port 32771, id=108, length=107 User-Name = "raduser(a)mytest.com" User-Password = "pass123" EAP-Message = 0x02d2001a0172616475736572406e65766973746573742e636f6d Message-Authenticator = 0xe61561c7667d60c2fbc37709b16e8193 Mon Sep 6 06:48:30 2010 : Info: +- entering group authorize {...} Mon Sep 6 06:48:30 2010 : Info: ++[preprocess] returns ok Mon Sep 6 06:48:30 2010 : Info: ++[chap] returns noop Mon Sep 6 06:48:30 2010 : Info: ++[mschap] returns noop Mon Sep 6 06:48:30 2010 : Info: [suffix] Looking up realm "mytest.com" for User-Name = "raduser(a)mytest.com" Mon Sep 6 06:48:30 2010 : Info: [suffix] Found realm "mytest.com" Mon Sep 6 06:48:30 2010 : Info: [suffix] Adding Stripped-User-Name = "raduser" Mon Sep 6 06:48:30 2010 : Info: [suffix] Adding Realm = "mytest.com" Mon Sep 6 06:48:30 2010 : Info: [suffix] Proxying request from user raduser to realm mytest.com Mon Sep 6 06:48:30 2010 : Info: [suffix] Preparing to proxy authentication request to realm "mytest.com" Mon Sep 6 06:48:30 2010 : Info: ++[suffix] returns updated Mon Sep 6 06:48:30 2010 : Info: [eap] Request is supposed to be proxied to Realm mytest.com. Not doing EAP. Mon Sep 6 06:48:30 2010 : Info: ++[eap] returns noop Mon Sep 6 06:48:30 2010 : Info: ++[unix] returns notfound Mon Sep 6 06:48:30 2010 : Info: [files] users: Matched entry DEFAULT at line 195 Mon Sep 6 06:48:30 2010 : Info: [files] expand: %{User-Name} -> raduser(a)mytest.com Mon Sep 6 06:48:30 2010 : Info: ++[files] returns ok Mon Sep 6 06:48:30 2010 : Info: ++[expiration] returns noop Mon Sep 6 06:48:30 2010 : Info: ++[logintime] returns noop Mon Sep 6 06:48:30 2010 : Info: ++[pap] returns noop Mon Sep 6 06:48:30 2010 : Info: WARNING: Empty pre-proxy section. Using default return values. Mon Sep 6 06:48:30 2010 : Info: Proxying request 0 to home server 192.168.7.40 port 1812 Sending Access-Request of id 40 to 192.168.7.40 port 1812 User-Name = "raduser" User-Password = "pass123" EAP-Message = 0x02d2001a0172616475736572406e65766973746573742e636f6d Message-Authenticator = 0x00000000000000000000000000000000 NAS-IP-Address = 192.168.6.181 Proxy-State = 0x313038 Mon Sep 6 06:48:30 2010 : Debug: Going to the next request Mon Sep 6 06:48:30 2010 : Debug: Waking up in 0.9 seconds. rad_recv: Access-Accept packet from host 192.168.7.40 port 1812, id=40, length=69 Proxy-State = 0x313038 Framed-Protocol = PPP Service-Type = Framed-User Class = 0x52a605b2000001370001c0a8072801cb4d87ddbf246a0000000000000017 Mon Sep 6 06:48:30 2010 : Info: +- entering group post-proxy {...} Mon Sep 6 06:48:30 2010 : Info: [force_username] expand: %{User-Name} -> raduser(a)mytest.com Mon Sep 6 06:48:30 2010 : Debug: force_username: Added attribute User-Name with value 'raduser(a)mytest.com' Mon Sep 6 06:48:30 2010 : Info: ++[force_username] returns ok Mon Sep 6 06:48:30 2010 : Info: [eap] No pre-existing handler found Mon Sep 6 06:48:30 2010 : Info: ++[eap] returns noop Mon Sep 6 06:48:30 2010 : Info: Found Auth-Type = Accept Mon Sep 6 06:48:30 2010 : Info: Auth-Type = Accept, accepting the user Mon Sep 6 06:48:30 2010 : Info: +- entering group post-auth {...} Mon Sep 6 06:48:30 2010 : Info: ++[exec] returns noop Sending Access-Accept of id 108 to 192.168.6.181 port 32771 Framed-Protocol = PPP Service-Type = Framed-User Class = 0x52a605b2000001370001c0a8072801cb4d87ddbf246a0000000000000017 User-Name = "raduser(a)mytest.com" When I use eapol_test client to using following command: eapol_test -c /tmp/eapol.conf -a 192.168.6.134 -p 1812 -s testing123 -r 1 eapol.conf is as follows network={ key_mgmt=NONE eap=MD5 identity="raduser(a)mytest.com" password="pass123" } I see following output on my proxy server: Mon Sep 6 06:53:49 2010 : Info: Proxying request 0 to home server 192.168.7.40 port 1812 Sending Access-Request of id 166 to 192.168.7.40 port 1812 User-Name = "raduser" NAS-IP-Address = 127.0.0.1 Calling-Station-Id = "02-00-00-00-00-01" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x0200001a0172616475736572406e65766973746573742e636f6d Message-Authenticator = 0x00000000000000000000000000000000 Proxy-State = 0x30 Mon Sep 6 06:53:49 2010 : Debug: Going to the next request Mon Sep 6 06:53:49 2010 : Debug: Waking up in 0.9 seconds. rad_recv: Access-Challenge packet from host 192.168.7.40 port 1812, id=166, length=109 Proxy-State = 0x30 Session-Timeout = 6 EAP-Message = 0x0101002304101f3bc497bfe2cfaf507a66218e4dcb01524f4f54544553544c41424144 State = 0x1a2902ae000001370001c0a8072800000003235c233800 Message-Authenticator = 0x467eeb430357cbddf194719353853d80 Mon Sep 6 06:53:49 2010 : Info: +- entering group post-proxy {...} Mon Sep 6 06:53:49 2010 : Info: [force_username] expand: %{User-Name} -> raduser(a)mytest.com Mon Sep 6 06:53:49 2010 : Debug: force_username: Added attribute User-Name with value 'raduser(a)mytest.com' Mon Sep 6 06:53:49 2010 : Info: ++[force_username] returns ok Mon Sep 6 06:53:49 2010 : Info: [eap] No pre-existing handler found Mon Sep 6 06:53:49 2010 : Info: ++[eap] returns noop Sending Access-Challenge of id 0 to 192.168.6.181 port 32771 Session-Timeout = 6 EAP-Message = 0x0101002304101f3bc497bfe2cfaf507a66218e4dcb01524f4f54544553544c41424144 State = 0x1a2902ae000001370001c0a8072800000003235c233800 Message-Authenticator = 0x00000000000000000000000000000000 User-Name = "raduser(a)mytest.com" Mon Sep 6 06:53:49 2010 : Info: Finished request 0. Mon Sep 6 06:53:49 2010 : Debug: Going to the next request Mon Sep 6 06:53:49 2010 : Debug: Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.6.181 port 32771, id=1, length=171 User-Name = "raduser(a)mytest.com" NAS-IP-Address = 127.0.0.1 Calling-Station-Id = "02-00-00-00-00-01" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x0201001604100ff84736f21760abada91fdb828e888c State = 0x1a2902ae000001370001c0a8072800000003235c233800 Message-Authenticator = 0xe1da93d7d4f4d4b68cf9ef4333a1f8eb Mon Sep 6 06:53:49 2010 : Info: +- entering group authorize {...} Mon Sep 6 06:53:49 2010 : Info: ++[preprocess] returns ok Mon Sep 6 06:53:49 2010 : Info: ++[chap] returns noop Mon Sep 6 06:53:49 2010 : Info: ++[mschap] returns noop Mon Sep 6 06:53:49 2010 : Info: [suffix] Looking up realm "mytest.com" for User-Name = "raduser(a)mytest.com" Mon Sep 6 06:53:49 2010 : Info: [suffix] Found realm "mytest.com" Mon Sep 6 06:53:49 2010 : Info: [suffix] Adding Stripped-User-Name = "raduser" Mon Sep 6 06:53:49 2010 : Info: [suffix] Adding Realm = "mytest.com" Mon Sep 6 06:53:49 2010 : Info: [suffix] Proxying request from user raduser to realm mytest.com Mon Sep 6 06:53:49 2010 : Info: [suffix] Preparing to proxy authentication request to realm "mytest.com" Mon Sep 6 06:53:49 2010 : Info: ++[suffix] returns updated Mon Sep 6 06:53:49 2010 : Info: [eap] Request is supposed to be proxied to Realm mytest.com. Not doing EAP. Mon Sep 6 06:53:49 2010 : Info: ++[eap] returns noop Mon Sep 6 06:53:49 2010 : Info: ++[unix] returns notfound Mon Sep 6 06:53:49 2010 : Info: [files] users: Matched entry DEFAULT at line 195 Mon Sep 6 06:53:49 2010 : Info: [files] expand: %{User-Name} -> raduser(a)mytest.com Mon Sep 6 06:53:49 2010 : Info: ++[files] returns ok Mon Sep 6 06:53:49 2010 : Info: ++[expiration] returns noop Mon Sep 6 06:53:49 2010 : Info: ++[logintime] returns noop Mon Sep 6 06:53:49 2010 : Info: ++[pap] returns noop Mon Sep 6 06:53:49 2010 : Info: WARNING: Empty pre-proxy section. Using default return values. Sending Access-Request of id 177 to 192.168.7.40 port 1812 User-Name = "raduser" NAS-IP-Address = 127.0.0.1 Calling-Station-Id = "02-00-00-00-00-01" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x0201001604100ff84736f21760abada91fdb828e888c State = 0x1a2902ae000001370001c0a8072800000003235c233800 Message-Authenticator = 0x00000000000000000000000000000000 Proxy-State = 0x31 Mon Sep 6 06:53:49 2010 : Info: Proxying request 1 to home server 192.168.7.40 port 1812 Sending Access-Request of id 177 to 192.168.7.40 port 1812 User-Name = "raduser" NAS-IP-Address = 127.0.0.1 Calling-Station-Id = "02-00-00-00-00-01" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x0201001604100ff84736f21760abada91fdb828e888c State = 0x1a2902ae000001370001c0a8072800000003235c233800 Message-Authenticator = 0x00000000000000000000000000000000 Proxy-State = 0x31 Mon Sep 6 06:53:49 2010 : Debug: Going to the next request Mon Sep 6 06:53:49 2010 : Debug: Waking up in 0.9 seconds. rad_recv: Access-Reject packet from host 192.168.7.40 port 1812, id=177, length=47 Proxy-State = 0x31 EAP-Message = 0x04010004 Message-Authenticator = 0x9ce0e5c3b355540c348cbff29f5f40f2 Mon Sep 6 06:53:49 2010 : Info: +- entering group post-proxy {...} Mon Sep 6 06:53:49 2010 : Info: [force_username] expand: %{User-Name} -> raduser(a)mytest.com Mon Sep 6 06:53:49 2010 : Debug: force_username: Added attribute User-Name with value 'raduser(a)mytest.com' Mon Sep 6 06:53:49 2010 : Info: ++[force_username] returns ok Mon Sep 6 06:53:49 2010 : Info: [eap] No pre-existing handler found Mon Sep 6 06:53:49 2010 : Info: ++[eap] returns noop Mon Sep 6 06:53:49 2010 : Info: Using Post-Auth-Type Reject Mon Sep 6 06:53:49 2010 : Info: +- entering group REJECT {...} Mon Sep 6 06:53:49 2010 : Info: [attr_filter.access_reject] expand: %{User-Name} -> raduser(a)mytest.com Mon Sep 6 06:53:49 2010 : Debug: attr_filter: Matched entry DEFAULT at line 11 Mon Sep 6 06:53:49 2010 : Info: ++[attr_filter.access_reject] returns updated Mon Sep 6 06:53:49 2010 : Info: Delaying reject of request 1 for 1 seconds Mon Sep 6 06:53:49 2010 : Debug: Going to the next request Mon Sep 6 06:53:49 2010 : Debug: Waking up in 0.9 seconds. Mon Sep 6 06:53:50 2010 : Info: Sending delayed reject for request 1 Sending Access-Reject of id 1 to 192.168.6.181 port 32771 EAP-Message = 0x04010004 Message-Authenticator = 0x00000000000000000000000000000000 Mon Sep 6 06:53:50 2010 : Debug: Waking up in 3.9 seconds. Mon Sep 6 06:53:54 2010 : Info: Cleaning up request 0 ID 0 with timestamp +48 Mon Sep 6 06:53:54 2010 : Debug: Waking up in 0.9 seconds. Mon Sep 6 06:53:55 2010 : Info: Cleaning up request 1 ID 1 with timestamp +48 Mon Sep 6 06:53:55 2010 : Info: Ready to process requests. I have never succedded with eapol_test. I doubt on NAS-IP-Address attribute in Access=Request which is 127.0.0.1. Can some body point me where am I going wrong? -- Chidanand Gangur Pune.

4 9