- Freeradius-Users - lists.freeradius.org

TLS: hostname does not match CN in peer certificate
by Ivan De Masi 18 Jun '12

18 Jun '12

Hello all, I have installed freeradius 2.1.10 on Debian Squeeze and configured to fetch the users on the ldap server. The access to the ldap server is secured with ssl (not TLS!), so openladp is listening on port 636. When I try # radtest user "mypassword" localhost 1 testing123 I get the following message: Reply-Message = "TLS: hostname does not match CN in peer certificate" Complete output: Sending Access-Request of id 137 to 127.0.0.1 port 1812 User-Name = "user" User-Password = "password" NAS-IP-Address = 127.0.1.1 NAS-Port = 1 rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=137, length=73 Reply-Message = "TLS: hostname does not match CN in peer certificate" That's correct, because I'm still in a testing phase and the openldap certificate doesn't match with the openldap hostname. But I need to fetch the data... What can I change to get it working? Is the only way to generate new certificate files? Thanks! Regards, Ivan

3 4

Freeradius accounting
by Павел Сорокин 18 Jun '12

18 Jun '12

hello. I use freeradius 2.1.12-5 with postgresql. I want to check every 10 minutes state of account? and if it's not valid disconnect it, but if it's valid to keep connection alive. How could I do this with freeradius. Wich parameter I have to use?

2 5

Configure FreeRadius to send CoA-ACK
by Gennaro Leo 18 Jun '12

18 Jun '12

Hi all, I installed FreeRadius and sent some Accounting Request through radclient but the server replies always with a CoA-NAK... how can I configure it to send CoA-ACK? Which file must be modified? Thanks in advance. Gennaro

2 1

Problem with EAP-TLS and certificate
by Stephane Brodeur 18 Jun '12

18 Jun '12

Hi, I am a newbie to Freeradius and I am having a real hard time to implement EAP-TLS using self-signed certificate. My certificate seems valid: Server Certificate [root@localhost CA]# openssl verify -CAfile /etc/pki/CA/cacert.pem xplab.pem xplab.pem: OK Client certificate [root@localhost CA]# openssl verify -CAfile /etc/pki/CA/cacert.pem bob.pem bob.pem: OK When I run [root@localhost CA]# eapol_test -c /opt/EAP-RADIUS/eap-tls.conf -s testing123, I have the following results: EAPOL: Successfully fetched key (len=32) PMK from EAPOL - hexdump(len=32): cf cd 8c f0 17 49 11 13 d6 7d fe cb b1 65 00 1d 85 c2 ef a5 33 35 78 00 b8 a1 0a 9d 02 4b 06 45 EAP: deinitialize previously used EAP method (13, TLS) at EAP deinit ENGINE: engine deinit MPPE keys OK: 1 mismatch: 0 SUCCESS using the following eap-tls.conf # eapol_test -c eap-tls.conf -s testing123 # network={ key_mgmt=IEEE8021X eap=TLS eapol_flags=0 eap_workaround=0 identity="bob" ca_cert="/etc/pki/CA/cacert.pem" client_cert="/etc/pki/CA/bob.der" private_key="/etc/pki/CA/bob.key" private_key_passwd="abc123" # # Uncomment the following to perform server certificate validation. ca_cert="/etc/pki/CA/cacert.pem" } My problem is the following error message when running eapol_test TLS: Trusted root certificate(s) loaded OpenSSL: SSL_use_certificate_file (DER) --> OK OpenSSL: tls_connection_private_key - SSL_use_PrivateKey_File (DER) failed error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag OpenSSL: pending error: error:0D08303A:asn1 encoding routines:ASN1_TEMPLATE_NOEXP_D2I:nested asn1 error OpenSSL: pending error: error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag OpenSSL: pending error: error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error OpenSSL: pending error: error:04093004:rsa routines:OLD_RSA_PRIV_DECODE:RSA lib OpenSSL: pending error: error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag OpenSSL: pending error: error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error OpenSSL: pending error: error:140CB00D:SSL routines:SSL_use_PrivateKey_file:ASN1 lib OpenSSL: SSL_use_PrivateKey_File (PEM) --> OK SSL: Private key loaded successfully CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected I would like to know if this means that my certificates are not valid even if the eapol_test seems successful. I was not able to find any information on the meaning of these messages. These messages are similar to what I have when I run the wpa_supplicant from my client machine. Since I am not able to authenticate from wpa_supplicant (failed to private key), I think that it might be possible that the certificate are wrong. wpa_supplicant.conf ap_scan=0 network={ key_mgmt=WPA-EAP eap=TLS identity="bob" ca_cert="/etc/ssl/demoCA/cacert.pem" client_cert="/etc/ssl/demoCA/certs/bob.pem" private_key="/etc/ssl/demoCA/private/bob.key" private_key_passwd="abc123" eapol_flags=0 } wpa_supplicant -c /etc/wpa_supplicant.conf -D wired -i br0 CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13 OpenSSL: pending error: error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error OpenSSL: pending error: error:140C800D:SSL routines:SSL_use_certificate_file:ASN1 lib OpenSSL: pending error: error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag OpenSSL: pending error: error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error OpenSSL: pending error: error:0D09A00D:asn1 encoding routines:d2i_PrivateKey:ASN1 lib OpenSSL: pending error: error:140CB00D:SSL routines:SSL_use_PrivateKey_file:ASN1 lib OpenSSL: pending error: error:23077073:PKCS12 routines:PKCS12_pbe_crypt:pkcs12 algor cipherinit error OpenSSL: pending error: error:2306A075:PKCS12 routines:PKCS12_item_decrypt_d2i:pkcs12 pbe crypt error OpenSSL: pending error: error:0907B00D:PEM routines:PEM_READ_BIO_PRIVATEKEY:ASN1 lib OpenSSL: pending error: error:140CB009:SSL routines:SSL_use_PrivateKey_file:PEM lib OpenSSL: tls_read_pkcs12 - Failed to use PKCS#12 file error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag OpenSSL: pending error: error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error OpenSSL: Failed to load private key Thanks for your help Stephane

