- Freeradius-Users - lists.freeradius.org

Fresh Install
by David Peterson 28 May '10

28 May '10

I just installed Ubuntu 10.04 server with the basic LAMP install added. I used the git method for downloading and compiling freeradius and everything installed properly but for one caveat. radiusd: error while loading shared libraries: libfreeradius-radius-2.1.9.so: cannot open shared object file: No such file or directory I can find this file but I am not sure how to resolve this issue David

3 3

Conditional radreply with Freeradius. Possible somehow ?
by Pere Hospital 28 May '10

28 May '10

Hi all, Here is the situation. We have a freeradius server that receives autnetication/authorization requests from multiple vpn servers. For just CERTAIN servers we want to return a Framed-IP-Address via radreply. We would control the Framed-IP-Address return value (if any) via Nas-Identifier parameter that we receive from the VPN servers. So the logic of the process would be : Receive auth request from VPN server ---> Authenticate/Authorize user (via radcheck, checking expiration date, number of simultaneous logins ...). ---> If NAS-Identifier = X then return (via radreply) Framed-IP-Address=Y ---> If NAS-Identifier = Z then return (via radreply) Framed-IP-Address=W ---> otherwise don't return a Framed-IP-Address Is this possible somehow ? We are using SQL module in freeradius. Details : Debian 5.0.4 freeradius 2.0.4+dfsg-6 Regards, Pere -- Pere Hospital, CISSP®, OSCP® secWays Security First p: +34 933905455 m: +34 649827299 e: pere(a)secways.com w: www.secways.com PGP keyid: 0x100D35BDA0F669A8 http://keyserver.pgp.com

2 3

check ldap users with different client IP's
by Stephon Chen 28 May '10

28 May '10

hello all I've used freeradius as the front of a LDAP server. Here, I want to allow different access rights for each LDAP group & client ip address For example below: user X in LDAP group A, from ip IP-A user Y in LDAP group B, from ip IP-B if the user is from IP-A and user in LDAP group A, then send Accept-Accept packet How do this be done with freeradius? Thanks a lot

3 2

Option 82 parse problems.
by Anton 28 May '10

28 May '10

Good day. I'm trying to set freeradius like dhcp server with option 82 parsing and SQL data lookup. Now I use versions 2.1.8 and 2.1.9 with exactly the same configs and there is no SQL configuration yet, only default dhcp config with my test diff (see below). I have two questions for now: 1. In dictionary.dhcp there are two strings (version 2.1.8): ATTRIBUTE DHCP-Agent-Circuit-Id 0x0152 octets ATTRIBUTE DHCP-Agent-Remote-Id 0x0252 octets but when I start radiusd -X I see only one whole string like: DHCP-Relay-Agent-Information = 0x010600040064000002080006000cce477c00 How can I get DHCP-Agent-Circuit-Id and DHCP-Agent-Remote-Id without using perl post_auth ? 2. There is announced feature in 2.1.9 "Add sub-option support for Option 82. See dictionary.dhcp". When I start radiusd -X (2.1.9) with its dictionary.dhcp it begin to eat 100% of CPU with no any output in console after the first dhcp packet received. How to use this announced feature of sub-option for opt82 ? How to find the reason why radiusd (2.1.9) eats 100% of CPU ? My dhcp site config (with changed ip-addresses): server dhcp { listen { ipaddr = 192.168.0.1 port = 67 type = dhcp interface = eth0 } dhcp DHCP-Discover { update reply { DHCP-DHCP-Server-Identifier = "%{Packet-Dst-IP-Address}" } linelog update reply { DHCP-Domain-Name-Server = 192.168.0.1 DHCP-Domain-Name-Server = 192.168.10.1 DHCP-Subnet-Mask = 255.255.255.240 DHCP-IP-Address-Lease-Time = 1800 } mac2ip linelog ok } dhcp DHCP-Request { update reply { DHCP-DHCP-Server-Identifier = "%{Packet-Dst-IP-Address}" } linelog update reply { DHCP-Domain-Name-Server = 192.168.0.1 DHCP-Domain-Name-Server = 192.168.10.1 DHCP-Subnet-Mask = 255.255.255.224 DHCP-IP-Address-Lease-Time = 1800 } linelog ok } dhcp { update reply { DHCP-Message-Type = DHCP-NAK } } } passwd mac2ip { filename = ${confdir}/mac2ip format = "*DHCP-Client-Hardware-Address:=DHCP-Your-IP-Address" delimiter = "," } -- Anton [WARM-RIPE] Stack ltd division head tel. 8 (3822) 555-797

2 3

