- Freeradius-Users - lists.freeradius.org

Best Practices - maximum NAS entries in clients.conf
by Sallee, Stephen (Jake) 13 Sep '11

13 Sep '11

@ everyone We have about 100 NAS entries in our clients.conf file, it makes the file a bear to deal with but the server seems to handle it fine. We will be expanding our infrastructure soon and the number of NAS entries will increase significantly. At what point should we think about putting them into a database for FR to use? Also, I have seen some chatter on the list about dynamic NASs. Am I correct in assuming that if we are using a DB instead of the clients.conf file we can add or remove clients simply by making changes to the correct table, all without having to restart FR? Jake Sallee Godfather of Bandwidth Network Engineer University of Mary Hardin-Baylor 900 College St. Belton, Texas 76513 Fone: 254-295-4658 Phax: 254-295-4221

8 20

Failure to activate mysql
by Majid Dadashi 13 Sep '11

13 Sep '11

Hi, I have the following platform: FreeRadius Version: freeradius-server-2.1.11 OS: Ubuntu 11.04 I did all the instructions in "http://wiki.freeradius.org/SQL-HOWTO" to activate mysql in free radius, but I get the following error: Could not link driver rlm_sql_mysql: rlm_sql_mysql.so: cannot open shared object file: No such file or directory Make sure it (and all its dependent libraries!) are in the search path of your system's ld. /usr/local/etc/raddb/sql.conf[22]: Instantiation failed for module "sql" /usr/local/etc/raddb/sites-enabled/default[166]: Failed to load module "sql". /usr/local/etc/raddb/sites-enabled/default[69]: Errors parsing authorize section. I just have a file named "rlm_sql_mysql.so" in the following address: "./src/modules/rlm_sql/drivers/rlm_sql_mysql" what do you think is the problem? Cheers

3 4

Re: First Run Problem
by Alan Buxey 13 Sep '11

13 Sep '11

Hi, Good to know, no problem alan

1 0

Re: NAS IP Address
by 2394263740 13 Sep '11

13 Sep '11

