- Freeradius-Users - lists.freeradius.org

sql + ippool + redundancy
by Konstantin Chekushin 05 Feb '10

05 Feb '10

Hi! I have a question about failover configuration. I have freeradius + sqlippool module for ip-assigning. I have 2 databases for redundancy (described in sql1 and sql2). my file from enabled-server: server allauth {         listen {                 type = auth                 ipaddr = *                 port = 1812         }         authorize {                 auth_log                 update control {                         Pool-Name = 'main_pool'                 }                 redundant {                         # we need this only to get new Pool-name, if user exist in our defined group.                         sql1                         sql2                 }                 update control {                         # any user must be accepted.                         Auth-Type = 'Accept'                 }         }         post-auth {                 redundant {                         sqlippool1 # this module use sql1 for assigning                         sqlippool2 # this module use sql2 for assigning, if first will fails.                         main_pool                 }                 reply_log         } } I've run the freeradius, but when I turned off my first database (sql1), my redundancy in post-auth return incorrect code:, sqlippool1 returns "noop", neither "fail". May be I've selected the wrong way to solve my task? Any comments are welcome... How can I switch ip-assigning on sqlippool2, when sql1 (used by sqlippool1) doesn't work? some information from log: Wed Feb  3 15:36:29 2010 : Error: rlm_sql (sql1): Failed to connect DB handle #1 Wed Feb  3 15:36:29 2010 : Error: rlm_sql (sql1): reconnect failed, database down? Wed Feb  3 15:36:29 2010 : Error: sqlippool_command: database query error in: 'COMMIT' Wed Feb  3 15:36:29 2010 : Info: [sqlippool1]   expand: SELECT id FROM radippool  WHERE pool_name='%{control:Pool-Name}' LIMIT 1 -> SELECT id FROM radippool  WHERE pool_name='main_pool' LIMIT 1 Wed Feb  3 15:36:29 2010 : Error: rlm_sql_mysql: Socket not connected Wed Feb  3 15:36:29 2010 : Debug: rlm_sql (sql1): Attempting to connect rlm_sql_mysql #1 Wed Feb  3 15:36:29 2010 : Info: rlm_sql_mysql: Starting connect to MySQL server for #1 Wed Feb  3 15:36:29 2010 : Error: rlm_sql_mysql: Couldn't connect socket to MySQL server user@ip:dbname Wed Feb  3 15:36:29 2010 : Error: rlm_sql_mysql: Mysql error 'Lost connection to MySQL server at 'reading initial communication packet', system error: 0' Wed Feb  3 15:36:29 2010 : Error: rlm_sql (sql1): Failed to connect DB handle #1 Wed Feb  3 15:36:29 2010 : Error: rlm_sql (sql1): reconnect failed, database down? Wed Feb  3 15:36:29 2010 : Error: sqlippool_query1: database query error Wed Feb  3 15:36:29 2010 : Debug: rlm_sql (sql1): Released sql socket id: 1 Wed Feb  3 15:36:29 2010 : Info: [sqlippool1] IP address could not be allocated as no pool exists with that name. Wed Feb  3 15:36:29 2010 : Info: +++[sqlippool1] returns noop Wed Feb  3 15:36:29 2010 : Info: ++- policy redundant returns noop

2 2

HOWTO Contribution
by George Shearer 05 Feb '10

05 Feb '10

Hi All, I'd like to contribute a HOWTO to the Wiki.. I don't see a HOWTO to do that :) Topic: Replacing Cisco ACS Server with FreeRadius in a Microsoft Active Directory environment to support Wireless, Network Administration, and VPN users.

3 4

RE: STILL Trying to get tunneling to work- resolved, and a question
by Mike Bernhardt 04 Feb '10

04 Feb '10

Just to clarify my questions: If one of the servers I'm proxying to is dead, is there a way to reduce the number of times freeradius tries before failing over to the next one? 2. Are there any ways to make this process more efficient, given that status check currently doesn't work with the downstream servers? -----Original Message----- From: Mike Bernhardt [mailto:bernhardt@bart.gov] Sent: Friday, January 29, 2010 11:36 AM To: 'freeradius-users(a)lists.freeradius.org' Subject: Re: STILL Trying to get tunneling to work- resolved, and a question I found the major problem that caused my configuration to not work. This was in regards to getting freeradius to proxy EAP/PEAP to IAS servers as standard CHAP. I was using freeradius 2.1.7, and then 2.1.8 as recommended by someone. Neither worked. The solution was to back down to 2.1.4. Is this a bug that was introduced after that, or what? I can email config files to whomever needs them to work on it. So, I now have another question: I have set up 2 IAS servers in a pool. I would like to drastically reduce the timeout before freeradius fails over to the 2nd one. How do I do that? Right now it takes about 30 seconds but I don't see a variable to change that. I also noticed that the status requests, which begin after it has marked a server as bad, do not work. How do I use the user name and [bad] password to check status and bring it back sooner? It only seems to try it once and that's it. Thanks, Mike

2 5

freeradius+freebsd
by James Devine 04 Feb '10

04 Feb '10

I'm trying to setup a freeradius server on freebsd7 to authenticate against the local passwd file and seem to be running into some problems. in sites-available/default I setup authorize/authenticate such as: authorize { preprocess chap mschap suffix unix files expiration logintime pap } authenticate { Auth-Type PAP { pap } Auth-Type CHAP { chap } Auth-Type MS-CHAP { mschap } unix } and /etc/pam.d/radiusd setup such as: # auth auth required pam_unix.so no_warn try_first_pass # account account required pam_nologin.so account required pam_login_access.so account required pam_unix.so # session session required pam_permit.so # password password required pam_unix.so no_warn try_first_pass And I get this output: rad_recv: Access-Request packet from host 10.10.10.231 port 57714, id=94, length=96 User-Name = "testuser" Service-Type = Login-User NAS-IP-Address = 10.10.10.140 NAS-Port = 4 Calling-Station-Id = "10.10.10.140" NAS-Port-Type = Virtual User-Password = "testpass" NAS-Port-Id = "tty4" +- entering group authorize {...} [preprocess] hints: Matched DEFAULT at 23 [preprocess] expand: %{Packet-Src-IP-Address} -> 10.10.10.231 [preprocess] expand: %{Packet-Type} -> Access-Request [preprocess] expand: %{Packet-Src-IP-Address} -> 10.10.10.231 [preprocess] expand: %{Packet-Src-IP-Address} -> 10.10.10.231 [preprocess] hints: Matched DEFAULT at 87 [preprocess] hints: Matched DEFAULT at 76 [preprocess] expand: %{Packet-Src-IP-Address} -> 10.10.10.231 [preprocess] expand: %{Packet-Src-IP-Address} -> 10.10.10.231 ++[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 ++[unix] returns updated [files] users: Matched entry DEFAULT at line 2 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns updated Found Auth-Type = PAP +- entering group PAP {...} [pap] login attempt with password "testpass" [pap] Using CRYPT encryption. [pap] Passwords don't match ++[pap] returns reject Failed to authenticate the user. Login incorrect (rlm_pap: CRYPT password check failed): [testuser/testpass] (from client boss1_internal port 4 cli 10.10.10.140) 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 Sending Access-Reject of id 94 to 10.10.10.231 port 57714 Finished request 0. Going to the next request Waking up in 4.9 seconds. Cleaning up request 0 ID 94 with timestamp +10 Ready to process requests. The password is correct, I'm not sure if the CRYPT encryption method is correct because I believe the passwords are stored as md5 hashes in the passwd file, any idea where I may be going wrong?

3 8

Re:Default entry to allow all
by Godfrey Peart 04 Feb '10

04 Feb '10

Thank you, so is there a method to grant access if a user fails the access-challenge request when using mschap + peap

2 1

Failover Configuration
by Troy.Rindy＠validants.com 03 Feb '10

03 Feb '10

I am attempting to use freeRadius to perform the following: Send Request to our Corporate Radius Server for Two Factor Auth If the corporate Server is Unavailable, doesn't respond or if the user is not found, then Use Auth-Type LDAP to Authenticate to our local LDAP repository If the Corporate Raidus Server is available, finds the user and sends an Access-Reject response, the local LDAP Authentication should not be attempted at all and the user denied access. I have freeRadius configured to proxy to the Corporate Radius server and it works great. I also have freeRadius configured to Authenticate users against LDAP. However, I cannot get them to work together as "Try Corporate first, then local LDAP second". I did get this working, sort of.... My first request to the proxy server will timeout as the proxy can't reach the corporate server. If I wait 30 seconds, the corporate server will be marked as "dead" and LDAP will be used instead. However, some users will be authenticated by corporate Radius server and additional users will be authenticated by the Local Radius server via LDAP. Telling a user to wait 30 seconds to login is probably not going to fly very far. I'm really not looking for troubleshooting help... but more of "best practice" using freeRadius. ie. Do I put the LDAP authentication into a virtual server (which I have working)? Do I use the proxy functionality to call the corporate RADIUS server (I also have this working). Do I use the module fail-over logic to first somehow invoke the proxy logic to call the Corporate server, then use the proxy module (if there is one which can be called) return codes to conditionally call the ldap authentication module? Our local LDAP repository does include ALL of our UNIX users. The Corporate RADIUS contains a subset of our UNIX users who are enabled for Two Factor Auth. Do I add a Radius attribute to each users's object in our local LDAP, which indicates which ones should be proxied to the corporate RADIUS server (I want to avoid the administrative burden of this)? And if what I am doing is best practice, why isn't it working the way I think it should? So I guess many of you will want to see debug output... here is debug output showing a test of the corporate RADIUS server being unavailable/down and failover to local LDAP authentication: Request 1) Tries corporate with proxy - Fails Request 2) Tries corporate via proxy again - Fails and marks server as "dead" Request 3) Does not try corporate at all and authenticates via LDAP - Success. I desire to have all of this to happen during a single authentication request. root@ldom0001 # /usr/sfw/sbin/radiusd -X -d /etc/raddb/proxy FreeRADIUS Version 2.1.8, for host sparc-sun-solaris2.10, built on Jan 26 2010 at 20:14:12 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/proxy/radiusd.conf including configuration file /etc/raddb/proxy/proxy.conf including configuration file /etc/raddb/proxy/clients.conf including files in directory /etc/raddb/proxy/modules/ including configuration file /etc/raddb/proxy/modules/ldap including configuration file /etc/raddb/proxy/modules/mac2ip including configuration file /etc/raddb/proxy/modules/logintime including configuration file /etc/raddb/proxy/modules/ippool including configuration file /etc/raddb/proxy/modules/sqlcounter_expire_on_login including configuration file /etc/raddb/proxy/modules/pap including configuration file /etc/raddb/proxy/modules/mac2vlan including configuration file /etc/raddb/proxy/modules/chap including configuration file /etc/raddb/proxy/modules/attr_filter including configuration file /etc/raddb/proxy/modules/expr including configuration file /etc/raddb/proxy/modules/unix including configuration file /etc/raddb/proxy/modules/exec including configuration file /etc/raddb/proxy/modules/counter including configuration file /etc/raddb/proxy/modules/pam including configuration file /etc/raddb/proxy/modules/wimax including configuration file /etc/raddb/proxy/modules/etc_group including configuration file /etc/raddb/proxy/modules/krb5 including configuration file /etc/raddb/proxy/modules/cui including configuration file /etc/raddb/proxy/modules/passwd including configuration file /etc/raddb/proxy/modules/always including configuration file /etc/raddb/proxy/modules/radutmp including configuration file /etc/raddb/proxy/modules/linelog including configuration file /etc/raddb/proxy/modules/checkval including configuration file /etc/raddb/proxy/modules/preprocess including configuration file /etc/raddb/proxy/modules/digest including configuration file /etc/raddb/proxy/modules/otp including configuration file /etc/raddb/proxy/modules/acct_unique including configuration file /etc/raddb/proxy/modules/detail including configuration file /etc/raddb/proxy/modules/echo including configuration file /etc/raddb/proxy/modules/detail.example.com including configuration file /etc/raddb/proxy/modules/mschap including configuration file /etc/raddb/proxy/modules/expiration including configuration file /etc/raddb/proxy/modules/sql_log including configuration file /etc/raddb/proxy/modules/attr_rewrite including configuration file /etc/raddb/proxy/modules/policy including configuration file /etc/raddb/proxy/modules/inner-eap including configuration file /etc/raddb/proxy/modules/detail.log including configuration file /etc/raddb/proxy/modules/sradutmp including configuration file /etc/raddb/proxy/modules/perl including configuration file /etc/raddb/proxy/modules/smbpasswd including configuration file /etc/raddb/proxy/modules/realm including configuration file /etc/raddb/proxy/modules/ntlm_auth including configuration file /etc/raddb/proxy/modules/files including configuration file /etc/raddb/proxy/modules/smsotp including configuration file /etc/raddb/proxy/eap.conf including configuration file /etc/raddb/proxy/policy.conf including files in directory /etc/raddb/proxy/sites-enabled/ including configuration file /etc/raddb/proxy/sites-enabled/inner-tunnel including configuration file /etc/raddb/proxy/sites-enabled/guns including configuration file /etc/raddb/proxy/sites-enabled/control-socket including configuration file /etc/raddb/proxy/sites-enabled/default main { allow_core_dumps = no } including dictionary file /etc/raddb/proxy/dictionary main { prefix = "/usr/sfw" localstatedir = "/usr/sfw/var" logdir = "/usr/sfw/var/log/radius" libdir = "/usr/sfw/lib" radacctdir = "/usr/sfw/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/usr/sfw/var/run/radiusd/radiusd.pid" checkrad = "/usr/sfw/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 = yes dead_time = 120 wake_all_if_all_dead = no } home_server radius.corporate.abc.com { ipaddr = 3.122.220.22 port = 1812 type = "auth" secret = "<removed>" response_window = 30 max_outstanding = 65536 zombie_period = 40 status_check = "none" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 300 status_check_timeout = 4 irt = 2 mrt = 16 mrc = 5 mrd = 30 } home_server radius.health.abc.com { virtual_server = "guns" port = 0 response_window = 30 max_outstanding = 65536 zombie_period = 40 status_check = "none" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 300 status_check_timeout = 4 irt = 2 mrt = 16 mrc = 5 mrd = 30 } home_server_pool abc_auth_failover { type = fail-over home_server = radius.corporate.abc.com fallback = radius.health.abc.com } realm NULL { auth_pool = abc_auth_failover } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "<removed>" 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 = "<removed>" nastype = "other" } client my_pc { ipaddr = 3.62.227.250 require_message_authenticator = no secret = "<removed>" } client ldom0001 { ipaddr = 3.62.48.76 require_message_authenticator = no secret = "<removed>" } 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 = "/usr/sfw/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 = 4096 } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } Module: Linked to sub-module rlm_eap_tls Module: Instantiating eap-tls tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 pem_file_type = yes private_key_file = "/etc/raddb/proxy/certs/server.pem" certificate_file = "/etc/raddb/proxy/certs/server.pem" CA_file = "/etc/raddb/proxy/certs/ca.pem" private_key_password = "<removed>" dh_file = "/etc/raddb/proxy/certs/dh" random_file = "/etc/raddb/proxy/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/etc/raddb/proxy/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/proxy/users" acctusersfile = "/etc/raddb/proxy/acct_users" preproxy_usersfile = "/etc/raddb/proxy/preproxy_users" compat = "no" } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/usr/sfw/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/proxy/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server guns { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_ldap Module: Instantiating ldap ldap { server = "mke-unix-dirsvc.abc.com" port = 389 password = "<removed>" identity = "uid=abcmenurw,cn=Directory Administrators,dc=abc,dc=com" net_timeout = 1 timeout = 4 timelimit = 3 tls_mode = no start_tls = no tls_require_cert = "allow" tls { start_tls = no require_cert = "allow" } basedn = "ou=accounts,ou=unixnm,dc=abc,dc=com" 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=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))" dictionary_mapping = "/etc/raddb/proxy/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: reading ldap<->radius mappings from file /etc/raddb/proxy/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: 183738 Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating preprocess preprocess { huntgroups = "/etc/raddb/proxy/huntgroups" hints = "/etc/raddb/proxy/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 = "/usr/sfw/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/proxy/attrs.accounting_response" key = "%{User-Name}" } Module: Checking session {...} 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: Checking preacct {...} for more modules to load Module: Checking accounting {...} for more modules to load 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 = "/usr/sfw/var/run/radiusd/radiusd.sock" } } listen { type = "auth" ipaddr = * port = 1822 } listen { type = "acct" ipaddr = * port = 1823 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/sfw/var/run/radiusd/radiusd.sock Listening on authentication address * port 1822 as server guns Listening on accounting address * port 1823 as server guns Listening on proxy address * port 1814 Ready to process requests. REQUEST #1 (to down corporate RADIUS server) ============================================ rad_recv: Access-Request packet from host 3.62.227.250 port 1948, id=58, length=66 User-Name = "le935529" User-Password = "<removed>" NAS-Identifier = "ABCResearchPark" +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "le935529", looking up realm NULL [suffix] Found realm "NULL" [suffix] Adding Stripped-User-Name = "le935529" [suffix] Adding Realm = "NULL" [suffix] Proxying request from user le935529 to realm NULL [suffix] Preparing to proxy authentication request to realm "NULL" ++[suffix] returns updated [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop WARNING: Empty section. Using default return values. Sending Access-Request of id 64 to 3.122.220.22 port 1812 User-Name = "le935529" User-Password = "<removed>" NAS-Identifier = "ABCResearchPark" NAS-IP-Address = 3.62.227.250 Proxy-State = 0x3538 Proxying request 0 to home server 3.122.220.22 port 1812 Sending Access-Request of id 64 to 3.122.220.22 port 1812 User-Name = "le935529" User-Password = "<removed>" NAS-Identifier = "ABCResearchPark" NAS-IP-Address = 3.62.227.250 Proxy-State = 0x3538 Going to the next request Waking up in 0.9 seconds. Waking up in 28.9 seconds. Marking home server 3.122.220.22 port 1812 as zombie (it looks like it is dead). Cleaning up request 0 ID 58 with timestamp +8 Ready to process requests. REQEUST #2 (to down corporate RADIUS server) ============================================ rad_recv: Access-Request packet from host 3.62.227.250 port 1951, id=59, length=66 User-Name = "le935529" User-Password = "<removed>" NAS-Identifier = "ABCResearchPark" +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "le935529", looking up realm NULL [suffix] Found realm "NULL" [suffix] Adding Stripped-User-Name = "le935529" [suffix] Adding Realm = "NULL" [suffix] Proxying request from user le935529 to realm NULL [suffix] Preparing to proxy authentication request to realm "NULL" ++[suffix] returns updated [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop WARNING: Empty section. Using default return values. Sending Access-Request of id 72 to 3.122.220.22 port 1812 User-Name = "le935529" User-Password = "<removed>" NAS-Identifier = "ABCResearchPark" NAS-IP-Address = 3.62.227.250 Proxy-State = 0x3539 Proxying request 1 to home server 3.122.220.22 port 1812 Sending Access-Request of id 72 to 3.122.220.22 port 1812 User-Name = "le935529" User-Password = "<removed>" NAS-Identifier = "ABCResearchPark" NAS-IP-Address = 3.62.227.250 Proxy-State = 0x3539 Going to the next request Waking up in 0.9 seconds. Waking up in 28.9 seconds. Marking home server 3.122.220.22 port 1812 as dead. Cleaning up request 1 ID 59 with timestamp +53 Waking up in 299.9 seconds. REQUEST #3 (corp is marked dead, successful LDAP Auth) ====================================================== rad_recv: Access-Request packet from host 3.62.227.250 port 1952, id=60, length=66 User-Name = "le935529" User-Password = "<removed>" NAS-Identifier = "ABCResearchPark" +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "le935529", looking up realm NULL [suffix] Found realm "NULL" [suffix] Adding Stripped-User-Name = "le935529" [suffix] Adding Realm = "NULL" [suffix] Proxying request from user le935529 to realm NULL [suffix] Preparing to proxy authentication request to realm "NULL" ++[suffix] returns updated [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop WARNING: Empty section. Using default return values. >>> Sending proxied request internally to virtual server. server guns { +- entering group authorize {...} ++[preprocess] returns ok [suffix] Request already proxied. Ignoring. ++[suffix] returns ok [ldap] performing user authorization for le935529 [ldap] expand: %{Stripped-User-Name} -> le935529 [ldap] expand: (uid=%{%{Stripped-User-Name}:-%{User-Name}}) -> (uid=le935529) [ldap] expand: ou=accounts,ou=unixnm,dc=abc,dc=com -> ou=accounts,ou=unixnm,dc=health,dc=ge,dc=com [ldap] ldap_get_conn: Checking Id: 0 [ldap] ldap_get_conn: Got Id: 0 [ldap] attempting LDAP reconnection [ldap] (re)connect to mke-unix-dirsvc.am.health.ge.com:389, authentication 0 [ldap] bind as uid=abcmenurw,cn=Directory Administrators,dc=abc,dc=com/<removed> to mke-unix-dirsvc.abc.com:389 [ldap] waiting for bind result ... [ldap] Bind was successful [ldap] performing search in ou=accounts,ou=unixnm,dc=ge,dc=com, with filter (uid=le935529) [ldap] looking for check items in directory... [ldap] looking for reply items in directory... WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? [ldap] Setting Auth-Type = LDAP [ldap] user le935529 authorized to use remote access [ldap] ldap_release_conn: Release Id: 0 ++[ldap] returns ok ++[expiration] returns noop ++[logintime] returns noop Found Auth-Type = LDAP +- entering group LDAP {...} [ldap] login attempt by "le935529" with password "<removed>" [ldap] user DN: uid=le935529,ou=people,ou=accounts,ou=unixnm,dc=abc,dc=com [ldap] (re)connect to mke-unix-dirsvc.abc.com:389, authentication 1 [ldap] bind as uid=le935529,ou=people,ou=accounts,ou=unixnm,dc=abc,dc=com/<removed> to mke-unix-dirsvc.abc.com:389 [ldap] waiting for bind result ... [ldap] Bind was successful [ldap] user le935529 authenticated succesfully ++[ldap] returns ok +- entering group post-auth {...} ++[exec] returns noop } # server guns Going to the next request <<< Received proxied response code 2 from internal virtual server. +- entering group post-proxy {...} [eap] No pre-existing handler found ++[eap] returns noop Found Auth-Type = Accept Auth-Type = Accept, accepting the user +- entering group post-auth {...} ++[exec] returns noop Sending Access-Accept of id 60 to 3.62.227.250 port 1952 Finished request 2. Going to the next request Waking up in 4.9 seconds. Cleaning up request 2 ID 60 with timestamp +105 Waking up in 272.1 seconds. Thanks in advance for your help! Troy

3 2

differentiate ldap
by cd 03 Feb '10

03 Feb '10

hi I have 2 ldap servers containing computers accounts with the same DN I don't know how differentiate access-accept or "ldap_1/2 returns ok" I want to put ldap_1's computers in vlan 1 and ldap_2 's computers in vlan 2 . What is the best practice to do this ? maybe with unlang ??? i've read the man authorize { ... group { ldap_1 ldap_2 } ... } authenticate{ Auth-Type ldap { group { ldap_1 { reject = 1 ok = return } ldap_2 { reject = 1 ok = return } } } Help please!

1 0

Another command authorization question
by Rija perso 03 Feb '10

03 Feb '10

Hi all, I'm trying to do per-command authorization with extreme networks switch (x450) and FR. According to extreme it's possible to do this with FR ... http://www.extremenetworks.com/libraries/services/ExtremeXOSConceptsGuideSo… page 816. "Command authorization is enabled in the users file on a FreeRADIUS server, and configured in the profiles file. Additional configuration is required in the dictionary file and the clients file." All you need is : -extreme VSA in dictionary -in users file : test Password = "test", Service-Type = Administrative, Profile-Name = "Profile1" Filter-Id = "unlim" Extreme:Extreme-CLI-Authorization = Enabled -in clients file : type:extreme:nas + RAD_RFC + ACCT_RFC -in profiles file (???) PROFILE1 deny { enable *, disable ipforwarding show switch } **** After some syntax tweaking : --Adding "Profile-Name" to dictionnary ATTRIBUTE Profile-Name 3500 string --adding in clients.conf client 10.0.0.10 { nastype = nas secret = XtremeSecret shortname = X450 } --adding in users file test Auth-Type := System, Service-Type := Administrative-User,Profile-Name := "PROFILE1" Service-Type = Administrative-User, Filter-Id = "unlim", Extreme-CLI-Authorization = Enabled --creating and filling /etc/freeradius/profiles file **** i've got : --- login to the switch : OK --- the switch send every user command to the FR server : OK --- FR check the "profiles" file to see if the user is authorized to execute this command : NOT OK It seems that FR don't care about the "profiles" file. The switch had only 2 level of authorization : - Service-Type = Administrative-User = read-write - Service-Type = anything else = read-only Maybe i've missed something ... My questions are : Is it possible to do what they claim with FR ? Is it possible to check an external file (by using external script) from "users" file or from any other FR config files to do the job ? Regards Rija

1 0

Default entry to allow all
by Godfrey Peart 03 Feb '10

03 Feb '10

At present my setup uses peap/ms-chapV2 to authenticate users is it possible to have an entry in the users file that will allow users to connect regardless of the username/password combo they input at the login box . I did try *DEFAULT Auth-Type := Accept*, but it didn't work rad_recv: Access-Request packet from host 10.10.3.29 port 1645, id=208, length=154 User-Name = "anything" Framed-MTU = 1400 Called-Station-Id = "0021.55ac.f2d0" Calling-Station-Id = "0013.0229.bf35" Cisco-AVPair = "ssid=swordfish" Service-Type = Login-User Message-Authenticator = 0x02152f851db652adcceccf557c2c9b5f EAP-Message = 0x0202000b01747972757275 NAS-Port-Type = Wireless-802.11 NAS-Port = 13008 NAS-Port-Id = "13008" NAS-IP-Address = 10.107.3.29 NAS-Identifier = "THEO" +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "anything", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 2 length 11 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[unix] returns notfound [files] users: Matched entry DEFAULT at line 207 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] Found existing Auth-Type, not changing it. ++[pap] returns noop Found Auth-Type = Accept Auth-Type = Accept, accepting the user +- entering group post-auth {...} ++[exec] returns noop Sending Access-Accept of id 208 to 10.10.3.29 port 1645 Finished request 0. Version: FR-2.1.8

3 2

Re:Default entry to allow all
by Godfrey Peart 03 Feb '10

03 Feb '10

I know, that's what baffling me, under my normal setup I get the TLS tunnel established and authentication works fine, but here there is no TLS setup just an accept mesage that matches the default entry but the client doesn't connect. Do I need to do any other tweaking concerning the peap setup

2 1