RADDB 2.1.7 and /etc/shadow
by sbchem 28 May '10

28 May '10

Greetings, I installed a fresh copy of FreeRadius v 2.1.7 on CentOS 5. Ran radtest locally as well as remotely and it works great. Now I want to point the server to my /etc/shadow file which lives on the same machine. I have not made any changes to the default config except to change the group ownership of my shadow file to radiusd so the radius daemon can access it. On startup here is the output: [root@labprinter raddb]# radiusd -X FreeRADIUS Version 2.1.7, for host x86_64-redhat-linux-gnu, built on Mar 31 2010 at 00:14:28 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/radutmp including configuration file /etc/raddb/modules/digest including configuration file /etc/raddb/modules/files including configuration file /etc/raddb/modules/detail.log including configuration file /etc/raddb/modules/mac2vlan including configuration file /etc/raddb/modules/unix including configuration file /etc/raddb/modules/smsotp including configuration file /etc/raddb/modules/linelog including configuration file /etc/raddb/modules/inner-eap including configuration file /etc/raddb/modules/echo including configuration file /etc/raddb/modules/sqlcounter_expire_on_login including configuration file /etc/raddb/modules/sql_log including configuration file /etc/raddb/modules/detail including configuration file /etc/raddb/modules/exec including configuration file /etc/raddb/modules/etc_group including configuration file /etc/raddb/modules/expiration including configuration file /etc/raddb/modules/realm including configuration file /etc/raddb/modules/sradutmp including configuration file /etc/raddb/modules/acct_unique including configuration file /etc/raddb/modules/logintime including configuration file /etc/raddb/modules/perl including configuration file /etc/raddb/modules/ippool including configuration file /etc/raddb/modules/counter including configuration file /etc/raddb/modules/attr_rewrite including configuration file /etc/raddb/modules/policy including configuration file /etc/raddb/modules/passwd including configuration file /etc/raddb/modules/mac2ip including configuration file /etc/raddb/modules/mschap including configuration file /etc/raddb/modules/detail.example.com including configuration file /etc/raddb/modules/preprocess including configuration file /etc/raddb/modules/checkval including configuration file /etc/raddb/modules/chap including configuration file /etc/raddb/modules/pam including configuration file /etc/raddb/modules/expr including configuration file /etc/raddb/modules/always including configuration file /etc/raddb/modules/otp including configuration file /etc/raddb/modules/pap including configuration file /etc/raddb/modules/smbpasswd including configuration file /etc/raddb/modules/cui including configuration file /etc/raddb/modules/attr_filter including configuration file /etc/raddb/modules/wimax 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/inner-tunnel including configuration file /etc/raddb/sites-enabled/default including configuration file /etc/raddb/sites-enabled/control-socket group = radiusd user = radiusd including dictionary file /etc/raddb/dictionary main { prefix = "/usr" localstatedir = "/var" logdir = "/var/log/radius" libdir = "/usr/lib64/freeradius" radacctdir = "/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 allow_core_dumps = no 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 } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } client 10.0.10.0/24 { require_message_authenticator = no secret = "testing123" shortname = "wireless" } 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 = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/var/log/radius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "md5" 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/server.pem" certificate_file = "/etc/raddb/certs/server.pem" CA_file = "/etc/raddb/certs/ca.pem" private_key_password = "whatever" dh_file = "/etc/raddb/certs/dh" random_file = "/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/etc/raddb/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 = no use_tunneled_reply = no 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_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = 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: Checking session {...} for more modules to load 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: 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/raddb/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server { modules { Module: Checking authenticate {...} for more modules to load 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: 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: 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: 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 } # 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. And on authentication here is the output: Going to the next request Waking up in 4.6 seconds. rad_recv: Access-Request packet from host 10.0.10.201 port 32768, id=54, length=381 Acct-Session-Id = "8ac1d4e8-00000085" NAS-Port = 134 NAS-Port-Type = Wireless-802.11 NAS-Identifier = "SG953UZW3J" NAS-IP-Address = 10.0.10.201 Framed-MTU = 1496 User-Name = "support" Calling-Station-Id = "00-26-C6-85-8C-2A" Called-Station-Id = "00-0F-61-53-12-C1" Service-Type = Framed-User EAP-Message = 0x02390070150017030100203ae1e187237e4b81e6caecff83f72c036840674ebf8a5c5a2cf4be6a0c09ea3217030100403b563821ba513e8a7bd18f1f2afc6f375fa289fdcb9a884eaceae4d248a0e49e4c68f0041de02b04defee03e3c7c257803b5593a4d1f4026128d473f025bccc4 State = 0x288bd15e2db2c488b05aedde474bde37 Colubris-AVPair = "ssid=ccsg" Colubris-AVPair = "incoming-vlan-id=432" Colubris-AVPair = "vsc-unique-id=2" Colubris-AVPair = "phytype=IEEE802dot11g" Colubris-Attr-250 = 0x00000000 Colubris-Attr-249 = 0x00000000 Message-Authenticator = 0xd22b50caa56f4af24ae8594256d41aab +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "support", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 57 length 112 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS [ttls] eaptls_verify returned 7 [ttls] Done initial handshake [ttls] eaptls_process returned 7 [ttls] Session established. Proceeding to decode tunneled attributes. [ttls] Got tunneled request User-Name = "support" User-Password = "test" FreeRADIUS-Proxied-To = 127.0.0.1 [ttls] Sending tunneled request User-Name = "support" User-Password = "test" FreeRADIUS-Proxied-To = 127.0.0.1 server inner-tunnel { +- entering group authorize {...} ++[chap] returns noop ++[mschap] returns noop ++[unix] returns notfound [suffix] No '@' in User-Name = "support", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop ++[control] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel [ttls] Got tunneled reply code 3 [ttls] Got tunneled Access-Reject [eap] Handler failed in EAP/ttls [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} -> support attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 8 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 8 Sending Access-Reject of id 54 to 10.0.10.201 port 32768 EAP-Message = 0x04390004 Message-Authenticator = 0x00000000000000000000000000000000 Waking up in 3.6 seconds. Cleaning up request 2 ID 255 with timestamp +166 Cleaning up request 3 ID 167 with timestamp +166 Waking up in 0.2 seconds. Cleaning up request 4 ID 192 with timestamp +166 Cleaning up request 5 ID 246 with timestamp +166 Cleaning up request 6 ID 16 with timestamp +166 Cleaning up request 7 ID 32 with timestamp +166 Waking up in 1.0 seconds. Cleaning up request 8 ID 54 with timestamp +166 Ready to process requests. And yes, there is a user named support with a hashed password that equals "test" Although it looks like the unix module is being queried, it does not look like the server is passing the request to the passwd module The references in the default and inner-tunnel files to shadow are meaningless as they refer to a section in radiusd.comf that does not exist. Any assistance is appreciated. Tom -- View this message in context: http://old.nabble.com/RADDB-2.1.7-and--etc-shadow-tp28640012p28640012.html Sent from the FreeRadius - User mailing list archive at Nabble.com.