Arran, Yes. You're right. It works. Great! Thanks! Tom ------------------ Original ------------------ From: "a.cudbardb"<a.cudbardb(a)freeradius.org>; Date: Tue, Sep 13, 2011 03:56 PM To: "2394263740"<2394263740(a)qq.com>; Subject: Re: NAS IP Address Ah you want the attribute Packet-Src-IP-Address -Arran On 13 Sep 2011, at 03:55, 2394263740 wrote: Arran, Looks like the email didn't go through sometime. Please see below email for my question. Thanks! Tom ------------------ Original ------------------ From: "2394263740"<2394263740(a)qq.com>; Date: Tue, Sep 13, 2011 09:28 AM To: "freeradius-users"<freeradius-users(a)lists.freeradius.org>; Subject: Re:NAS IP Address Arran, Thanks for your help and reply. %{NAS-IP-Address} doesn't work for this case. The connection like below. Mobile --- WiFi Router --- Internet Gateway (NAT) ---Internet --- FreeRadius Server. The %{NAS-IP-Address} will be the LAN interfact IP, such as 192.168.1.1. This is not I need. I need the IP address, with such IP address, FreeRadius Server is communicating. This means, when FreeRadius receive the access request, the request IP packet was sourced from the Internet Gateway IP address, and this is the IP address I need. Inside the access request, there is %{NAS-IP-Address}, it's the LAN IP address of the WIFI router, %{NAS-IP-Address} is not the information I need in such case. Thanks! Tom ------------------ Original ------------------ From: "freeradius-users"<freeradius-users-request(a)lists.freeradius.org>; Date: Mon, Sep 12, 2011 10:44 PM To: "freeradius-users"<freeradius-users(a)lists.freeradius.org>; Subject: Freeradius-Users Digest, Vol 77, Issue 42 Send Freeradius-Users mailing list submissions to freeradius-users(a)lists.freeradius.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freeradius.org/mailman/listinfo/freeradius-users or, via email, send a message with subject or body 'help' to freeradius-users-request(a)lists.freeradius.org You can reach the person managing the list at freeradius-users-owner(a)lists.freeradius.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Freeradius-Users digest..." Today's Topics: 1. NAS IP Address ( 2394263740 ) 2. Re: NAS IP Address (Arran Cudbard-Bell) 3. Best Practices - maximum NAS entries in clients.conf (Sallee, Stephen (Jake)) 4. Re: Best Practices - maximum NAS entries in clients.conf (Alan DeKok) 5. Re: Best Practices - maximum NAS entries in clients.conf (Arran Cudbard-Bell) 6. Re: Best Practices - maximum NAS entries in clients.conf (Arran Cudbard-Bell) 7. Re: Best Practices - maximum NAS entries in clients.conf (Bruce Nunn) 8. Unable to Authenticate with SHA Password (Rajkumar balaji) ---------------------------------------------------------------------- Message: 1 Date: Mon, 12 Sep 2011 19:58:18 +0800 From: " 2394263740 " <2394263740(a)qq.com> Subject: NAS IP Address To: " freeradius-users " <freeradius-users(a)lists.freeradius.org> Message-ID: <tencent_5E7B240C4B421E587B96F796(a)qq.com> Content-Type: text/plain; charset="iso-8859-1" Hello, I'm using free radius server 2.1.11 on Linux Enterprise Server 6.1. OS: Linux Enterprise Server 6.1 Radius: free radius server 2.1.11 Database: Mysql The WIFI routers we're using are in diffirent private networks, behind the internet gateways. The WIFI router has private IP address, such as 192.168.1.1. For some reason, we need know which Internet IP address, the WIFI router is using to do the authention with the FreeRadius server. The FreeRadius server is on internet. As the business needs, we need save the IP addres(Internet gateway IP address) to MySql database. Can anyone advise how to do so? Thanks! Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freeradius.org/pipermail/freeradius-users/attachments/2011091…> ------------------------------ Message: 2 Date: Mon, 12 Sep 2011 14:10:48 +0200 From: Arran Cudbard-Bell <a.cudbardb(a)freeradius.org> Subject: Re: NAS IP Address To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Message-ID: <8B265A64-D969-4949-A8C8-A0BD016C62E8(a)freeradius.org> Content-Type: text/plain; charset="iso-8859-1" On 12 Sep 2011, at 13:58, 2394263740 wrote: > Hello, > I'm using free radius server 2.1.11 on Linux Enterprise Server 6.1. > OS: Linux Enterprise Server 6.1 > Radius: free radius server 2.1.11 > Database: Mysql > > The WIFI routers we're using are in diffirent private networks, behind the internet gateways. The WIFI router has private IP address, such as 192.168.1.1. > > For some reason, we need know which Internet IP address, the WIFI router is using to do the authention with the FreeRadius server. The FreeRadius server is on internet. > > As the business needs, we need save the IP addres(Internet gateway IP address) to MySql database. edit the queries in raddb/sql/mysql/dialup.conf and add the additional columns to the SQL database. The original IP address of the NAS may be sent in the NAS-IP-Address attribute, in which case use the expansion %{NAS-IP-Address} for the value of the new column. Arran Cudbard-Bell a.cudbardb(a)freeradius.org RADIUS - Waging war on ignorance and apathy one Access-Challenge at a time. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freeradius.org/pipermail/freeradius-users/attachments/2011091…> ------------------------------ Message: 3 Date: Mon, 12 Sep 2011 14:04:53 +0000 From: "Sallee, Stephen (Jake)" <Jake.Sallee(a)umhb.edu> Subject: Best Practices - maximum NAS entries in clients.conf To: freeradius-users <freeradius-users(a)lists.freeradius.org> Message-ID: <3A9815D880FBAF41A523B3A35AF3C3DF170E6FD1(a)AVATAR.umhb.edu> Content-Type: text/plain; charset="iso-8859-1" @ everyone We have about 100 NAS entries in our clients.conf file, it makes the file a bear to deal with but the server seems to handle it fine. We will be expanding our infrastructure soon and the number of NAS entries will increase significantly. At what point should we think about putting them into a database for FR to use? Also, I have seen some chatter on the list about dynamic NASs. Am I correct in assuming that if we are using a DB instead of the clients.conf file we can add or remove clients simply by making changes to the correct table, all without having to restart FR? Jake Sallee Godfather of Bandwidth Network Engineer University of Mary Hardin-Baylor 900 College St. Belton, Texas 76513 Fone: 254-295-4658 Phax: 254-295-4221 ------------------------------ Message: 4 Date: Mon, 12 Sep 2011 16:17:40 +0200 From: Alan DeKok <aland(a)deployingradius.com> Subject: Re: Best Practices - maximum NAS entries in clients.conf To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Message-ID: <4E6E1484.70200(a)deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 Sallee, Stephen (Jake) wrote: > We have about 100 NAS entries in our clients.conf file, it makes the file a bear to deal with but the server seems to handle it fine. We will be expanding our infrastructure soon and the number of NAS entries will increase significantly. At what point should we think about putting them into a database for FR to use? Whenever you get tired of managing them in clients.conf. The server has been tested with 500K clients in clients.conf. It takes a few seconds to start, and a gig or so of RAM, but it works. > Also, I have seen some chatter on the list about dynamic NASs. Am I correct in assuming that if we are using a DB instead of the clients.conf file we can add or remove clients simply by making changes to the correct table, all without having to restart FR? Yes. You can also do this with files. See raddb/dynamic_clients in 2.1.12. (When it comes out) Alan DeKok. ------------------------------ Message: 5 Date: Mon, 12 Sep 2011 16:21:45 +0200 From: Arran Cudbard-Bell <a.cudbardb(a)freeradius.org> Subject: Re: Best Practices - maximum NAS entries in clients.conf To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Message-ID: <D41AD9A3-B5A6-4690-B053-58361E3D7D71(a)freeradius.org> Content-Type: text/plain; charset=us-ascii On 12 Sep 2011, at 16:04, Sallee, Stephen (Jake) wrote: > @ everyone > > We have about 100 NAS entries in our clients.conf file, it makes the file a bear to deal with but the server seems to handle it fine. We will be expanding our infrastructure soon and the number of NAS entries will increase significantly. At what point should we think about putting them into a database for FR to use? When it becomes a bear to deal with the clients.conf file :) - I guess memory might be a concern? But i'm sure there are sites out there with client.conf files holding thousands of entries... It's a hash table in C, it's going to be fast. > > Also, I have seen some chatter on the list about dynamic NASs. Am I correct in assuming that if we are using a DB instead of the clients.conf file we can add or remove clients simply by making changes to the correct table, all without having to restart FR? Indeed. You can also set them to expire as well, to clean up old unused entries. -Arran Arran Cudbard-Bell a.cudbardb(a)freeradius.org RADIUS - Waging war on ignorance and apathy one Access-Challenge at a time. ------------------------------ Message: 6 Date: Mon, 12 Sep 2011 16:25:14 +0200 From: Arran Cudbard-Bell <a.cudbardb(a)freeradius.org> Subject: Re: Best Practices - maximum NAS entries in clients.conf To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Message-ID: <CA2EA7A1-A06B-428C-9259-DEE20CFAC278(a)freeradius.org> Content-Type: text/plain; charset=us-ascii > Fone: 254-295-4658 > Phax: 254-295-4221 Nice :) Arran Cudbard-Bell a.cudbardb(a)freeradius.org RADIUS - Waging war on ignorance and apathy one Access-Challenge at a time. ------------------------------ Message: 7 Date: Mon, 12 Sep 2011 07:41:16 -0700 (PDT) From: Bruce Nunn <ironrake(a)yahoo.com> Subject: Re: Best Practices - maximum NAS entries in clients.conf To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Message-ID: <1315838476.43108.YahooMailNeo(a)web110413.mail.gq1.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 If the network your APs are on is physically secure, and you don't need accounting for individual APs, you can use netmasks to define clients in the clients.conf file. ----- Original Message ----- From: "Sallee, Stephen (Jake)" <Jake.Sallee(a)umhb.edu> To: freeradius-users <freeradius-users(a)lists.freeradius.org> Cc: Sent: Monday, September 12, 2011 9:04 AM Subject: Best Practices - maximum NAS entries in clients.conf @ everyone We have about 100 NAS entries in our clients.conf file, it makes the file a bear to deal with but the server seems to handle it fine.? We will be expanding our infrastructure soon and the number of NAS entries will increase significantly.? At what point should we think about putting them into a database for FR to use? Also, I have seen some chatter on the list about dynamic NASs.? Am I correct in assuming that if we are using a DB instead of the clients.conf file we can add or remove clients simply by making changes to the correct table, all without having to restart FR? ------------------------------ Message: 8 Date: Mon, 12 Sep 2011 07:44:25 -0700 (PDT) From: Rajkumar balaji <rajkumar.balaji.s(a)gmail.com> Subject: Unable to Authenticate with SHA Password To: freeradius-users(a)lists.freeradius.org Message-ID: <1315838665841-4794449.post(a)n5.nabble.com> Content-Type: text/plain; charset=us-ascii Hi All, I am unable to authenticate the When I send SHA password to the FreeRADIUS. I have configured SHA-Password := "admin123" in the users file. My Password is admin123 and after SHA messagedigest its -50-2710713-59-76-1105593-48-89-126-957495-4-108-29-81-48 RADIUS is getting the request but its rejecting it. Please find the following radius logs, rad_recv: Access-Request packet from host 172.17.148.152 port 50459, id=0, length=111 User-Name = "emsadmin" User-Password = "-50-2710713-59-76-1105593-48-89-126-957495-4-108-29-81-48" NAS-Identifier = "sunems8-zone2" # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop ++[digest] returns noop [suffix] No '@' in User-Name = "emsadmin", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop [files] users: Matched entry emsadmin at line 204 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns updated Found Auth-Type = PAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +- entering group PAP {...} [pap] login attempt with password "-50-2710713-59-76-1105593-48-89-126-957495-4-108-29-81-48" [pap] Using SHA1 encryption. [pap] Configured SHA1 password has incorrect length [pap] Passwords don't match ++[pap] returns reject Failed to authenticate the user. Using Post-Auth-Type Reject # Executing group from file /usr/local/etc/raddb/sites-enabled/default +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> emsadmin attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 1 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 1 Sending Access-Reject of id 0 to 172.17.148.152 port 50459 Waking up in 4.9 seconds. Cleaning up request 1 ID 0 with timestamp +6002 Ready to process requests. -- View this message in context: http://freeradius.1045715.n5.nabble.com/Unable-to-Authenticate-with-SHA-Pas… Sent from the FreeRadius - User mailing list archive at Nabble.com. ------------------------------ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html End of Freeradius-Users Digest, Vol 77, Issue 42 ************************************************ Arran Cudbard-Bell a.cudbardb(a)freeradius.org RADIUS - Waging war on ignorance and apathy one Access-Challenge at a time.

