- Freeradius-Users - lists.freeradius.org

Pool-Name woes with sqlippool
by Simon Earthrowl 18 Feb '09

18 Feb '09

Hi all, I have, what I think is a simple problem, with a simple answer that doesn't work. The environment I am supply authentication requests to, require that I respond with a fixed IP address in each NAS domain. eg NAS-IP-Addresses 192.168.1.0/28 should get an IP from the pool 10.0.0.0/16 While NAS-IP-Addresses 192.168.1.128/28 should get an IP from the 10.1.0.0/16 Users have no control from which of NASs they come into. All the normal user name/password stuff works fine (many thanks!) What I would love to do is set up Huntgroups (OK so that bit works too!) and then in the sqlippool.conf just assign pool-name = %{Huntgroup-Name} This doesn't work, and all I get is pool-name is undefined. Does anyone have any ideas? Kind regards Simon

2 7

Autz-type LDAP, Auth-Type MSCHAP possible ? (for vlan assignment)
by LEOSI 18 Feb '09

18 Feb '09

Hi, I’m trying to set up Freeradius to use the LDAP module for the authorization and process authentication with MSCHAPv2. My goal is to assign vlans from some Organizational Units in AD. I wanted to use into the users files the argument “huntgroups” because it could check OU. Last time I tried MSCHAPv2 for both autz and auth with “ntlm_auth … --require-membership-of” but I could get only 2 vlans (depending is the user is in the group or not). So my question is it possible? And if yes, how to do that? Thanks, My files configuration files : - sites-enabled/default & inner-tunnel authorize { Autz-Type LDAP { ldap } .. ldap } authenticate { .. #Auth-Type LDAP { # ldap #} } - users DEFAULT Autz-Type := LDAP, Auth-Type := MSCHAP - eap.conf eap { default_eap_type = peap .. } peap { default_eap_type = mschapv2 .. } - modules/ldap ldap { server = "test.fr" identity = "cn=bindradius,cn=Users,dc=test,dc=fr" password = bindradius basedn = "cn=Users,dc=test,dc=fr" filter = "(samaccountname=%{User-Name})" .. } password_attribute = userPassword --------------------------------------------------------------------------------- Freeradius server log : --------------------------------------------------------------------------------- Wed Feb 18 11:11:28 2009 : Debug: Ready to process requests. rad_recv: Access-Request packet from host 192.168.1.1 port 1024, id=7, length=202 Framed-MTU = 1480 NAS-IP-Address = 192.168.1.1 NAS-Identifier = "SWiTCH" User-Name = "philippe" Service-Type = Framed-User Framed-Protocol = PPP NAS-Port = 17 NAS-Port-Type = Ethernet NAS-Port-Id = "17" Called-Station-Id = "00-13-21-a8-24-40" Calling-Station-Id = "00-15-c5-06-84-d8" Connect-Info = "CONNECT Ethernet 100Mbps Full duplex" Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "4" EAP-Message = 0x0201000d017068696c69707065 Message-Authenticator = 0x5270b68813d479cb9e13dbb933792913 Wed Feb 18 11:11:39 2009 : Info: +- entering group authorize {...} Wed Feb 18 11:11:39 2009 : Info: ++[preprocess] returns ok Wed Feb 18 11:11:39 2009 : Info: ++[chap] returns noop Wed Feb 18 11:11:39 2009 : Info: ++[mschap] returns noop Wed Feb 18 11:11:39 2009 : Info: [suffix] No '@' in User-Name = "philippe", looking up realm NULL Wed Feb 18 11:11:39 2009 : Info: [suffix] No such realm "NULL" Wed Feb 18 11:11:39 2009 : Info: ++[suffix] returns noop Wed Feb 18 11:11:39 2009 : Info: [eap] EAP packet type response id 1 length 13 Wed Feb 18 11:11:39 2009 : Info: [eap] No EAP Start, assuming it's an on-going EAP conversation Wed Feb 18 11:11:39 2009 : Info: ++[eap] returns updated Wed Feb 18 11:11:39 2009 : Info: ++[unix] returns notfound Wed Feb 18 11:11:39 2009 : Info: [files] users: Matched entry DEFAULT at line 1 Wed Feb 18 11:11:39 2009 : Info: ++[files] returns ok Wed Feb 18 11:11:39 2009 : Info: [ldap] performing user authorization for philippe Wed Feb 18 11:11:39 2009 : Info: [ldap] expand: (samaccountname=%{User-Name}) -> (samaccountname=philippe) Wed Feb 18 11:11:39 2009 : Info: [ldap] expand: cn=Users,dc=test,dc=fr -> cn=Users,dc=test,dc=fr Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: ldap_get_conn: Checking Id: 0 Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: ldap_get_conn: Got Id: 0 Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: attempting LDAP reconnection Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: (re)connect to test.fr:389, authentication 0 Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: bind as cn=bindradius,cn=Users,dc=test,dc=fr/bindradius to test.fr:389 Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: waiting for bind result ... Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: Bind was successful Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: performing search in cn=Users,dc=test,dc=fr, with filter (samaccountname=philippe) Wed Feb 18 11:11:39 2009 : Info: [ldap] looking for check items in directory... Wed Feb 18 11:11:39 2009 : Info: [ldap] looking for reply items in directory... Wed Feb 18 11:11:39 2009 : Debug: WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? Wed Feb 18 11:11:39 2009 : Info: [ldap] user philippe authorized to use remote access Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: ldap_release_conn: Release Id: 0 Wed Feb 18 11:11:39 2009 : Info: ++[ldap] returns ok Wed Feb 18 11:11:39 2009 : Info: ++[expiration] returns noop Wed Feb 18 11:11:39 2009 : Info: ++[logintime] returns noop Wed Feb 18 11:11:39 2009 : Info: [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. Wed Feb 18 11:11:39 2009 : Info: ++[pap] returns noop Wed Feb 18 11:11:39 2009 : Info: Using Autz-Type LDAP Wed Feb 18 11:11:39 2009 : Info: +- entering group LDAP {...} Wed Feb 18 11:11:39 2009 : Info: [ldap] performing user authorization for philippe Wed Feb 18 11:11:39 2009 : Info: [ldap] expand: (samaccountname=%{User-Name}) -> (samaccountname=philippe) Wed Feb 18 11:11:39 2009 : Info: [ldap] expand: cn=Users,dc=test,dc=fr -> cn=Users,dc=test,dc=fr Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: ldap_get_conn: Checking Id: 0 Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: ldap_get_conn: Got Id: 0 Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: performing search in cn=Users,dc=test,dc=fr, with filter (samaccountname=philippe) Wed Feb 18 11:11:39 2009 : Info: [ldap] looking for check items in directory... Wed Feb 18 11:11:39 2009 : Info: [ldap] looking for reply items in directory... Wed Feb 18 11:11:39 2009 : Debug: WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? Wed Feb 18 11:11:39 2009 : Info: [ldap] user philippe authorized to use remote access Wed Feb 18 11:11:39 2009 : Debug: rlm_ldap: ldap_release_conn: Release Id: 0 Wed Feb 18 11:11:39 2009 : Info: ++[ldap] returns ok Wed Feb 18 11:11:39 2009 : Info: Found Auth-Type = MSCHAP Wed Feb 18 11:11:39 2009 : Info: +- entering group MS-CHAP {...} Wed Feb 18 11:11:39 2009 : Info: [mschap] No Cleartext-Password configured. Cannot create LM-Password. Wed Feb 18 11:11:39 2009 : Info: [mschap] No Cleartext-Password configured. Cannot create NT-Password. Wed Feb 18 11:11:39 2009 : Info: [mschap] No MS-CHAP-Challenge in the request Wed Feb 18 11:11:39 2009 : Info: ++[mschap] returns reject Wed Feb 18 11:11:39 2009 : Info: Failed to authenticate the user. Wed Feb 18 11:11:39 2009 : Info: Using Post-Auth-Type Reject Wed Feb 18 11:11:39 2009 : Info: +- entering group REJECT {...} Wed Feb 18 11:11:39 2009 : Info: [attr_filter.access_reject] expand: %{User-Name} -> philippe Wed Feb 18 11:11:39 2009 : Debug: attr_filter: Matched entry DEFAULT at line 11 Wed Feb 18 11:11:39 2009 : Info: ++[attr_filter.access_reject] returns updated Wed Feb 18 11:11:39 2009 : Info: Delaying reject of request 0 for 1 seconds Wed Feb 18 11:11:39 2009 : Debug: Going to the next request Wed Feb 18 11:11:39 2009 : Debug: Waking up in 0.9 seconds. rad_recv: Access-Request packet from host 192.168.1.1 port 1024, id=7, length=202 Wed Feb 18 11:11:40 2009 : Info: Waiting to send Access-Reject to client 192.168.1.1 port 1024 - ID: 7 Wed Feb 18 11:11:40 2009 : Info: Sending delayed reject for request 0 Sending Access-Reject of id 7 to 192.168.1.1 port 1024 Wed Feb 18 11:11:40 2009 : Debug: Waking up in 4.9 seconds. Wed Feb 18 11:11:45 2009 : Info: Cleaning up request 0 ID 7 with timestamp +11 Wed Feb 18 11:11:45 2009 : Debug: Ready to process requests. -- View this message in context: http://www.nabble.com/Autz-type-LDAP%2C-Auth-Type-MSCHAP-possible---%28for-… Sent from the FreeRadius - User mailing list archive at Nabble.com.

2 5

CHAP authentication + FreeRadius + SQL
by Marcelo Freitas 18 Feb '09

18 Feb '09

Hello, I'm trying to authenticate users using CHAP and store the passwords in the SQL, but I'm having a hard time. I checked past messages, but I still couldn't get it to work ... Below is my Access-Request packet Wed Feb 18 12:31:04 2009 Packet-Type = Access-Request NAS-Port-Type = Wireless-802.11 Calling-Station-Id = "000E2EEB1D91" Called-Station-Id = "hotspot1" NAS-Port-Id = "wHotSpotB" User-Name = "admin2" NAS-Port = 2153775219 Acct-Session-Id = "80600073" Framed-IP-Address = 10.5.50.253 Mikrotik-Host-IP = 10.5.50.253 CHAP-Challenge = 0x4f0299d5a5107ded915739e236f71e3c CHAP-Password = 0x606707e3411f443140573554283c987ca5 Service-Type = Login-User WISPr-Logoff-URL = "http://10.5.50.1/logout" NAS-Identifier = "AP_HQ" NAS-IP-Address = 10.0.1.130 In MySQL I just have Cleartext-Password == admin2 for check items ... But I always get Access-Reject. Before checking the past messages, I had already check items like Auth-Type := CHAP, Cleartext-Password == admin2; and also just CHAP-Password, but none of it worked ... Thanks in advance,

2 1

None
by Simon Earthrowl 18 Feb '09

18 Feb '09

Hi, I am trying to configure free radius to work with our 28 NASs. These NASs are split into two groups, at different locations (equal split 14-14). ll NASs report NAS-IP-Address correctly (ie uniquely) Any device requesting authentication randomly connects to any one of the 28 NASs. All devices are unique, and Calling-Station-ID is used to uniquely identify every device. There is no possible chance of multiple instances connecting Some devices *may* require require PAP/CHAP -- the default being ignore User-Name etc. This is configured on a device by device basis. Devices may require an alternative configuration using Called-Station-ID Furthermore, I wish to use MySQL, so that I can add new provisioned devices auto-magically, without needing to tell the radius server. I've a freshly compiled version 2.1.3, running on CentOS 5.3 -- That was by far the easiest bit! Many thanks for that. *Now the problem....* Each set of NASs requires a different Framed-IP-Address pool eg 10.0.0.0/24 for site1, and 10.8.0.0/24 for site2 with Called-Station-Id = domain.com, and 192.168.110.0/26 for site1, and 192.168.110.128/26 for site2 with Called-Station-Id = domain.co.uk I'm using sqlippool to supply the IP. *What I've tried.....* Pool-name : I've set this in huntgroups, hints, clients.conf with no success whatsoever. Pool-Name: In netgroups -- performace was too slow, as I need 28 groups per device! Virtual-Servers: I just don't get these. The README suggests I don't need a listen clause, the debug output suggests I do. I'm concerned that if I go down this route, I'll end up with slow responses again *Where I've got to:* I'm using radcheck table with the Sql-Name set to Calling-Station-ID, with Auth-Type := Accept (for the default case), and adding User-Name & password checking for specific PAP/CHAP authentication. *What I need please* Easiest: A fix, so I can set Pool-Name in clients.conf, or hints, that works in sqlippool. Intermediate: Another strategy that will scale (not 28 groups per device) Or Advanced: A far better understanding of where, and how, I can use unlang, and be able to calculate Pool-Name within a context such that sqlippool will corectly allocate an IP address. Many thanks in anticipation for help/suggestions being offered kind regards Simon

2 4

linking gdbm_compat in rlm_dbm
by Damjan 18 Feb '09

18 Feb '09

I've noticed that the check that ./configure script does in order to find out if gdbm si used only tries to link with gdbm_compat. But the man page of gdbm says: If you wish to use the dbm or ndbm compatibility routines, you must link in the gdbm_compat library as well. For example: gcc -o prog proc.c -lgdbm -lgdbm_compat and indeed on any vanilla system this is the case. Debian, OTOH have patched their libgdbm_compat. -- damjan | дамјан This is my jabber ID --> damjan(a)bagra.net.mk -- not my mail address, it's a Jabber ID --^ :)