6 22

EAP-TLS CN Check Question
by David Mitchell 27 May '10

27 May '10

Greetings, I'm working with the EAP-TLS configuration and one thing I'd like to do is to be able to restrict a certificate to use on a specific device. In most cases, I can get this to work: check_cert_cn = %{User-Name}-%{Calling-Station-Id} However, by default WindowsXP is using the value of CN from the certificate as the username so I get a value which matches check_cert_cn = %{User-Name} making it hard to integrate the Calling-Station-Id into the comparison. Full regexp comparisons don't seem to be available, at least that used to be the case based on my reading of the mailing list archives. Is there some other way to accomplish this? I was thinking if perhaps the certificate attributes ended up in a place where I could perform more thorough unlang comparisons I could get the same effect. The authentication eventually passes through the users file, and the User-Name and Calling-Station-Id should be available there but I don't know if I can access the CN or other certificate attributes there. Does anybody know if this is possible? As a fallback, I can have the XP users jump through more configuration hoops, or put only the Calling-Station-Id into the CN but I do like having the username in there as well. Thanks in advance, -David Mitchell -- ----------------------------------------------------------------- | David Mitchell (mitchell(a)ucar.edu) Network Engineer IV | | Tel: (303) 497-1845 National Center for | | FAX: (303) 497-1818 Atmospheric Research | -----------------------------------------------------------------

2 3

dynamic assignment of VLANs from LDAP via freeradius to WLAN-Clients doesn't work properly
by Meister, Frank 27 May '10

27 May '10

Hello, we have freeradius-2.1.8 running, with openldap-2.3.43 as backend. in ldap we have three attributes (radiusTunnelMediumType=IEEE-802, radiusTunnelType=VLAN, and radiusTunnelPrivateGroupId=[vlan-id]), freeradius maps the ldap-attributes to radius-attributes. We have three vlans, one for staff, one for students and one for guests on the WLAN. after assigning the 1st VLAN on our cisco aironet 1242 accesspoints to the SSID -> clicking Apply, assigning the 2nd VLAN -> click Apply, assigning the 3rd VLAN, click Apply it works fine. (I mean manual assigning VLANs using web-interface) after reboot of the accesspoint it doesn't work anymore. after assign all three VLANs again, one after the other, it works. has anybody an idea about what I'm doing wrong ? the command "aaa authorization network default group radius" from the Cisco-site I tried, but it didn't help further. Thanks for some help, Frank Meister