1 0

Custom function to update Session-Timeout
by Ivaylo Petkov 13 Sep '11

13 Sep '11

Hi All, I am new to developing for Freeradius and i was hoping one of you can direct me into the right direction. I would like to have a program update the Session-Timeout on authentication request or on disconnect so that when the user receives the access accept it receives the updated Session-TImeout. What is the correct way of doing this and is there some sort of example that i can read. I have been searching in the mailing list and in google but so far no luck. Regards, Ivo

6 6

First Run Problem
by Majid Dadashi 13 Sep '11

13 Sep '11

Hi, I just installed "freeradius-server-2.1.11" as follow: $ ./configure $ make $ sudo make install when I run the server using the following command: $ sudo radiusd -X it just returns the following error: "radiusd: error while loading shared libraries: libfreeradius-radius-2.1.11.so: cannot open shared object file: No such file or directory" what do you think is the problem? Thanks for your help. Regards

2 2

Troubleshooting FreeRadius +LDAP
by Ricardo Sousa 13 Sep '11

13 Sep '11

Greetings list users, I'm trying setup FreeRadius to work with LDAP in a deployment of ClearOS and have followed this How-To http://www.clearfoundation.com/docs/howtos/setting_up_freeradius2_to_use_ld… and this How-To http://deployingradius.com/documents/configuration/pap.html with success, up to the part of the inital radtest with credentials inserted in the users file. But when trying to use credentials from the LDAP directory, the Radius server returns an Access-Reject packet. Below is the output from the debug mode. *************************************************** login as: root root(a)192.168.3.5's password: Last login: Mon Sep 12 13:31:45 2011 from 192.168.3.2 [root@system ~]# service radiusd stop Stopping RADIUS server: [ OK ] [root@system ~]# radiusd -X FreeRADIUS Version 2.1.7, for host i686-redhat-linux-gnu, built on May 19 2010 at 13:10:59 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/clearos-clients.conf including files in directory /etc/raddb/modules/ including configuration file /etc/raddb/modules/radutmp including configuration file /etc/raddb/modules/smbpasswd including configuration file /etc/raddb/modules/realm including configuration file /etc/raddb/modules/etc_group including configuration file /etc/raddb/modules/attr_rewrite including configuration file /etc/raddb/modules/wimax including configuration file /etc/raddb/modules/detail including configuration file /etc/raddb/modules/logintime including configuration file /etc/raddb/modules/detail.example.com including configuration file /etc/raddb/modules/files including configuration file /etc/raddb/modules/counter including configuration file /etc/raddb/modules/acct_unique including configuration file /etc/raddb/modules/ippool including configuration file /etc/raddb/modules/exec including configuration file /etc/raddb/modules/inner-eap including configuration file /etc/raddb/modules/always including configuration file /etc/raddb/modules/passwd including configuration file /etc/raddb/modules/expiration including configuration file /etc/raddb/modules/checkval including configuration file /etc/raddb/modules/linelog including configuration file /etc/raddb/modules/sqlcounter_expire_on_login including configuration file /etc/raddb/modules/digest including configuration file /etc/raddb/modules/mschap including configuration file /etc/raddb/modules/detail.log including configuration file /etc/raddb/modules/echo including configuration file /etc/raddb/modules/sradutmp including configuration file /etc/raddb/modules/mac2ip including configuration file /etc/raddb/modules/mac2vlan including configuration file /etc/raddb/modules/pam including configuration file /etc/raddb/modules/smsotp including configuration file /etc/raddb/modules/ldap including configuration file /etc/raddb/modules/unix including configuration file /etc/raddb/modules/pap including configuration file /etc/raddb/modules/sql_log including configuration file /etc/raddb/modules/policy including configuration file /etc/raddb/modules/expr including configuration file /etc/raddb/modules/attr_filter including configuration file /etc/raddb/modules/perl including configuration file /etc/raddb/modules/cui including configuration file /etc/raddb/modules/preprocess including configuration file /etc/raddb/modules/otp including configuration file /etc/raddb/modules/chap including configuration file /etc/raddb/clearos-eap.conf including configuration file /etc/raddb/policy.conf including files in directory /etc/raddb/sites-enabled/ including configuration file /etc/raddb/sites-enabled/control-socket including configuration file /etc/raddb/sites-enabled/inner-tunnel including configuration file /etc/raddb/sites-enabled/default including configuration file /etc/raddb/sites-enabled/clearos-inner-tunnel group = radiusd user = radiusd 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 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 { require_message_authenticator = no secret = "mysecretpass" shortname = "myclient" } 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 = "ttls" 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/clearos-certs/key.pem" certificate_file = "/etc/raddb/clearos-certs/cert.pem" CA_file = "/etc/raddb/clearos-certs/ca.pem" dh_file = "/etc/raddb/clearos-certs/dh1024.pem" random_file = "/etc/raddb/clearos-certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" 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 = "clearos-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 clearos-inner-tunnel { modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_ldap Module: Instantiating ldap ldap { server = "localhost" port = 389 password = "CnboAg6Wb3lTe75u" identity = "cn=manager,cn=internal,dc=clearos,dc=lan" net_timeout = 5 timeout = 20 timelimit = 10 tls_mode = no start_tls = no tls_require_cert = "allow" tls { start_tls = no require_cert = "allow" } basedn = "dc=clearos,dc=lan" filter = "(uid=%{%{Stripped-User-Name}:-%{User-Name}})" base_filter = "(objectclass=radiusprofile)" auto_header = no access_attr_used_for_allow = yes groupname_attribute = "cn" groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{control:Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{control: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_groupcmp for Ldap-Group 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 sambaLmPassword mapped to RADIUS LM-Password rlm_ldap: LDAP sambaNtPassword mapped to RADIUS NT-Password rlm_ldap: LDAP dBCSPwd mapped to RADIUS LM-Password rlm_ldap: LDAP acctFlags mapped to RADIUS SMB-Account-CTRL-TEXT 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: 0x8eaf548 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 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. rad_recv: Access-Request packet from host 127.0.0.1 port 40537, id=123, length=55 User-Name = "bob" User-Password = "hello" NAS-IP-Address = 127.0.0.1 NAS-Port = 0 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "bob", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop [files] users: Matched entry bob at line 1 ++[files] returns ok [ldap] performing user authorization for bob [ldap] expand: %{Stripped-User-Name} -> [ldap] expand: %{User-Name} -> bob [ldap] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=bob) [ldap] expand: dc=clearos,dc=lan -> dc=clearos,dc=lan 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 localhost:389, authentication 0 rlm_ldap: bind as cn=manager,cn=internal,dc=clearos,dc=lan/CnboAg6Wb3lTe75u to localhost:389 rlm_ldap: waiting for bind result ... rlm_ldap: Bind was successful rlm_ldap: performing search in dc=clearos,dc=lan, with filter (uid=bob) rlm_ldap: object not found [ldap] search failed rlm_ldap: ldap_release_conn: Release Id: 0 ++[ldap] returns notfound ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns updated Found Auth-Type = PAP +- entering group PAP {...} [pap] login attempt with password "hello" [pap] Using clear text password "hello" [pap] User authenticated successfully ++[pap] returns ok +- entering group post-auth {...} ++[exec] returns noop Sending Access-Accept of id 123 to 127.0.0.1 port 40537 Finished request 0. Going to the next request Waking up in 4.9 seconds. Cleaning up request 0 ID 123 with timestamp +6 Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1 port 52736, id=80, length=57 User-Name = "user1" User-Password = "user1pass" NAS-IP-Address = 127.0.0.1 NAS-Port = 0 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "user1", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop rlm_ldap: Entering ldap_groupcmp() [files] expand: dc=clearos,dc=lan -> dc=clearos,dc=lan [files] expand: %{Stripped-User-Name} -> [files] expand: %{User-Name} -> user1 [files] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=user1) rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in dc=clearos,dc=lan, with filter (uid=user1) rlm_ldap: object not found rlm_ldap::ldap_groupcmp: search failed rlm_ldap: ldap_release_conn: Release Id: 0 [files] users: Matched entry DEFAULT at line 1 ++[files] returns ok [ldap] performing user authorization for user1 [ldap] expand: %{Stripped-User-Name} -> [ldap] expand: %{User-Name} -> user1 [ldap] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=user1) [ldap] expand: dc=clearos,dc=lan -> dc=clearos,dc=lan rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in dc=clearos,dc=lan, with filter (uid=user1) rlm_ldap: object not found [ldap] search failed rlm_ldap: ldap_release_conn: Release Id: 0 ++[ldap] returns notfound ++[expiration] returns noop ++[logintime] returns noop [pap] Found existing Auth-Type, not changing it. ++[pap] returns noop Found Auth-Type = Reject Auth-Type = Reject, rejecting user Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> user1 attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 1 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 1 Sending Access-Reject of id 80 to 127.0.0.1 port 52736 Waking up in 4.5 seconds. *************************************************** Hope someone can show some light to this unix illiterate. Regards, Ricardo