2 1

FW: wimax.c
by dave anderson 17 Feb '09

17 Feb '09

-----Original Message----- From: dave anderson Sent: February 13, 2009 5:14 PM To: freeradius-users Subject: FW: wimax.c I have the Wimax FreeRadius (2.1.3) working but I am a bit unclear on a few key reply parameters: In the default server I have added update "reply"{ WiMAX-MSK = �%{reply:EAP-MSK}� Which successfully produces the right length MSK in the reply. However to populate these other variable into the reply such as Session reply, it is not clear how to do so: WiMAX-AAA-Session-ID = ? WiMAX-HA-RK-SPI = ? WiMAX-HA-RK-Lifetime = ? How to I get the reply to include these with correct values ? Further, putting WiMAX-MN-NAI = �%{User-Name}� in the default config prior to calling the wimax function still results in the WiMAX module warning that WiMAX-MN-NAI has not been set. Would anyone have advice on how to resolve these two issues? Thanks Dave Anderson

2 8

Freeradius with OpenLDAP and AD.
by LEOSI 17 Feb '09

17 Feb '09

Hi, I have several problems when I would like to link freeradius with AD using OpenLDAP. When I tried to test the binding of OpenLDAP to the AD with radtest, it responds Access-Accept (as you can see in the log after). But when I wanted to check with a real supplicant (under WinXP with MD5-Challenge Auth) I got an access-reject. Things I changed : - modules/ldap : ldap { server = "test.fr" identity = "cn=bindradius,cn=Users,dc=test,dc=fr" password = bindradius basedn = "cn=Users,dc=test,dc=fr" filter = "(samaccountname=%{User-Name})" .. } password_attribute = userPassword - site-enabled/default & inner-tunnel : authorize { .. # uncommented : ldap .. } authenticate { .. # uncommented : Auth-Type LDAP { ldap } Thanks for your help --------------------------------------------------------------------------------- Radtest : --------------------------------------------------------------------------------- root@freeradius:~# radtest philippe philippe localhost 0 testing123 Sending Access-Request of id 50 to 127.0.0.1 port 1812 User-Name = "philippe" User-Password = "philippe" NAS-IP-Address = 192.168.1.3 NAS-Port = 0 rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=50, length=20 --------------------------------------------------------------------------------- Freeradius log with radtest : --------------------------------------------------------------------------------- rad_recv: Access-Request packet from host 127.0.0.1 port 47525, id=50, length=60 User-Name = "philippe" User-Password = "philippe" NAS-IP-Address = 192.168.1.3 NAS-Port = 0 [..] Tue Feb 17 15:38:25 2009 : Info: [ldap] performing user authorization for philippe Tue Feb 17 15:38:25 2009 : Info: [ldap] expand: (samaccountname=%{User-Name}) -> (samaccountname=philippe) Tue Feb 17 15:38:25 2009 : Info: [ldap] expand: cn=Users,dc=test,dc=fr -> cn=Users,dc=test,dc=fr Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: ldap_get_conn: Checking Id: 0 Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: ldap_get_conn: Got Id: 0 Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: attempting LDAP reconnection Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: (re)connect to test.fr:389, authentication 0 Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: bind as cn=bindradius,cn=Users,dc=test,dc=fr/bindradius to test.fr:389 Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: waiting for bind result ... Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: Bind was successful Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: performing search in cn=Users,dc=test,dc=fr, with filter (samaccountname=philippe) Tue Feb 17 15:38:25 2009 : Info: [ldap] looking for check items in directory... Tue Feb 17 15:38:25 2009 : Info: [ldap] looking for reply items in directory... Tue Feb 17 15:38:25 2009 : Debug: WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? Tue Feb 17 15:38:25 2009 : Info: [ldap] user philippe authorized to use remote access Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: ldap_release_conn: Release Id: 0 Tue Feb 17 15:38:25 2009 : Info: ++[ldap] returns ok [..] Tue Feb 17 15:38:25 2009 : Info: Found Auth-Type = LDAP Tue Feb 17 15:38:25 2009 : Info: +- entering group LDAP {...} Tue Feb 17 15:38:25 2009 : Info: [ldap] login attempt by "philippe" with password "philippe" Tue Feb 17 15:38:25 2009 : Info: [ldap] user DN: CN=philippe,CN=Users,DC=test,DC=fr Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: (re)connect to test.fr:389, authentication 1 Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: bind as CN=philippe,CN=Users,DC=test,DC=fr/philippe to test.fr:389 Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: waiting for bind result ... Tue Feb 17 15:38:25 2009 : Debug: rlm_ldap: Bind was successful Tue Feb 17 15:38:25 2009 : Info: [ldap] user philippe authenticated succesfully [..] Sending Access-Accept of id 50 to 127.0.0.1 port 47525 --------------------------------------------------------------------------------- With a real supplicant : --------------------------------------------------------------------------------- Tue Feb 17 15:40:50 2009 : Debug: Ready to process requests. rad_recv: Access-Request packet from host 192.168.1.1 port 1024, id=5, length=202 Framed-MTU = 1480 NAS-IP-Address = 192.168.1.1 NAS-Identifier = "SWiTCH" User-Name = "philippe" Service-Type = Framed-User Framed-Protocol = PPP NAS-Port = 21 NAS-Port-Type = Ethernet NAS-Port-Id = "21" Called-Station-Id = "00-13-21-a8-24-40" Calling-Station-Id = "00-15-c5-06-84-d8" Connect-Info = "CONNECT Ethernet 100Mbps Full duplex" Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "4" EAP-Message = 0x0201000d017068696c69707065 Message-Authenticator = 0x2e787b9c5fea331ecfc02e8c3b85c55c Tue Feb 17 15:41:28 2009 : Info: +- entering group authorize {...} Tue Feb 17 15:41:28 2009 : Info: ++[preprocess] returns ok Tue Feb 17 15:41:28 2009 : Info: ++[chap] returns noop Tue Feb 17 15:41:28 2009 : Info: ++[mschap] returns noop Tue Feb 17 15:41:28 2009 : Info: [suffix] No '@' in User-Name = "philippe", looking up realm NULL Tue Feb 17 15:41:28 2009 : Info: [suffix] No such realm "NULL" Tue Feb 17 15:41:28 2009 : Info: ++[suffix] returns noop Tue Feb 17 15:41:28 2009 : Info: [eap] EAP packet type response id 1 length 13 Tue Feb 17 15:41:28 2009 : Info: [eap] No EAP Start, assuming it's an on-going EAP conversation Tue Feb 17 15:41:28 2009 : Info: ++[eap] returns updated Tue Feb 17 15:41:28 2009 : Info: ++[unix] returns notfound Tue Feb 17 15:41:28 2009 : Info: [files] users: Matched entry DEFAULT at line 1 Tue Feb 17 15:41:28 2009 : Info: ++[files] returns ok Tue Feb 17 15:41:28 2009 : Info: [ldap] performing user authorization for philippe Tue Feb 17 15:41:28 2009 : Info: [ldap] expand: (samaccountname=%{User-Name}) -> (samaccountname=philippe) Tue Feb 17 15:41:28 2009 : Info: [ldap] expand: cn=Users,dc=test,dc=fr -> cn=Users,dc=test,dc=fr Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: ldap_get_conn: Checking Id: 0 Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: ldap_get_conn: Got Id: 0 Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: attempting LDAP reconnection Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: (re)connect to test.fr:389, authentication 0 Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: bind as cn=bindradius,cn=Users,dc=test,dc=fr/bindradius to test.fr:389 Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: waiting for bind result ... Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: Bind was successful Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: performing search in cn=Users,dc=test,dc=fr, with filter (samaccountname=philippe) Tue Feb 17 15:41:28 2009 : Info: [ldap] looking for check items in directory... Tue Feb 17 15:41:28 2009 : Info: [ldap] looking for reply items in directory... Tue Feb 17 15:41:28 2009 : Debug: WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? Tue Feb 17 15:41:28 2009 : Info: [ldap] user philippe authorized to use remote access Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: ldap_release_conn: Release Id: 0 Tue Feb 17 15:41:28 2009 : Info: ++[ldap] returns ok Tue Feb 17 15:41:28 2009 : Info: ++[expiration] returns noop Tue Feb 17 15:41:28 2009 : Info: ++[logintime] returns noop Tue Feb 17 15:41:28 2009 : Info: [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. Tue Feb 17 15:41:28 2009 : Info: ++[pap] returns noop Tue Feb 17 15:41:28 2009 : Info: Found Auth-Type = EAP Tue Feb 17 15:41:28 2009 : Info: +- entering group authenticate {...} Tue Feb 17 15:41:28 2009 : Info: [eap] EAP Identity Tue Feb 17 15:41:28 2009 : Info: [eap] processing type md5 Tue Feb 17 15:41:28 2009 : Debug: rlm_eap_md5: Issuing Challenge Tue Feb 17 15:41:28 2009 : Info: ++[eap] returns handled Sending Access-Challenge of id 5 to 192.168.1.1 port 1024 EAP-Message = 0x01020016041005f180280d72810cb4b1b9fa2033ede2 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x89d76e5089d56a6c48de80e818248c16 Tue Feb 17 15:41:28 2009 : Info: Finished request 0. Tue Feb 17 15:41:28 2009 : Debug: Going to the next request Tue Feb 17 15:41:28 2009 : Debug: Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.1.1 port 1024, id=6, length=237 Framed-MTU = 1480 NAS-IP-Address = 192.168.1.1 NAS-Identifier = "SWiTCH" User-Name = "philippe" Service-Type = Framed-User Framed-Protocol = PPP NAS-Port = 21 NAS-Port-Type = Ethernet NAS-Port-Id = "21" Called-Station-Id = "00-13-21-a8-24-40" Calling-Station-Id = "00-15-c5-06-84-d8" Connect-Info = "CONNECT Ethernet 100Mbps Full duplex" Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 Tunnel-Private-Group-Id:0 = "4" State = 0x89d76e5089d56a6c48de80e818248c16 EAP-Message = 0x0202001e041046b39f2ac453deec1f14d2b599506e377068696c69707065 Message-Authenticator = 0x57f0fce82988e78eeb9bc719d015033d Tue Feb 17 15:41:28 2009 : Info: +- entering group authorize {...} Tue Feb 17 15:41:28 2009 : Info: ++[preprocess] returns ok Tue Feb 17 15:41:28 2009 : Info: ++[chap] returns noop Tue Feb 17 15:41:28 2009 : Info: ++[mschap] returns noop Tue Feb 17 15:41:28 2009 : Info: [suffix] No '@' in User-Name = "philippe", looking up realm NULL Tue Feb 17 15:41:28 2009 : Info: [suffix] No such realm "NULL" Tue Feb 17 15:41:28 2009 : Info: ++[suffix] returns noop Tue Feb 17 15:41:28 2009 : Info: [eap] EAP packet type response id 2 length 30 Tue Feb 17 15:41:28 2009 : Info: [eap] No EAP Start, assuming it's an on-going EAP conversation Tue Feb 17 15:41:28 2009 : Info: ++[eap] returns updated Tue Feb 17 15:41:28 2009 : Info: ++[unix] returns notfound Tue Feb 17 15:41:28 2009 : Info: [files] users: Matched entry DEFAULT at line 1 Tue Feb 17 15:41:28 2009 : Info: ++[files] returns ok Tue Feb 17 15:41:28 2009 : Info: [ldap] performing user authorization for philippe Tue Feb 17 15:41:28 2009 : Info: [ldap] expand: (samaccountname=%{User-Name}) -> (samaccountname=philippe) Tue Feb 17 15:41:28 2009 : Info: [ldap] expand: cn=Users,dc=test,dc=fr -> cn=Users,dc=test,dc=fr Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: ldap_get_conn: Checking Id: 0 Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: ldap_get_conn: Got Id: 0 Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: performing search in cn=Users,dc=test,dc=fr, with filter (samaccountname=philippe) Tue Feb 17 15:41:28 2009 : Info: [ldap] looking for check items in directory... Tue Feb 17 15:41:28 2009 : Info: [ldap] looking for reply items in directory... Tue Feb 17 15:41:28 2009 : Debug: WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? Tue Feb 17 15:41:28 2009 : Info: [ldap] user philippe authorized to use remote access Tue Feb 17 15:41:28 2009 : Debug: rlm_ldap: ldap_release_conn: Release Id: 0 Tue Feb 17 15:41:28 2009 : Info: ++[ldap] returns ok Tue Feb 17 15:41:28 2009 : Info: ++[expiration] returns noop Tue Feb 17 15:41:28 2009 : Info: ++[logintime] returns noop Tue Feb 17 15:41:28 2009 : Info: [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. Tue Feb 17 15:41:28 2009 : Info: ++[pap] returns noop Tue Feb 17 15:41:28 2009 : Info: Found Auth-Type = EAP Tue Feb 17 15:41:28 2009 : Info: +- entering group authenticate {...} Tue Feb 17 15:41:28 2009 : Info: [eap] Request found, released from the list Tue Feb 17 15:41:28 2009 : Info: [eap] EAP/md5 Tue Feb 17 15:41:28 2009 : Info: [eap] processing type md5 Tue Feb 17 15:41:28 2009 : Debug: rlm_eap_md5: Cleartext-Password is required for EAP-MD5 authentication Tue Feb 17 15:41:28 2009 : Info: [eap] Handler failed in EAP/md5 Tue Feb 17 15:41:28 2009 : Info: [eap] Failed in EAP select Tue Feb 17 15:41:28 2009 : Info: ++[eap] returns invalid Tue Feb 17 15:41:28 2009 : Info: Failed to authenticate the user. Tue Feb 17 15:41:28 2009 : Info: Using Post-Auth-Type Reject Tue Feb 17 15:41:28 2009 : Info: +- entering group REJECT {...} Tue Feb 17 15:41:28 2009 : Info: [attr_filter.access_reject] expand: %{User-Name} -> philippe Tue Feb 17 15:41:28 2009 : Debug: attr_filter: Matched entry DEFAULT at line 11 Tue Feb 17 15:41:28 2009 : Info: ++[attr_filter.access_reject] returns updated Tue Feb 17 15:41:28 2009 : Info: Delaying reject of request 1 for 1 seconds Tue Feb 17 15:41:28 2009 : Debug: Going to the next request Tue Feb 17 15:41:28 2009 : Debug: Waking up in 0.9 seconds. rad_recv: Access-Request packet from host 192.168.1.1 port 1024, id=6, length=237 Tue Feb 17 15:41:29 2009 : Info: Waiting to send Access-Reject to client 192.168.1.1 port 1024 - ID: 6 Tue Feb 17 15:41:29 2009 : Info: Sending delayed reject for request 1 Sending Access-Reject of id 6 to 192.168.1.1 port 1024 EAP-Message = 0x04020004 Message-Authenticator = 0x00000000000000000000000000000000 Tue Feb 17 15:41:29 2009 : Debug: Waking up in 3.9 seconds. Tue Feb 17 15:41:33 2009 : Info: Cleaning up request 0 ID 5 with timestamp +38 Tue Feb 17 15:41:33 2009 : Debug: Waking up in 0.9 seconds. Tue Feb 17 15:41:34 2009 : Info: Cleaning up request 1 ID 6 with timestamp +38 Tue Feb 17 15:41:34 2009 : Debug: Ready to process requests. -- View this message in context: http://www.nabble.com/Freeradius-with-OpenLDAP-and-AD.-tp22058186p22058186.… Sent from the FreeRadius - User mailing list archive at Nabble.com.

4 4

No authenticate method using Mysql
by Pedro Henrique Mazzoni 17 Feb '09

17 Feb '09

Hello, I am trying to use mysql and Freeradius for AAA. The communication between freeradius and mysql server seems OK, since Freeradius is getting the clients from radclients table. When I do a test from the command line: "radtest user1 pass localhost 1812 shared" I got the output: "rad_recv: Access-Request packet from host 127.0.0.1 port 56962, id=152, length=57 User-Name = "user1" User-Password = "pass" NAS-IP-Address = 127.0.1.1 NAS-Port = 1812 Mon Feb 16 17:22:09 2009 : Info: No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Mon Feb 16 17:22:09 2009 : Info: Failed to authenticate the user. Mon Feb 16 17:22:09 2009 : Info: Using Post-Auth-Type Reject Mon Feb 16 17:22:09 2009 : Debug: WARNING: Unknown value specified for Post-Auth-Type. Cannot perform requested action. Mon Feb 16 17:22:09 2009 : Info: Delaying reject of request 1 for 1 seconds Mon Feb 16 17:22:09 2009 : Debug: Going to the next request Mon Feb 16 17:22:09 2009 : Debug: Waking up in 0.9 seconds. Mon Feb 16 17:22:11 2009 : Info: Sending delayed reject for request 1 Sending Access-Reject of id 152 to 127.0.0.1 port 56962 Mon Feb 16 17:22:11 2009 : Debug: Waking up in 4.9 seconds. " Following is my configuration file(please note that this is only the file in sites-avaiable dir, note radiusd.conf): "###################################################################### # # As of 2.0.0, FreeRADIUS supports virtual hosts using the # "server" section, and configuration directives. # # Virtual hosts should be put into the "sites-available" # directory. Soft links should be created in the "sites-enabled" # directory to these files. This is done in a normal installation. # # $Id$ # ###################################################################### # # Read "man radiusd" before editing this file. See the section # titled DEBUGGING. It outlines a method where you can quickly # obtain the configuration you want, without running into # trouble. See also "man unlang", which documents the format # of this file. # # This configuration is designed to work in the widest possible # set of circumstances, with the widest possible number of # authentication methods. This means that in general, you should # need to make very few changes to this file. # # The best way to configure the server for your local system # is to CAREFULLY edit this file. Most attempts to make large # edits to this file will BREAK THE SERVER. Any edits should # be small, and tested by running the server with "radiusd -X". # Once the edits have been verified to work, save a copy of these # configuration files somewhere. (e.g. as a "tar" file). Then, # make more edits, and test, as above. # # There are many "commented out" references to modules such # as ldap, sql, etc. These references serve as place-holders. # If you need the functionality of that module, then configure # it in radiusd.conf, and un-comment the references to it in # this file. In most cases, those small changes will result # in the server being able to connect to the DB, and to # authenticate users. # ###################################################################### server intelitiva.com { # # In 1.x, the "authorize", etc. sections were global in # radiusd.conf. As of 2.0, they SHOULD be in a server section. # # The server section with no virtual server name is the "default" # section. It is used when no server name is specified. # # We don't indent the rest of this file, because doing so # would make it harder to read. # # Authorization. First preprocess (hints and huntgroups files), # then realms, and finally look in the "users" file. # # The order of the realm modules will determine the order that # we try to find a matching realm. # # Make *sure* that 'preprocess' comes before any realm if you # need to setup hints for the remote radius server authorize { # # The preprocess module takes care of sanitizing some bizarre # attributes in the request, and turning them into attributes # which are more standard. # # It takes care of processing the 'raddb/hints' and the # 'raddb/huntgroups' files. # # It also adds the %{Client-IP-Address} attribute to the request. preprocess # # If you want to have a log of authentication requests, # un-comment the following line, and the 'detail auth_log' # section, above. #auth_log # # The chap module will set 'Auth-Type := CHAP' if we are # handling a CHAP request and Auth-Type has not already been set chap # # If the users are logging in with an MS-CHAP-Challenge # attribute for authentication, the mschap module will find # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP' # to the request, which will cause the server to then use # the mschap module for authentication. mschap # # If you have a Cisco SIP server authenticating against # FreeRADIUS, uncomment the following line, and the 'digest' # line in the 'authenticate' section. # digest # # Look for IPASS style 'realm/', and if not found, look for # '@realm', and decide whether or not to proxy, based on # that. # IPASS # # If you are using multiple kinds of realms, you probably # want to set "ignore_null = yes" for all of them. # Otherwise, when the first style of realm doesn't match, # the other styles won't be checked. # # suffix # ntdomain # # This module takes care of EAP-MD5, EAP-TLS, and EAP-LEAP # authentication. # # It also sets the EAP-Type attribute in the request # attribute list to the EAP type from the packet. # # As of 2.0, the EAP module returns "ok" in the authorize stage # for TTLS and PEAP. In 1.x, it never returned "ok" here, so # this change is compatible with older configurations. # # The example below uses module failover to avoid querying all # of the following modules if the EAP module returns "ok". # Therefore, your LDAP and/or SQL servers will not be queried # for the many packets that go back and forth to set up TTLS # or PEAP. The load on those servers will therefore be reduced. # # eap { # ok = return # } # # Look in an SQL database. The schema of the database # is meant to mirror the "users" file. # # See "Authorization Queries" in sql.conf sql # # Pull crypt'd passwords from /etc/passwd or /etc/shadow, # using the system API's to get the password. If you want # to read /etc/passwd or /etc/shadow directly, see the # passwd module in radiusd.conf. # # unix # # Read the 'users' file # files # # If you are using /etc/smbpasswd, and are also doing # mschap authentication, the un-comment this line, and # configure the 'etc_smbpasswd' module, above. # etc_smbpasswd # # The ldap module will set Auth-Type to LDAP if it has not # already been set # ldap # # Enforce daily limits on time spent logged in. # daily # # Use the checkval module # checkval # expiration # logintime # # If no other module has claimed responsibility for # authentication, then try to use PAP. This allows the # other modules listed above to add a "known good" password # to the request, and to do nothing else. The PAP module # will then see that password, and use it to do PAP # authentication. # # This module should be listed last, so that the other modules # get a chance to set Auth-Type for themselves. # # pap # # If "status_server = yes", then Status-Server messages are passed # through the following section, and ONLY the following section. # This permits you to do DB queries, for example. If the modules # listed here return "fail", then NO response is sent. # # Autz-Type Status-Server { # # } } # Authentication. # # # This section lists which modules are available for authentication. # Note that it does NOT mean 'try each module in order'. It means # that a module from the 'authorize' section adds a configuration # attribute 'Auth-Type := FOO'. That authentication type is then # used to pick the apropriate module from the list below. # # In general, you SHOULD NOT set the Auth-Type attribute. The server # will figure it out on its own, and will do the right thing. The # most common side effect of erroneously setting the Auth-Type # attribute is that one authentication method will work, but the # others will not. # # The common reasons to set the Auth-Type attribute by hand # is to either forcibly reject the user (Auth-Type := Reject), # or to or forcibly accept the user (Auth-Type := Accept). # # Note that Auth-Type := Accept will NOT work with EAP. # # Please do not put "unlang" configurations into the "authenticate" # section. Put them in the "post-auth" section instead. That's what # the post-auth section is for. # authenticate { # # PAP authentication, when a back-end database listed # in the 'authorize' section supplies a password. The # password can be clear-text, or encrypted. Auth-Type PAP { pap } # # Most people want CHAP authentication # A back-end database listed in the 'authorize' section # MUST supply a CLEAR TEXT password. Encrypted passwords # won't work. Auth-Type CHAP { chap } # # MSCHAP authentication. Auth-Type MS-CHAP { mschap } # # If you have a Cisco SIP server authenticating against # FreeRADIUS, uncomment the following line, and the 'digest' # line in the 'authorize' section. # digest # # Pluggable Authentication Modules. # pam # # See 'man getpwent' for information on how the 'unix' # module checks the users password. Note that packets # containing CHAP-Password attributes CANNOT be authenticated # against /etc/passwd! See the FAQ for details. # # unix # Uncomment it if you want to use ldap for authentication # # Note that this means "check plain-text password against # the ldap database", which means that EAP won't work, # as it does not supply a plain-text password. # Auth-Type LDAP { # ldap # } # # Allow EAP authentication. # eap } # # Pre-accounting. Decide which accounting type to use. # preacct { preprocess # # Ensure that we have a semi-unique identifier for every # request, and many NAS boxes are broken. acct_unique # # Look for IPASS-style 'realm/', and if not found, look for # '@realm', and decide whether or not to proxy, based on # that. # # Accounting requests are generally proxied to the same # home server as authentication requests. # IPASS suffix # ntdomain # # Read the 'acct_users' file files } # # Accounting. Log the accounting data. # accounting { # # Create a 'detail'ed log of the packets. # Note that accounting requests which are proxied # are also logged in the detail file. detail # daily # Update the wtmp file # # If you don't use "radlast", you can delete this line. unix # # For Simultaneous-Use tracking. # # Due to packet losses in the network, the data here # may be incorrect. There is little we can do about it. radutmp # sradutmp # Return an address to the IP Pool when we see a stop record. # main_pool # # Log traffic to an SQL database. # # See "Accounting queries" in sql.conf sql # # Instead of sending the query to the SQL server, # write it into a log file. # # sql_log # Cisco VoIP specific bulk accounting # pgsql-voip # Filter attributes from the accounting response. attr_filter.accounting_response # # See "Autz-Type Status-Server" for how this works. # # Acct-Type Status-Server { # # } } # Session database, used for checking Simultaneous-Use. Either the radutmp # or rlm_sql module can handle this. # The rlm_sql module is *much* faster session { radutmp # # See "Simultaneous Use Checking Queries" in sql.conf sql } # Post-Authentication # Once we KNOW that the user has been authenticated, there are # additional steps we can take. post-auth { # Get an address from the IP Pool. # main_pool # # If you want to have a log of authentication replies, # un-comment the following line, and the 'detail reply_log' # section, above. # reply_log # # After authenticating the user, do another SQL query. # # See "Authentication Logging Queries" in sql.conf sql # # Instead of sending the query to the SQL server, # write it into a log file. # # sql_log # # Un-comment the following if you have set # 'edir_account_policy_check = yes' in the ldap module sub-section of # the 'modules' section. # # ldap exec # # Access-Reject packets are sent through the REJECT sub-section of the # post-auth section. # # Add the ldap module name (or instance) if you have set # 'edir_account_policy_check = yes' in the ldap module configuration # Post-Auth-Type REJECT { attr_filter.access_reject } } # # When the server decides to proxy a request to a home server, # the proxied request is first passed through the pre-proxy # stage. This stage can re-write the request, or decide to # cancel the proxy. # # Only a few modules currently have this method. # pre-proxy { # attr_rewrite # Uncomment the following line if you want to change attributes # as defined in the preproxy_users file. # files # Uncomment the following line if you want to filter requests # sent to remote servers based on the rules defined in the # 'attrs.pre-proxy' file. # attr_filter.pre-proxy # If you want to have a log of packets proxied to a home # server, un-comment the following line, and the # 'detail pre_proxy_log' section, above. # pre_proxy_log } # # When the server receives a reply to a request it proxied # to a home server, the request may be massaged here, in the # post-proxy stage. # post-proxy { # If you want to have a log of replies from a home server, # un-comment the following line, and the 'detail post_proxy_log' # section, above. # post_proxy_log # attr_rewrite # Uncomment the following line if you want to filter replies from # remote proxies based on the rules defined in the 'attrs' file. # attr_filter.post-proxy # # If you are proxying LEAP, you MUST configure the EAP # module, and you MUST list it here, in the post-proxy # stage. # # You MUST also use the 'nostrip' option in the 'realm' # configuration. Otherwise, the User-Name attribute # in the proxied request will not match the user name # hidden inside of the EAP packet, and the end server will # reject the EAP request. # eap # # If the server tries to proxy a request and fails, then the # request is processed through the modules in this section. # # The main use of this section is to permit robust proxying # of accounting packets. The server can be configured to # proxy accounting packets as part of normal processing. # Then, if the home server goes down, accounting packets can # be logged to a local "detail" file, for processing with # radrelay. When the home server comes back up, radrelay # will read the detail file, and send the packets to the # home server. # # With this configuration, the server always responds to # Accounting-Requests from the NAS, but only writes # accounting packets to disk if the home server is down. # # Post-Proxy-Type Fail { # detail # } } }" Any ideas? Thanks in advance, Pedro Mazzoni

4 5

Using accounting data for quotas
by Jonathan Gazeley 17 Feb '09

17 Feb '09

I'm trying to find a way to extract useful data from accounting logs to use towards a quota. I'm a bit stuck and I'm wondering if anyone has tried anything similar with success. Let me explain... My accounting logs are sent to SQL with the inner ID. Periodically, the NAS updates the accounting record with total of upload and download during that session. I've tweaked the FR queries so they also update a new field called 'lastupdatetime'. I want to write an hourly script that will tell me (eg in a CSV file) how much traffic has been done for each username (not necessarily each session) during the last hour. Clearly this will take some sort of hourly summary that can be compared each hour. But it is still not straightforward: - Some sessions remain open for weeks. - Some users have multiple simultaneous or multiple sequential sessions. - The updates come in at different times. - The traffic counters will roll over from time to time. - It's not possible to query hourly on how traffic the user has used since forever, because records older than around 90 days are dropped. Any ideas? Or am I barking up completely the wrong tree... Cheers, Jonathan ---------------------------- Jonathan Gazeley Systems Support Specialist ResNet | Wireless & VPN Team Information Services University of Bristol ----------------------------

3 2

reference client stanzas in unlang?
by Stefan Winter 17 Feb '09

17 Feb '09

Hi, is there a way to reference the name of the client stanza (or its shortname) in unlang? I.e. if there is client foo { ipaddr = 1.2.3.4 shortname = foostuff } Then there's a request coming in from this client. In the client processing, can there be sth like if ( -- something that reveals "foo" or "foostuff" -- ) { ... } ? Using huntgroups and assigning Client-IP-Address into huntgroups is procedurally not an option. Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473

3 2