3 2

still about how to return some attributes only in Access-Accept packet
by weiwei fang 27 May '10

27 May '10

Yesterday, I post a question here: weiwei fang wrote: > Hello, all! > > I want some attributes only sent back to users in Access-Accept packet, > but won't appear in Access-Challenge packet? > > How could I do? Now I just add the attribute in MySQL database, however, > it is also contained in Access-Challenge packet. > Read raddb/sites-available/default, and look for "challenge" > Alan DeKok. I uncommented the following lines in raddb/sites-available/default: # # The older configurations sent a number of attributes in # Access-Challenge packets, which wasn't strictly correct. # If you want to filter out these attributes, uncomment # the following lines. # Auth-Type eap { eap { handled = 1 } if (handled && (Response-Packet-Type == Access-Challenge)) { attr_filter.access_challenge.post-auth handled # override the "updated" code from attr_filter } } } Now I use the EAPMD5 simple example to test it. I add "Framed-MTU = 1500" in the req.txt and then run: radeapclient -x localhost auth testing123 <req.txt As in RFC2865, this attribute "Framed-MTU = 1500" should not returned in the access-challenge packet. however, I can still get it in the access-challenge packet. I don't know why? If I should add something in the raddb/sites-available/attrs.access_challenge file? Thanks a lot for your answer.

5 20

RE: log request to Freeradius server from unknown client
by Yacuk 26 May '10

26 May '10