2 2

LDAP Authentication bind as user issue
by DaveA 12 Sep '11

12 Sep '11

This is exactly what I want, from the docs: "If the administrator wishes to use rlm_ldap only for authentication or does not wish to populate the identity,password configuration attributes he can set this attribute by other means and avoid the ldap search completely. For instance it can be set through the hints file in the authorize section: DEFAULT Ldap-UserDN := `uid=%{User-Name},ou=people,dc=company,dc=com`" I followed this and cannot make it work. Configs/Tests/Results to follow… The LDAP module stays the same for these tests. I want to use LDAPs over port 636. I want to authenticate the user only, preferably binding as the user. ldap ldap.netid { server = "netid-dev.<redacted>.ca" port = 636 basedn = "dc=netid,dc=<redacted>,dc=ca" filter = "(uid=%{%{Stripped-User-Name}:-%{User-Name}})" password_attribute = "userPassword" } ----------------------------------------- What we want to see: >>> Sending proxied request internally to virtual server. server net_id { # Executing section authorize from file /etc/raddb/sites-enabled/net_id +- entering group authorize {...} [files] users: Matched entry DEFAULT at line 3 ++[files] returns ok Found Auth-Type = LDAP # Executing group from file /etc/raddb/sites-enabled/net_id +- entering group LDAP {...} [ldap.netid] login attempt by "<redacted>" with password "TEST" [ldap.netid] user DN: uid=<redacted>,ou=people,dc=netid,dc=<redacted>,dc=ca [ldap.netid] (re)connect to netid-dev.<redacted>.ca:636, authentication 1 [ldap.netid] setting TLS mode to 1 [ldap.netid] bind as uid=<redacted>,ou=people,dc=netid,dc=<redacted>,dc=ca/TEST to netid-dev.<redacted>.ca:636 [ldap.netid] waiting for bind result ... [ldap.netid] Bind was successful [ldap.netid] user <redacted> authenticated successfully ++[ldap.netid] returns ok Login OK: [<redacted>] (from client localhost port 10 via TLS tunnel) WARNING: Empty post-auth section. Using default return values. } # server net_id Going to the next request <<< Received proxied response code 2 from internal virtual server. # Executing section post-proxy from file /etc/raddb/sites-enabled/default +- entering group post-proxy {...} ++[post_proxy_log] returns noop [eap] No pre-existing handler found ++[eap] returns noop Found Auth-Type = LDAP Found Auth-Type = Accept Warning: Found 2 auth-types on request for user '<redacted>' Auth-Type = Accept, accepting the user Login OK: [<redacted>@netid.<redacted>.ca] (from client localhost port 10) BUT this is bad because as you can see in line 5, I've cheated to populate the DN. In the users file, I have: DEFAULT Auth-Type := LDAP, Ldap-UserDN := `uid=realusername,ou=people,dc=netid,dc=<redacted>,dc=ca` Obviously this is no good because we need to authenticate hundreds of people. I tried setting the uid in the line above with the User-Name variable and that didn't fly; it doesn't get expanded. The server for this test: server net_id { authorize { files } authenticate { files Auth-Type LDAP { ldap.netid } } } ----------------------------------------- This is what happens when I try using the hints file as suggested in the docs: users - DEFAULT Auth-Type := LDAP hints - DEFAULT Ldap-UserDN := `uid=%{User-Name},ou=people,dc=netid,dc=<redacted>,dc=ca` server net_id { authorize { # I left files here to set the Auth-Type, I also tried removing files and adding the default auth-type to hints, which didn't work either. files preprocess } authenticate { Auth-Type LDAP { ldap.netid } } } Results: # Executing section authorize from file /etc/raddb/sites-enabled/net_id +- entering group authorize {...} [files] users: Matched entry DEFAULT at line 3 ++[files] returns ok [preprocess] hints: Matched DEFAULT at 36 ++[preprocess] returns ok Found Auth-Type = LDAP # Executing group from file /etc/raddb/sites-enabled/net_id +- entering group LDAP {...} [ldap.netid] login attempt by "<redacted>" with password "TEST" [ldap.netid] expand: %{Stripped-User-Name} -> <redacted> [ldap.netid] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=<redacted>) [ldap.netid] expand: dc=netid,dc=<redacted>,dc=ca -> dc=netid,dc=<redacted>,dc=ca [ldap.netid] ldap_get_conn: Checking Id: 0 [ldap.netid] ldap_get_conn: Got Id: 0 [ldap.netid] attempting LDAP reconnection [ldap.netid] (re)connect to netid-dev.<redacted>.ca:636, authentication 0 [ldap.netid] setting TLS mode to 1 [ldap.netid] bind as / to netid-dev.<redacted>.ca:636 [ldap.netid] waiting for bind result ... [ldap.netid] Bind was successful [ldap.netid] performing search in dc=netid,dc=<redacted>,dc=ca, with filter (uid=<redacted>) [ldap.netid] ldap_search() failed: Insufficient access. Check the identity and password configuration directives. [ldap.netid] ldap_release_conn: Release Id: 0 ++[ldap.netid] returns fail Failed to authenticate the user. Login incorrect: [<redacted>] (from client localhost port 10 via TLS tunnel) This way it binds anonymously, and then fails to do an ldapsearch because of insufficient privs. Giving * read to all seems silly, and I would rather not go that route. If anyone has suggestions or comments they would be greatly appreciated. Dave -- View this message in context: http://freeradius.1045715.n5.nabble.com/LDAP-Authentication-bind-as-user-is… Sent from the FreeRadius - User mailing list archive at Nabble.com.

4 6

Unable to Authenticate with SHA Password
by Rajkumar balaji 12 Sep '11

12 Sep '11

Hi All, I am unable to authenticate the When I send SHA password to the FreeRADIUS. I have configured SHA-Password := "admin123" in the users file. My Password is admin123 and after SHA messagedigest its -50-2710713-59-76-1105593-48-89-126-957495-4-108-29-81-48 RADIUS is getting the request but its rejecting it. Please find the following radius logs, rad_recv: Access-Request packet from host 172.17.148.152 port 50459, id=0, length=111 User-Name = "emsadmin" User-Password = "-50-2710713-59-76-1105593-48-89-126-957495-4-108-29-81-48" NAS-Identifier = "sunems8-zone2" # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop ++[digest] returns noop [suffix] No '@' in User-Name = "emsadmin", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop [files] users: Matched entry emsadmin at line 204 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns updated Found Auth-Type = PAP # Executing group from file /usr/local/etc/raddb/sites-enabled/default +- entering group PAP {...} [pap] login attempt with password "-50-2710713-59-76-1105593-48-89-126-957495-4-108-29-81-48" [pap] Using SHA1 encryption. [pap] Configured SHA1 password has incorrect length [pap] Passwords don't match ++[pap] returns reject Failed to authenticate the user. Using Post-Auth-Type Reject # Executing group from file /usr/local/etc/raddb/sites-enabled/default +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> emsadmin attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 1 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 1 Sending Access-Reject of id 0 to 172.17.148.152 port 50459 Waking up in 4.9 seconds. Cleaning up request 1 ID 0 with timestamp +6002 Ready to process requests. -- View this message in context: http://freeradius.1045715.n5.nabble.com/Unable-to-Authenticate-with-SHA-Pas… Sent from the FreeRadius - User mailing list archive at Nabble.com.

2 1

NAS IP Address
by 2394263740 12 Sep '11

12 Sep '11

Hello, I'm using free radius server 2.1.11 on Linux Enterprise Server 6.1. OS: Linux Enterprise Server 6.1 Radius: free radius server 2.1.11 Database: Mysql The WIFI routers we're using are in diffirent private networks, behind the internet gateways. The WIFI router has private IP address, such as 192.168.1.1. For some reason, we need know which Internet IP address, the WIFI router is using to do the authention with the FreeRadius server. The FreeRadius server is on internet. As the business needs, we need save the IP addres(Internet gateway IP address) to MySql database. Can anyone advise how to do so? Thanks! Tom

2 1