3 2

Handling of Duplicate Accounting Requests
by Ramakrishna 18 Jun '12

18 Jun '12

Hi, I have freeradius-2.1.12 installed on Solaris server. I have written one new module rlm_xyz which i am using to handle both authentication and accounting requests from NAS. When authentication fails, I am replying with Access-Reject message but when Accounting request fails, I am not sending any reply to the NAS. Since NAS doesn't get reply, it is resending the same accounting request to the server. My problem is i want the free radius stack to handle the duplicate requests instead of passing the request to my rlm_xyz module. Please lemme know if any configuration details are required. Thanks in advance. -- View this message in context: http://freeradius.1045715.n5.nabble.com/Handling-of-Duplicate-Accounting-Re… Sent from the FreeRadius - User mailing list archive at Nabble.com.

2 1

802.1x, deault windows supplicant and kerberos
by Adrian Czapek 18 Jun '12

18 Jun '12

Hello, I wonder if it is possible to configure freeradius to authenticate default windows supplicants (offering PEAP only method) to authenticate users in wired network against kerberos. I have working configuration - freeradius can succesfully authenticate users against kerberos using DEFULT Auth-Type = Kerberos in users file: Found Auth-Type = Kerberos # Executing group from file /etc/raddb/sites-enabled/default +- entering group Kerberos {...} rlm_krb5: verify_krb_v5_tgt: host key not found : Key table entry not found ++[krb5] returns ok # Executing section post-auth from file /etc/raddb/sites-enabled/default +- entering group post-auth {...} ++[exec] returns noop ++[reply] returns noop Sending Access-Accept of id 11 to 10.5.200.201 port 1645 Service-Type = NAS-Prompt-User Cisco-AVPair = "shell:priv-lvl=15" Finished request 0. Going to the next request Now I would like to protect ethernet network with 802.1x protocol. I am stuck, because I don't have User-Password inside of the PEAP tunnel (I know the reason why I don;t have that password there, no need to explain :)) which is needed for kerberos module. Is there any other method to get it working ? I've googled out some info about using ttls tunnel instead of peap, but I have no idea how to force windows supplicants to do so. Best regards -- Adrian

3 3

Virtual Server Pool Problem
by manny 16 Jun '12

16 Jun '12