Hi, David! I am sorry , but i am already have all my radius client in mysql radius\nas database. I don`t want to allow unknown client connect to my Radius server? I just want to log this connection attempt to log file. Thanks. here is debug(skipped some things) =============== freeradius -X FreeRADIUS Version 2.0.4, for host i486-pc-linux-gnu, built on Sep 7 2008 at 23:35:34 Copyright (C) 1999-2008 The FreeRADIUS server project and contributors. 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 configuration file /etc/freeradius/snmp.conf including configuration file /etc/freeradius/sql.conf including configuration file /etc/freeradius/sql/mysql/counter.conf including configuration file /etc/freeradius/sqlippool.conf including configuration file /etc/freeradius/sql/mysql/ippool.conf including configuration file /etc/freeradius/policy.conf including files in directory/etc/freeradius/sites-enabled/ including configuration file /etc/freeradius/sites-enabled/default including dictionary file /etc/freeradius/dictionary main { prefix = "/usr" localstatedir = "/var" logdir = "/var/log/freeradius" libdir = "/usr/lib/freeradius" radacctdir = "/var/log/freeradius/radacct" Module: Linked to module rlm_detail 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 } radiusd: #### Loading Virtual Servers #### server { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = yes require_strong = yes with_ntdomain_hack = no } Module: Instantiating sql sql { driver = "rlm_sql_mysql" server = "localhost" port = "" login = "radius" password = "test123" radius_db = "radius" read_groups = yes sqltrace = no sqltracefile = "/var/log/freeradius/sqltrace.sql" readclients = yes Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on proxy address * port 1814 Ready to process requests. =================================================== Ignoring request to authentication address * port 1812 from unknown client ===========

3 3

another wpa/ldap issue
by Brian Dial 26 May '10

26 May '10

hello everyone, i have a typical wpa + radius + ldap issue. Im using freeradius 2.1.6. i've tried to follow the 'dont edit anything but the ldap module, it will figure it out' mantra as much as possible. i have an openldap server and the test user i'm using has a plain text password. here is my ldap module config ldap { server = "ldap.mydomain.com" identity = "cn=ldapproxy,dc=mydomain,dc=com" password = mypassword basedn = "dc=mydomain,dc=com" filter = "(uid=%{Stripped-User-Name:-%{User-Name}})" ldap_connections_number = 5 timeout = 4 timelimit = 3 net_timeout = 1 tls { start_tls = no } access_attr = "uid" dictionary_mapping = ${confdir}/ldap.attrmap password_attribute = userPassword edir_account_policy_check = no } I found after my first radtest attempt that it wasn't even trying ldap, and because the sites-available/default file had ldap commented out in the authorize section, so I uncommented that (my first change) and running the following command radtest testuser Dirxml1 127.0.0.1 1812 testing123 rad_recv: Access-Request packet from host 127.0.0.1 port 43729, id=226, length=61 User-Name = "testuser" User-Password = "Dirxml1" NAS-IP-Address = 127.0.0.2 NAS-Port = 1812 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[unix] returns notfound ++[files] returns noop [ldap] performing user authorization for testuser [ldap] WARNING: Deprecated conditional expansion ":-". See "man unlang" for details [ldap] expand: (uid=%{Stripped-User-Name:-%{User-Name}}) -> (uid=testuser) [ldap] expand: dc=mydomain,dc=com -> dc=mydomain,dc=com rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: attempting LDAP reconnection rlm_ldap: (re)connect to ldap.mydomain.com:389, authentication 0 rlm_ldap: bind as cn=ldapproxy,dc=mydomain,dc=com/mypassword to ldap.mydomain.com:389 rlm_ldap: waiting for bind result ... rlm_ldap: Bind was successful rlm_ldap: performing search in dc=mydomain,dc=com, with filter (uid=testuser) [ldap] checking if remote access for testuser is allowed by uid [ldap] Added User-Password = Dirxml1 in check items [ldap] No default NMAS login sequence [ldap] looking for check items in directory... [ldap] looking for reply items in directory... [ldap] user testuser authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 ++[ldap] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns updated Found Auth-Type = PAP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!! Replacing User-Password in config items with Cleartext-Password. !!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!! Please update your configuration so that the "known good" !!! !!! clear text password is in Cleartext-Password, and not in User-Password. !!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! +- entering group PAP {...} [pap] login attempt with password "Dirxml1" [pap] Using clear text password "Dirxml1" [pap] User authenticated successfully ++[pap] returns ok +- entering group post-auth {...} ++[exec] returns noop Sending Access-Accept of id 226 to 127.0.0.1 port 43729 so it works, but i figured the big warning should be addressed. wasn't quite sure what to do but i modified the ldap.attrmap and added checkItem Cleartext-Password userPassword and now when i run the radtest there is no error, and it pretty much works the same. Now I setup my cisco 1200 series ap to point to the freeradius server and configured a laptop to try to connect via EAP-TTLS with PAP. Here is the debug rad_recv: Access-Request packet from host 192.168.199.25 port 21648, id=187, length=268 User-Name = "testuser" Framed-MTU = 1400 Called-Station-Id = "0012.7f3f.c4b0" Calling-Station-Id = "0024.2b81.8896" Service-Type = Login-User Message-Authenticator = 0x9320d95b16fe205069287df91cd6b783 EAP-Message = 0x0207008015001703010020d1340dcdcbe734bcc98e3b3fd19f09133ad78d6bd382ab4f4fa95ed5acf6c3a51703010050bd112bf770827d4848cd8f5f4fa9da752a1729a3a6cffce111f651441f7c36e0bb231ef24a8a8ed798b255d9d93ca136be1051f5307d985227f7acb80eb17376e6bab49140907b2d3f91dde05b08a3d4 NAS-Port-Type = Wireless-802.11 NAS-Port = 721 State = 0x8c184d3f891f58a17315ecfba6c3a889 NAS-IP-Address = 192.168.199.25 NAS-Identifier = "rkkap01" +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 7 length 128 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/ttls [eap] processing type ttls [ttls] Authenticate [ttls] processing EAP-TLS [ttls] eaptls_verify returned 7 [ttls] Done initial handshake [ttls] eaptls_process returned 7 [ttls] Session established. Proceeding to decode tunneled attributes. [ttls] Got tunneled request User-Name = "testuser" User-Password = "Dirxmnl1" FreeRADIUS-Proxied-To = 127.0.0.1 [ttls] Sending tunneled request User-Name = "testuser" User-Password = "Dirxmnl1" FreeRADIUS-Proxied-To = 127.0.0.1 server inner-tunnel { +- entering group authorize {...} ++[chap] returns noop ++[mschap] returns noop ++[unix] returns notfound [suffix] No '@' in User-Name = "testuser", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop ++[control] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel [ttls] Got tunneled reply code 3 [ttls] Got tunneled Access-Reject [eap] Handler failed in EAP/ttls [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} -> testuser attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated If I change my username/password on the laptop eap-ttls config to be one i listed in the users file, it works fine so i know that eap-ttls-pap is working correctly. Can someone clue me in where i'm going wrong? "RK&K" and "RK&K Engineers" are registered trade names of Rummel, Klepper & Kahl, LLP, a Maryland limited liability partnership. This message contains confidential information intended only for the person or persons named above. If you have received this message in error, please immediately notify the sender by return email and delete the message. Thank you.

2 2