Hello all, I am attempting to setup a FreeRADIUS server to listen only on one IP address, but have two virtual servers. At the moment I am testing with simple servers, one that accepts and one that rejects. I have a freeradius server that is dependent on another server, and want to provide an alternate authentication method when the server is down. I sort of have an idea but i feel far from getting to a working setup. The following is part of my setup configuration. listen { type = auth ipaddr = 192.168.100.251 port = 1812 virtual_server = primary } listen { ipaddr = 192.168.100.251 port = 1813 type = acct virtual_server = primary } server primary { authorize { update control { Auth-Type := Reject } } ... } server secondary { authorize { update control { Auth-Type := Accept } } } proxy server { default_fallback = yes } home_server first { type = auth+acct ipaddr = 192.168.100.251 #virtual_server = primary port = 1812 secret = secret require_message_authenticator = no ... } home_server second { virtual_server = secondary type = auth+acct port = 1822 secret = secret } home_server_pool my_auth_failover { type = fail-over home_server = first home_server = second } This is the result from radtest [root@chive raddb]# radtest test test123 192.168.100.251 1812 secret Sending Access-Request of id 239 to 192.168.100.251 port 1812 User-Name = "test" User-Password = "test123" NAS-IP-Address = 127.0.0.1 NAS-Port = 1812 rad_recv: Access-Reject packet from host 192.168.100.251 port 1812, id=239, length=20 [root@chive raddb]# This is the result after I use radmin to set home_server as dead (set home_server state 192.168.100.251 812 dead): [root@localhost raddb]# radtest test test123 192.168.100.251 1812 secret Sending Access-Request of id 1 to 192.168.100.251 port 1812 User-Name = "test" User-Password = "test123" NAS-IP-Address = 127.0.0.1 NAS-Port = 1812 rad_recv: Access-Reject packet from host 192.168.100.251 port 1812, id=1, length=20 [root@localhost raddb]# It is my understanding that once a home_server is dead, it tries the next one, but here I see that port 1812 is still used instead of 1822. Your help is greatly appreciated. Thanks, Manny ----- Test. -- View this message in context: http://freeradius.1045715.n5.nabble.com/Virtual-Server-Pool-Problem-tp57136… Sent from the FreeRadius - User mailing list archive at Nabble.com.

2 4

Difference between local and external in inner-tunnel
by Alberto Martínez 15 Jun '12

15 Jun '12

o/ Our FR is doing EAP most of the time, and it's working fine. However, we would want our NAS to see the inner true User-Name, not the outer one. I know this can be set in the inner-tunnel post-auth section uncommenting the update outer.reply lines, but that exposes our users' inner User-Name to proxied-to-us authentications. So my question is: Which attributes should I check to tell apart local and external auths? Best regards, Alberto

5 6

rlm_perl module not executing authenticate
by Diego Matute 15 Jun '12

15 Jun '12

I've installed freeradius and other packages on a vanilla amazon ec2 instance and am trying to get the rlm_perl module working. Ultimately the authenticate function in the perl script is not being run. Here are the details. Running: Amazon Linux AMI release 2012.03 Install: $ sudo yum update $ sudo yum install freeradius $ sudo yum install freeradius-perl $ sudo yum install freeradius-utils Configuration files: /etc/raddb/modules/perl: perl { # # The Perl script to execute on authorize, authenticate, # accounting, xlat, etc. This is very similar to using # 'rlm_exec' module, but it is persistent, and therefore # faster. # module = /etc/raddb/example.pl ... } /etc/raddb/sites-enabled/default: authorize { ... perl ... } authenticate { ... perl ... } accounting { ... perl ... } rlm_perl files: /etc/raddb/example.pl: # Function to handle authorize sub authorize { # For debugging purposes only &log_request_attributes; print "authorize!!!"; # Here's where your authorization code comes # You can call another function from here: &test_call; return RLM_MODULE_OK; } # Function to handle authenticate sub authenticate { # For debugging purposes only # &log_request_attributes; print "authenticate!!!"; ... Testing: $ radtest test test localhost 0 testing123 Sending Access-Request of id 154 to 127.0.0.1 port 1812 User-Name = "test" User-Password = "test" NAS-IP-Address = 10.111.61.150 NAS-Port = 0 rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=154, length=20 Server output: $ sudo radiusd -X FreeRADIUS Version 2.1.10, for host x86_64-redhat-linux-gnu, built on Feb 13 2012 at 23:13:41 Copyright (C) 1999-2009 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License v2. Starting - reading configuration files ... including configuration file /etc/raddb/radiusd.conf including configuration file /etc/raddb/proxy.conf including configuration file /etc/raddb/clients.conf including files in directory /etc/raddb/modules/ including configuration file /etc/raddb/modules/detail.example.com including configuration file /etc/raddb/modules/mschap including configuration file /etc/raddb/modules/perl including configuration file /etc/raddb/modules/chap including configuration file /etc/raddb/modules/files including configuration file /etc/raddb/modules/sradutmp including configuration file /etc/raddb/modules/mac2ip including configuration file /etc/raddb/modules/radutmp including configuration file /etc/raddb/modules/logintime including configuration file /etc/raddb/modules/etc_group including configuration file /etc/raddb/modules/dynamic_clients including configuration file /etc/raddb/modules/detail.log including configuration file /etc/raddb/modules/realm including configuration file /etc/raddb/modules/mac2vlan including configuration file /etc/raddb/modules/passwd including configuration file /etc/raddb/modules/linelog including configuration file /etc/raddb/modules/expr including configuration file /etc/raddb/modules/expiration including configuration file /etc/raddb/modules/opendirectory including configuration file /etc/raddb/modules/unix including configuration file /etc/raddb/modules/attr_rewrite including configuration file /etc/raddb/modules/attr_filter including configuration file /etc/raddb/modules/smbpasswd including configuration file /etc/raddb/modules/detail including configuration file /etc/raddb/modules/smsotp including configuration file /etc/raddb/modules/cui including configuration file /etc/raddb/modules/otp including configuration file /etc/raddb/modules/policy including configuration file /etc/raddb/modules/sql_log including configuration file /etc/raddb/modules/digest including configuration file /etc/raddb/modules/always including configuration file /etc/raddb/modules/wimax including configuration file /etc/raddb/modules/counter including configuration file /etc/raddb/modules/preprocess including configuration file /etc/raddb/modules/exec including configuration file /etc/raddb/modules/ntlm_auth including configuration file /etc/raddb/modules/echo including configuration file /etc/raddb/modules/pam including configuration file /etc/raddb/modules/checkval including configuration file /etc/raddb/modules/acct_unique including configuration file /etc/raddb/modules/ippool including configuration file /etc/raddb/modules/inner-eap including configuration file /etc/raddb/modules/pap including configuration file /etc/raddb/modules/sqlcounter_expire_on_login including configuration file /etc/raddb/eap.conf including configuration file /etc/raddb/policy.conf including files in directory /etc/raddb/sites-enabled/ including configuration file /etc/raddb/sites-enabled/control-socket including configuration file /etc/raddb/sites-enabled/inner-tunnel including configuration file /etc/raddb/sites-enabled/default main { user = "radiusd" group = "radiusd" allow_core_dumps = no } including dictionary file /etc/raddb/dictionary main { prefix = "/usr" localstatedir = "/var" logdir = "/var/log/radius" libdir = "/usr/lib64/freeradius" radacctdir = "/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/var/run/radiusd/radiusd.pid" checkrad = "/usr/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = no auth_badpass = no auth_goodpass = no } security { max_attributes = 200 reject_delay = 1 status_server = yes } } radiusd: #### Loading Realms and Home Servers #### proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 require_message_authenticator = yes zombie_period = 40 status_check = "status-server" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 irt = 2 mrt = 16 mrc = 5 mrd = 30 } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating module "exec" from file /etc/raddb/modules/exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating module "expr" from file /etc/raddb/modules/expr Module: Linked to module rlm_expiration Module: Instantiating module "expiration" from file /etc/raddb/modules/expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating module "logintime" from file /etc/raddb/modules/logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { # from file /etc/raddb/sites-enabled/inner-tunnel modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating module "pap" from file /etc/raddb/modules/pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating module "chap" from file /etc/raddb/modules/chap Module: Linked to module rlm_mschap Module: Instantiating module "mschap" from file /etc/raddb/modules/mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating module "unix" from file /etc/raddb/modules/unix unix { radwtmp = "/var/log/radius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating module "eap" from file /etc/raddb/eap.conf 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 CA_path = "/etc/raddb/certs" pem_file_type = yes private_key_file = "/etc/raddb/certs/server.pem" certificate_file = "/etc/raddb/certs/server.pem" CA_file = "/etc/raddb/certs/ca.pem" private_key_password = "whatever" dh_file = "/etc/raddb/certs/dh" random_file = "/etc/raddb/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" cache { enable = no lifetime = 24 max_entries = 255 } verify { } } 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 module "suffix" from file /etc/raddb/modules/realm realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating module "files" from file /etc/raddb/modules/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 module "radutmp" from file /etc/raddb/modules/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 module "attr_filter.access_reject" from file /etc/raddb/modules/attr_filter attr_filter attr_filter.access_reject { attrsfile = "/etc/raddb/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server { # from file /etc/raddb/radiusd.conf modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_digest Module: Instantiating module "digest" from file /etc/raddb/modules/digest Module: Linked to module rlm_perl Module: Instantiating module "perl" from file /etc/raddb/modules/perl perl { module = "/etc/raddb/example.pl" func_authorize = "authorize" func_authenticate = "authenticate" func_accounting = "accounting" func_preacct = "preacct" func_checksimul = "checksimul" func_detach = "detach" func_xlat = "xlat" func_pre_proxy = "pre_proxy" func_post_proxy = "post_proxy" func_post_auth = "post_auth" func_recv_coa = "recv_coa" func_send_coa = "send_coa" } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating module "preprocess" from file /etc/raddb/modules/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 module "acct_unique" from file /etc/raddb/modules/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 module "detail" from file /etc/raddb/modules/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 module "attr_filter.accounting_response" from file /etc/raddb/modules/attr_filter 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" } } listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /var/run/radiusd/radiusd.sock Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1 port 52493, id=154, length=56 User-Name = "test" User-Password = "test" NAS-IP-Address = 10.111.61.150 NAS-Port = 0 # Executing section authorize from file /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 = "test", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[files] returns noop rlm_perl: RAD_REQUEST: User-Name = test rlm_perl: RAD_REQUEST: User-Password = test rlm_perl: RAD_REQUEST: NAS-Port = 0 rlm_perl: RAD_REQUEST: NAS-IP-Address = 10.111.61.150 rlm_perl: Added pair User-Name = test rlm_perl: Added pair User-Password = test rlm_perl: Added pair NAS-Port = 0 rlm_perl: Added pair NAS-IP-Address = 10.111.61.150 ++[perl] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user Failed to authenticate the user. Using Post-Auth-Type Reject # Executing group from file /etc/raddb/sites-enabled/default +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> test attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 0 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 0 Sending Access-Reject of id 154 to 127.0.0.1 port 52493 Waking up in 4.9 seconds. Cleaning up request 0 ID 154 with timestamp +3 Ready to process requests. Questions: 1/ Request comes in and authorize is being called within rlm_perl. The print statement is not outputting on the server side? 2/ How does Auth-Type get set? I've read a bunch of forum threads and it looks like best practice nowadays is to let the server figure it out and not set it explicitly in /etc/raddb/users, however it isn't being set. Suggestions? Cheers and thanks.

3 6

[PATCH] fix connection limits
by Brian Julin 14 Jun '12

14 Jun '12

Attached is an improved version of one of the patches originally posted here. http://lists.freeradius.org/pipermail/freeradius-users/2012-May/060820.html It moves decrements of socket/client num_connections counters into event_new_fd so that it happens on all paths by which a connection may be removed. As the code now stands, when a connection is terminated by the other side, num_connections continues to count it towards connection limits. (Note that with the above code, num_connections will still count a dead connection towards limits until it has been abandoned by all users and cleaned up. Also I'm not completely sure this is immune to races since I haven't yet figured out if the connection garbage collection might be reentrant.) This has been tested in a radsec pure-proxy relay setup. It has not yet been tested in an AS setup.

1 0