January 2012 - Freeradius-Devel - lists.freeradius.org

rlm_sql_ocioracle driver v. 0.1
by Ge＠＠ru 14 Mar '15

14 Mar '15

Hi, in attachment patch to add rlm_sql_ocioracle driver to freeradius 2.1.x tree (it seems work yet on 3.x tree). This drivers permit to use function/procedure with CURSOR (through :Ret_Cursor string) like for example: group_membership_query = "begin :Ret_Cursor := \ pkRadius.group_membership_query('%{SQL-User-Name}'); end;" TODO for next release: - add support to oracle connection pool instead of open a new connection for every socket on startup; - enhancement on handle error (through error callback) on do query; - add documentation. Module need oracle instantclient library and ocilib library (http://orclib.sourceforge.net/) Good luck to rlm_sql_ocioracle driver!! Geaaru

2 5

Complete authorize & accounting redis module
by Manuel Guesdon 31 Oct '12

31 Oct '12

Hi, I've adapted rlm_sql to REDIS (http://redis.io/) key-store database. It handle authorize, accounting, checksimul and post-auth (only authorize is deeply tested). Authorize works like rlm_sql with groups, etc... Files are here: http://free.oxymium.net/freeradius/rlm_redisn/ Available as .tgz here: http://free.oxymium.net/freeradius/rlm_redisn-20111112-001.tgz Manuel -- ______________________________________________________________________ Manuel Guesdon - OXYMIUM

4 11

New build system
by Alan DeKok 21 Sep '12

21 Sep '12

OK, I've fixed a bug with dependencies, where it wouldn't re-build a C file if a header changed. I've also added some "configure" support. So modules like rlm_pam, python, perl, etc. only get built if their prerequisites are found. One benefit is that "make -j 8" now works. On my quad-core system I get this: $ time make -j 8 clean all ... real 0m4.357s user 0m24.702s sys 0m3.580s A complete build in less than 5 seconds. Very nice! Alan DeKok.

4 6

RE: Not verifying username in EAP-TLS
by Verma Anurag-VNF673 30 Jan '12

30 Jan '12

Looks like the link below may provide what I need. I will try this out. http://www.dartmouth.edu/~pkilab/pages/EAP-TLSwFreeRadius.html From: Verma Anurag-VNF673 Sent: Friday, January 27, 2012 5:50 PM To: 'freeradius-devel(a)lists.freeradius.org' Subject: Not verifying username in EAP-TLS Hi, I want to bypass user verification when using EAP-TLS - i.e. freeRADIUS should only verify the certificate validity without verifying that the user name, contained in CN part of the Subject field in the certificate, is present in the user database. Is it possible to do this? If so, what should the configuration look like? Thanks, Anurag

1 0

Not verifying username in EAP-TLS
by Verma Anurag-VNF673 27 Jan '12

27 Jan '12

Hi, I want to bypass user verification when using EAP-TLS - i.e. freeRADIUS should only verify the certificate validity without verifying that the user name, contained in CN part of the Subject field in the certificate, is present in the user database. Is it possible to do this? If so, what should the configuration look like? Thanks, Anurag

3 2

New build system in "master" branch
by Alan DeKok 27 Jan '12

27 Jan '12

After 10+ years of fighting recursive make, I've committed a new system. It's only used if you want, by editing Make.inc, and adding a line: BOILER=yes When you do that, the build should be MUCH faster. Everything goes into a "build" directory, so don't look for libs/binaries in their usual places. On my system, the build is rather a lot faster. Anyone doing even occasional development should look into using it. Let me know what you think. Alan DeKok.

4 18

DHCP + sqlpippol test, v2.1.x
by Fajar A. Nugraha 25 Jan '12

25 Jan '12

Hi, I'm testing some modifications to make DHCP able to allocate dynamic IP address using sqlippool. It's only tested with one client, but it should be able to assign dynamic IP address (smallest ip address first, due to sorting). The modification is purely config files addition/modification, no source code change. Current version is here: https://github.com/fajarnugraha/freeradius-server/commit/8af7142 Static IP allocation SHOULD also be possible by having expiration time far in the future (e.g. 2100-01-01 00:00:00) on radippool table, and modifying the query to NOT overwrite the expiration time on that scenario. This hasn't been implemented though. Any thoughts on these changes? Perhaps there a simpler way to implement it. -- Fajar

3 11

Why using username instead of user id?
by Morteza Milani 24 Jan '12

24 Jan '12

In freeradius sql modules, queries are based on username instead of user id. Is it anything related to performance or it went in this way without any decision? Using username has two problems: * updating a username, or deleting one needs querying at least three tables. * Comparing strings needs more time than comparing integers when fetching data. Regards, Morteza Milani

5 8

ocsp timeout and server failure
by Matthew Newton 23 Jan '12

23 Jan '12

Hi, If freeradius tries to talk to an OCSP responder, and the server is not available for some reason, the ocsp check gets stuck for a while, then bombs out with (as expected) a verification failure. The two problems are that it takes quite a while for the client to be told it can't connect, and clients with good certificates can't connect. The obvious solution is to make the ocsp server more resilient, but that's not always going to be possible. The easy solution to the problem of the server temporarily going away seems to be to add a "soft-fail" option, whereby the server will accept the certificate if it can't talk to the OCSP responder. This obviously has some security implications so can't be done unless it's been thought through properly. However, even adding this feature doesn't solve the problem, as the whole client access request fails because the OCSP takes so long to timeout (depending on failure mode). I'm guessing a reasonable solution, apart from high availability OCSP, is to have a short timeout on the ocsp query, then enable success if the server fails to respond (e.g. the certificate can't be checked), and to also use CRLs that are updated frequently. OCSP can then be used as an 'immediate' solution, whereas the CRL is the more permanent in case OCSP isn't available. I've written two smallish patches against v2.1.x - the first adds a 'timeout' option to the ocsp section. This gives up checking after the set number of seconds. I've tested this code through several different scenarios and it seems to all behave as expected (setting timeout=0, the default, has the same behaviour as before): https://github.com/mcnewton/freeradius-server/commit/56d6093828839ece191dad… The second option adds the option 'softfail', which by default is "no" (the safer option). In the case it's set to yes, a failure to query the server (or get a response) is treated as a success in terms of validation. There are warnings in the eap.conf file that this is not entirely secure, so needs to be assessed according to the risk. It's a simpler patch from the above, and applies on top: https://github.com/mcnewton/freeradius-server/commit/119ac969d8c658934d86de… Comments? Cheers, Matthew -- Matthew Newton, Ph.D. <mcn4(a)le.ac.uk> Systems Architect (UNIX and Networks), Network Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp(a)le.ac.uk>

2 2

Re: Why using username instead of user id?
by Morteza Milani 23 Jan '12

23 Jan '12

I couldn't get my answer! > On one of my systems, we use ids. It's somewhat complicated though: > - use stored procedures, as I need to use several statements to > achieve the same functionality. It's better than joins (which is very > expensive in mysql cluster) >- lookup user id based on username (on an additional table, obviously) >- lookup other properties (e.g. radcheck, radreply, etc.) based on the id The only extra step required is to lookup user id from another table. Then we can use it instead of username in all queries. To achieve this, we can set User-Name to that id. Maybe I'm missing something. I really want that "live" and "historical" tables implemented. I have 35000 users and I need fetching data from radacct for statistical analysis. It's a heavy table! Morteza Milani

3 2

RADIUS & Billing MVTS Pro
by Mohamed Daif 20 Jan '12

20 Jan '12

Hello, I have installed two servers with MVTS PRO installed on both servers , supports 600 concurrent calls. and i installed one server with FreeRADIUS to manage both servers and billing "with daloRADIUS". and i have some needs must to be in the FreeRADIUS to manage the calls . all calls must be checked firstly from two tables then go to Specific Gateways like below : 1 - BlackList : to block calls to numbers from the BlackList table , 2 - WhiteList : to send calls to numbers from the WhiteList table to White Gateways 3 - Other calls not stored in both tables must be send to Checking Gateways . 4 - if calls have a good CDR must be storing in WhiteList . 5 - other calls have a bad CDR must be storing in BlackList . I want to have free choice for activate checking from both tables or one of both tables or don't check any tables for each client individually. how can i add both tables to FreeRADIUS and make configuration to check before sending calls to MVTS Servers. -- *Best Regards Mohamed Daif*

1 0

mods-available and mods-enabled for v2.1.x
by Fajar A. Nugraha 19 Jan '12

19 Jan '12

Hi Alan, I've ported mods-available and mods-enabled to v2.1.x, but with a different approach that what was implemented in master. It's currently a patch to the debian directory which will only affect debian package. Full commit: https://github.com/fajarnugraha/freeradius-server/commit/a4e2942 The idea is: - exisisting debian/ubuntu with freeradius package installed can upgrade to latest version and (if they choose to keep old radiusd.conf) have everything continue to work just as it was before (modules are loaded from modules/ directory) - new users (or those chose to replace radiusd.conf with the one in the package) will get 3.x behavior (modules loaded from mods-enabled/) - mods-availabe is just a symlink to modules - everything that's in mods-available (or to be accurate, everything listed in DEFAULT_MODULES) is symlinked to mods-enabled If you're interested in applying the change upstream (not just for debian build), the alternate commit is here: https://github.com/fajarnugraha/freeradius-server/commit/284198c -- Fajar

2 2

RADIUS & Billing for MVTS
by Mohamed Daif 16 Jan '12

16 Jan '12

Hello, I have installed two servers with MVTS PRO installed on both servers , supports 600 concurrent calls. and i need install one server with FreeRADIUS to manage both servers and billing . and i have some needs must to be in the FreeRADIUS to manage the calls . all calls must be checked firstly from two tables then go to Specific Gateways like below : 1 - BlackList : to block calls to numbers from the BlackList table , 2 - WhiteList : to send calls to numbers from the WhiteList table to White Gateways 3 - Other calls not stored in both tables must be send to Checking Gateways . 4 - if calls have a good CDR must be storing in WhiteList . 5 - other calls have a bad CDR must be storing in BlackList . I want to have free choice for activate checking from both tables or one of both tables or don't check any tables for each client individually. -- *Best Regards Mohamed Daif*

1 0

Patch to add /etc/default/freeradius to debian package
by Matthew Newton 14 Jan '12

14 Jan '12

Hi, Another simple patch - this one adds /etc/default/freeradius to the debian package to allow daemon options to be easily set. I sent the patch to Debian and it was included a year or so ago (closed debian bug #564716), but not yet in the main distribution. https://github.com/mcnewton/freeradius-server/commit/5d0d6d23b27949ba8c3504… Cheers! Matthew commit 5d0d6d23b27949ba8c35049ae5008bd4b9ebf748 Author: Matthew Newton <mcn4(a)leicester.ac.uk> Date: Wed Jan 11 15:40:52 2012 +0000 Add /etc/default/freeradius to debian package This gives an easy way to supply options to the daemon when starting it using the init.d script. diff --git a/debian/freeradius.default b/debian/freeradius.default new file mode 100644 index 0000000..1c31908 --- /dev/null +++ b/debian/freeradius.default @@ -0,0 +1,3 @@ +# Options for the FreeRADIUS deamon. +#FREERADIUS_OPTIONS="-d /etc/freeradius" + diff --git a/debian/freeradius.init b/debian/freeradius.init index 0738914..985c044 100755 --- a/debian/freeradius.init +++ b/debian/freeradius.init @@ -21,6 +21,10 @@ PROGRAM="/usr/sbin/freeradius" PIDFILE="/var/run/freeradius/freeradius.pid" DESCR="FreeRADIUS daemon" +if [ -r /etc/default/$PROG ]; then + . /etc/default/$PROG +fi + test -f $PROGRAM || exit 0 # /var/run may be a tmpfs @@ -36,7 +40,7 @@ ret=0 case "$1" in start) log_daemon_msg "Starting $DESCR" "$PROG" - start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $PROGRAM || ret=$? + start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $PROGRAM -- $FREERADIUS_OPTIONS || ret=$? log_end_msg $ret exit $ret ;; -- Matthew Newton, Ph.D. <mcn4(a)le.ac.uk> Systems Architect (UNIX and Networks), Network Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp(a)le.ac.uk>

2 1

Fix typo in rlm_dbm_parser man page
by John Dennis 14 Jan '12

14 Jan '12

rlm_dbm_parser is installed in /usr/bin but it's man page (and it's contents) call it rlm_dbm_parse (note the missing trailing r). The name of the man page and the executable it documents need to match. Attached is a git patch (can be applied with git am) to fix the naming. It should be applied to all the branches. John -- John Dennis <jdennis(a)redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/

2 1

DHCP: ARP issue, FR2.x vs FR 3.x
by Fajar A. Nugraha 13 Jan '12

13 Jan '12

I'm trying to test a simple DHCP server implementation using FR. The setup: - server is using dummy1 interface for dhcp server test purposes, IP 172.16.101.1 - client is using virtualbox running on server, with client's eth0 bridged to server's dummy1, tested using client's "dhclient" command. - basic DHCP test using dnsmasq and FR 3 (with freeradius -X) on server works fine, so there's no issue about using dummy interface and virtualbox. Then I test FR 2.2.0 (from v2.1.x git). The dhcp listen section is different, so I adusted it accordingly. But there seems to be a problem with arp, and the reply never recached the client (also confirmed with tcpdump). Any idea how to make FR2's DHCP work, or at least behaves similar to FR3? FR2 debug log: #=========================================================================== root@HP:/# freeradius -X FreeRADIUS Version 2.2.0, for host i686-pc-linux-gnu, built on Jan 11 2012 at 17:20:48 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/freeradius/radiusd.conf including configuration file /etc/freeradius/proxy.conf including configuration file /etc/freeradius/clients.conf including files in directory /etc/freeradius/modules/ including configuration file /etc/freeradius/modules/radutmp including configuration file /etc/freeradius/modules/realm including configuration file /etc/freeradius/modules/detail.log including configuration file /etc/freeradius/modules/linelog including configuration file /etc/freeradius/modules/rediswho including configuration file /etc/freeradius/modules/krb5 including configuration file /etc/freeradius/modules/expr including configuration file /etc/freeradius/modules/cui including configuration file /etc/freeradius/modules/replicate including configuration file /etc/freeradius/modules/sradutmp including configuration file /etc/freeradius/modules/checkval including configuration file /etc/freeradius/modules/digest including configuration file /etc/freeradius/modules/policy including configuration file /etc/freeradius/modules/unix including configuration file /etc/freeradius/modules/opendirectory including configuration file /etc/freeradius/modules/counter including configuration file /etc/freeradius/modules/perl including configuration file /etc/freeradius/modules/chap including configuration file /etc/freeradius/modules/redis including configuration file /etc/freeradius/modules/attr_filter including configuration file /etc/freeradius/modules/ntlm_auth including configuration file /etc/freeradius/modules/mac2ip including configuration file /etc/freeradius/modules/files including configuration file /etc/freeradius/modules/etc_group including configuration file /etc/freeradius/modules/expiration including configuration file /etc/freeradius/modules/smsotp including configuration file /etc/freeradius/modules/exec including configuration file /etc/freeradius/modules/acct_unique including configuration file /etc/freeradius/modules/ippool including configuration file /etc/freeradius/modules/detail.example.com including configuration file /etc/freeradius/modules/inner-eap including configuration file /etc/freeradius/modules/pap including configuration file /etc/freeradius/modules/wimax including configuration file /etc/freeradius/modules/mschap including configuration file /etc/freeradius/modules/pam including configuration file /etc/freeradius/modules/smbpasswd including configuration file /etc/freeradius/modules/otp including configuration file /etc/freeradius/modules/echo including configuration file /etc/freeradius/modules/sql_log including configuration file /etc/freeradius/modules/soh including configuration file /etc/freeradius/modules/ldap including configuration file /etc/freeradius/modules/preprocess including configuration file /etc/freeradius/modules/always including configuration file /etc/freeradius/modules/mac2vlan including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login including configuration file /etc/freeradius/modules/attr_rewrite including configuration file /etc/freeradius/modules/logintime including configuration file /etc/freeradius/modules/dynamic_clients including configuration file /etc/freeradius/modules/detail including configuration file /etc/freeradius/modules/passwd including configuration file /etc/freeradius/modules/radrelay including configuration file /etc/freeradius/eap.conf including configuration file /etc/freeradius/policy.conf including files in directory /etc/freeradius/sites-enabled/ including configuration file /etc/freeradius/sites-enabled/default including configuration file /etc/freeradius/sites-enabled/inner-tunnel including configuration file /etc/freeradius/sites-enabled/dhcp main { user = "freerad" group = "freerad" allow_core_dumps = no } including dictionary file /etc/freeradius/dictionary main { name = "freeradius" prefix = "/usr" localstatedir = "/var" sbindir = "/usr/sbin" logdir = "/var/log/freeradius" run_dir = "/var/run/freeradius" libdir = "/usr/lib/freeradius" radacctdir = "/var/log/freeradius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/var/run/freeradius/freeradius.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 coa { 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/freeradius/modules/exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating module "expr" from file /etc/freeradius/modules/expr Module: Linked to module rlm_expiration Module: Instantiating module "expiration" from file /etc/freeradius/modules/expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating module "logintime" from file /etc/freeradius/modules/logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server { # from file /etc/freeradius/radiusd.conf modules { Module: Creating Auth-Type = digest Module: Creating Post-Auth-Type = REJECT Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating module "pap" from file /etc/freeradius/modules/pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating module "chap" from file /etc/freeradius/modules/chap Module: Linked to module rlm_mschap Module: Instantiating module "mschap" from file /etc/freeradius/modules/mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no allow_retry = yes } Module: Linked to module rlm_digest Module: Instantiating module "digest" from file /etc/freeradius/modules/digest Module: Linked to module rlm_unix Module: Instantiating module "unix" from file /etc/freeradius/modules/unix unix { radwtmp = "/var/log/freeradius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating module "eap" from file /etc/freeradius/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/freeradius/certs" pem_file_type = yes private_key_file = "/etc/freeradius/certs/server.key" certificate_file = "/etc/freeradius/certs/server.pem" CA_file = "/etc/freeradius/certs/ca.pem" private_key_password = "whatever" dh_file = "/etc/freeradius/certs/dh" random_file = "/dev/urandom" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/etc/freeradius/certs/bootstrap" ecdh_curve = "prime256v1" cache { enable = no lifetime = 24 max_entries = 255 } verify { } ocsp { enable = no override_cert_url = yes url = "http://127.0.0.1/ocsp/" } } 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" soh = no } Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no send_error = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating module "preprocess" from file /etc/freeradius/modules/preprocess preprocess { huntgroups = "/etc/freeradius/huntgroups" hints = "/etc/freeradius/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: Linked to module rlm_realm Module: Instantiating module "suffix" from file /etc/freeradius/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/freeradius/modules/files files { usersfile = "/etc/freeradius/users" acctusersfile = "/etc/freeradius/acct_users" preproxy_usersfile = "/etc/freeradius/preproxy_users" compat = "no" } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating module "acct_unique" from file /etc/freeradius/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/freeradius/modules/detail detail { detailfile = "/var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Linked to module rlm_radutmp Module: Instantiating module "radutmp" from file /etc/freeradius/modules/radutmp radutmp { filename = "/var/log/freeradius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Linked to module rlm_attr_filter Module: Instantiating module "attr_filter.accounting_response" from file /etc/freeradius/modules/attr_filter attr_filter attr_filter.accounting_response { attrsfile = "/etc/freeradius/attrs.accounting_response" key = "%{User-Name}" relaxed = no } 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 Module: Instantiating module "attr_filter.access_reject" from file /etc/freeradius/modules/attr_filter attr_filter attr_filter.access_reject { attrsfile = "/etc/freeradius/attrs.access_reject" key = "%{User-Name}" relaxed = no } } # modules } # server server inner-tunnel { # from file /etc/freeradius/sites-enabled/inner-tunnel modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} 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 server dhcp { # from file /etc/freeradius/sites-enabled/dhcp modules { Module: Checking dhcp DHCP-Discover {...} for more modules to load Module: Linked to module rlm_passwd Module: Instantiating module "mac2ip" from file /etc/freeradius/modules/mac2ip passwd mac2ip { filename = "/etc/freeradius/mac2ip" format = "*DHCP-Client-Hardware-Address:=DHCP-Your-IP-Address" delimiter = "," ignorenislike = yes ignoreempty = yes allowmultiplekeys = no hashsize = 100 } rlm_passwd: nfields: 2 keyfield 0(DHCP-Client-Hardware-Address) listable: no Module: Linked to module rlm_always Module: Instantiating module "ok" from file /etc/freeradius/modules/always always ok { rcode = "ok" simulcount = 0 mpp = no } Module: Checking dhcp DHCP-Request {...} for more modules to load Module: Checking dhcp (null) {...} for more modules to load /etc/freeradius/sites-enabled/dhcp[237]: No name specified for Post-Auth-Type block } # modules } # server radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 } listen { type = "dhcp" ipaddr = 255.255.255.255 port = 67 interface_ipaddr = 172.16.101.1 } listen { type = "dhcp" ipaddr = 172.16.101.1 port = 67 } ... adding new socket proxy address * port 49208 Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on dhcp interface dummy1 address 255.255.255.255 port 67 as server dhcp Listening on dhcp address 172.16.101.1 port 67 as server dhcp Listening on proxy address * port 1814 Ready to process requests. Received DHCP-Discover of id 3ecf5c31 from 0.0.0.0:68 to 255.255.255.255:67 DHCP-Opcode = Client-Message DHCP-Hardware-Type = Ethernet DHCP-Hardware-Address-Length = 6 DHCP-Hop-Count = 0 DHCP-Transaction-Id = 1053776945 DHCP-Number-of-Seconds = 0 DHCP-Flags = 0 DHCP-Client-IP-Address = 0.0.0.0 DHCP-Your-IP-Address = 0.0.0.0 DHCP-Server-IP-Address = 0.0.0.0 DHCP-Gateway-IP-Address = 0.0.0.0 DHCP-Client-Hardware-Address = 08:00:27:a2:13:b9 DHCP-Message-Type = DHCP-Discover DHCP-Parameter-Request-List = DHCP-Subnet-Mask DHCP-Parameter-Request-List = DHCP-Broadcast-Address DHCP-Parameter-Request-List = DHCP-Time-Offset DHCP-Parameter-Request-List = DHCP-Router-Address DHCP-Parameter-Request-List = DHCP-Domain-Name DHCP-Parameter-Request-List = DHCP-Domain-Name-Server DHCP-Parameter-Request-List = DHCP-Hostname DHCP-Parameter-Request-List = DHCP-NTP-Servers server dhcp { Trying sub-section dhcp DHCP-Discover {...} +- entering group DHCP-Discover {...} ++[reply] returns noop ++[reply] returns noop [mac2ip] Added DHCP-Your-IP-Address: '172.16.101.101' to reply_items ++[mac2ip] returns ok ++[ok] returns ok } # server dhcp DHCP-Subnet-Mask = 255.255.255.0 DHCP-Router-Address = 172.16.101.1 DHCP-Domain-Name-Server = 8.8.8.8 DHCP-IP-Address-Lease-Time = 60 DHCP-DHCP-Server-Identifier = 172.16.101.1 Sending DHCP-Offer of id 3ecf5c31 from 172.16.101.1:67 to 172.16.101.101:68 Finished request 0. Cleaning up request 0 ID 1053776945 with timestamp +12 Going to the next request Ready to process requests. Received DHCP-Discover of id 3ecf5c31 from 0.0.0.0:68 to 255.255.255.255:67 DHCP-Opcode = Client-Message DHCP-Hardware-Type = Ethernet DHCP-Hardware-Address-Length = 6 DHCP-Hop-Count = 0 DHCP-Transaction-Id = 1053776945 DHCP-Number-of-Seconds = 4 DHCP-Flags = 0 DHCP-Client-IP-Address = 0.0.0.0 DHCP-Your-IP-Address = 0.0.0.0 DHCP-Server-IP-Address = 0.0.0.0 DHCP-Gateway-IP-Address = 0.0.0.0 DHCP-Client-Hardware-Address = 08:00:27:a2:13:b9 DHCP-Message-Type = DHCP-Discover DHCP-Parameter-Request-List = DHCP-Subnet-Mask DHCP-Parameter-Request-List = DHCP-Broadcast-Address DHCP-Parameter-Request-List = DHCP-Time-Offset DHCP-Parameter-Request-List = DHCP-Router-Address DHCP-Parameter-Request-List = DHCP-Domain-Name DHCP-Parameter-Request-List = DHCP-Domain-Name-Server DHCP-Parameter-Request-List = DHCP-Hostname DHCP-Parameter-Request-List = DHCP-NTP-Servers server dhcp { Trying sub-section dhcp DHCP-Discover {...} +- entering group DHCP-Discover {...} ++[reply] returns noop ++[reply] returns noop [mac2ip] Added DHCP-Your-IP-Address: '172.16.101.101' to reply_items ++[mac2ip] returns ok ++[ok] returns ok } # server dhcp DHCP-Subnet-Mask = 255.255.255.0 DHCP-Router-Address = 172.16.101.1 DHCP-Domain-Name-Server = 8.8.8.8 DHCP-IP-Address-Lease-Time = 60 DHCP-DHCP-Server-Identifier = 172.16.101.1 Sending DHCP-Offer of id 3ecf5c31 from 172.16.101.1:67 to 172.16.101.101:68 Finished request 1. Cleaning up request 1 ID 1053776945 with timestamp +16 Going to the next request Ready to process requests. #=========================================================================== tcpdump output from the server #=========================================================================== 15:39:47.611809 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:00:27:a2:13:b9, length 300, xid 0x3ecf5c31, Flags [none] Client-Ethernet-Address 08:00:27:a2:13:b9 Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Parameter-Request Option 55, length 8: Subnet-Mask, BR, Time-Zone, Default-Gateway Domain-Name, Domain-Name-Server, Hostname, NTP 15:39:47.611830 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:00:27:a2:13:b9, length 300, xid 0x3ecf5c31, Flags [none] Client-Ethernet-Address 08:00:27:a2:13:b9 Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Parameter-Request Option 55, length 8: Subnet-Mask, BR, Time-Zone, Default-Gateway Domain-Name, Domain-Name-Server, Hostname, NTP 15:39:47.616432 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.101.101 tell 172.16.101.1, length 28 15:39:48.616525 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.101.101 tell 172.16.101.1, length 28 15:39:49.616483 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.101.101 tell 172.16.101.1, length 28 15:39:51.613941 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:00:27:a2:13:b9, length 300, xid 0x3ecf5c31, secs 4, Flags [none] Client-Ethernet-Address 08:00:27:a2:13:b9 Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Parameter-Request Option 55, length 8: Subnet-Mask, BR, Time-Zone, Default-Gateway Domain-Name, Domain-Name-Server, Hostname, NTP 15:39:51.613964 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:00:27:a2:13:b9, length 300, xid 0x3ecf5c31, secs 4, Flags [none] Client-Ethernet-Address 08:00:27:a2:13:b9 Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Parameter-Request Option 55, length 8: Subnet-Mask, BR, Time-Zone, Default-Gateway Domain-Name, Domain-Name-Server, Hostname, NTP 15:39:51.616438 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.101.101 tell 172.16.101.1, length 28 15:39:52.616460 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.101.101 tell 172.16.101.1, length 28 15:39:53.616516 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 172.16.101.101 tell 172.16.101.1, length 28 #=========================================================================== -- Fajar

2 8

OCSP failure with nonce - patch for option use_nonce
by Matthew Newton 12 Jan '12

12 Jan '12

Hi, Testing OCSP today, it took a while to realise that the server didn't support nonce, but freeradius always sends it. This meant all OCSP requests were rejected as 'unauthorised'. It turns out that the MS Certificate Services responder ships with nonce support disabled, but it can be enabled, which did fix our issue. However reading around the web it sounds like there are responders out there that can't cope with nonce. So here's a patch that adds a new option to the OCSP settings, 'use_nonce', which defaults to yes. Tested here (v2.1.x branch) and it means that the certificate validation will still work if the server can't understand nonce. Obviously there's an increased chance of a replay attack with it disabled, so I added a warning to the config that recommends not turning it off unless necessary. Patch for v2.1.x branch: https://github.com/mcnewton/freeradius-server/commit/1f52a80b62d00fa2200487… and against master (untested, I confess): https://github.com/mcnewton/freeradius-server/commit/f9578ba407934d0a27a7e1… It looks sane to me, and works, but probably needs eyeballing by someone with openssl knowledge to ensure I haven't done something stupid. Cheers, Matthew -- Matthew Newton, Ph.D. <mcn4(a)le.ac.uk> Systems Architect (UNIX and Networks), Network Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp(a)le.ac.uk>

1 0

3.0 (master) build error
by Fajar A. Nugraha 12 Jan '12

12 Jan '12

Hi, Not sure if this mail is better of freeradius-devel or -user. I'm posting it to -devel since 3.0 is not released yet. I'm trying to build master branch (last commit d1dfb80) on Ubuntu natty (gcc-4.5.2) with a simple ./configure && make, and the build failed with this error: CC listen.c listen.c: In function 'proxy_new_listener': listen.c:2403:21: error: 'buffer' undeclared (first use in this function) listen.c:2403:21: note: each undeclared identifier is reported only once for each function it appears in listen.c: In function 'listen_init': listen.c:2863:4: warning: passing argument 1 of 'cf_sectiontoitem' discards qualifiers from pointer target type /data/build/freeradius-server-3.0.0/src/freeradius-devel/conffile.h:101:12: note: expected 'struct CONF_SECTION *' but argument is of type 'const struct CONF_SECTION *' listen.c:2864:4: warning: passing argument 1 of 'cf_sectiontoitem' discards qualifiers from pointer target type /data/build/freeradius-server-3.0.0/src/freeradius-devel/conffile.h:101:12: note: expected 'struct CONF_SECTION *' but argument is of type 'const struct CONF_SECTION *' listen.c: At top level: listen.c:54:13: warning: 'print_packet' defined but not used make[4]: *** [listen.lo] Error 1 make[3]: *** [main] Error 2 make[2]: *** [all] Error 2 make[1]: *** [src] Error 2 make: *** [all] Error 2 Any known workaround for this? -- Fajar

4 18

Patch to use query_timeout in rlm_sql_mysql
by Brian De Wolf 12 Jan '12

12 Jan '12

Greetings, When I was setting up freeradius to use our existing multi-master MySQL setup, I noticed that freeradius would hang seemingly forever if one of the MySQL servers failed to respond (or wasn't responding during startup). The rlm_sql module has a query_timeout option but it wasn't being used in the mysql driver. The attached patch adds the appropriate lines to set mysql library options to use timeouts based on query_timeout for connecting, reads, and writes. The only confusing caveat is that the read and write timeouts apparently have retries built-in, so the timeout is effectively 3 times the query_timeout time. Also, the connect timeout would ideally be a different variable, but I didn't see an existing variable for such a purpose and felt it simplified the patch if I didn't add one. Other than this problem, freeradius has been great. Thanks! Brian

2 1

Patch to set group ownership of linelog file
by Matthew Newton 11 Jan '12

11 Jan '12

Hi, I couldn't find a way to set the group of the log file written by linelog, so I wrote code to do it. It adds a 'group' option to the linelog config. Obviously it can only change the file group if the user running freeradius is already in the new group. To use you'd probably also want to set the 'permissions' option to '0640' to allow the new group to read the logs. Patch below is for 2.1.12, and applies cleanly to v2.1.x and master HEAD. I'm working on the same for rlm_detail. Cheers, Matthew commit 3457c424255b0996bfd1549d1a76c6ecf6f240e5 Author: Matthew Newton <mcn4(a)leicester.ac.uk> Date: Tue Jan 10 12:45:42 2012 +0000 Add new 'group' option to rlm_linelog rlm_linelog saves its log files as the user/group of the running freeradius daemon. This update allows the group to be set on new log files (to a group that the daemon's user is a member of). diff --git a/raddb/modules/linelog b/raddb/modules/linelog index 2be4d81..d4e862e 100644 --- a/raddb/modules/linelog +++ b/raddb/modules/linelog @@ -26,6 +26,17 @@ linelog { permissions = 0600 # + # The Unix group of the log file. + # + # Use this to set the the system group of the log file after + # it is created. + # + # Note: the user that freeradius runs as must be in the specified + # group, otherwise it will not be possible to set the group. + # + # group = freerad + + # # The default format string. format = "This is a log message for %{User-Name}" diff --git a/src/modules/rlm_linelog/rlm_linelog.c b/src/modules/rlm_linelog/rlm_linelog.c index 24c809f..fa30e4b 100644 --- a/src/modules/rlm_linelog/rlm_linelog.c +++ b/src/modules/rlm_linelog/rlm_linelog.c @@ -31,6 +31,14 @@ RCSID("$Id$") #include <fcntl.h> #endif +#ifdef HAVE_UNISTD_H +#include <unistd.h> +#endif + +#ifdef HAVE_GRP_H +#include <grp.h> +#endif + #ifdef HAVE_SYSLOG_H #include <syslog.h> @@ -46,6 +54,7 @@ typedef struct rlm_linelog_t { CONF_SECTION *cs; char *filename; int permissions; + char *group; char *line; char *reference; } rlm_linelog_t; @@ -64,6 +73,8 @@ static const CONF_PARSER module_config[] = { offsetof(rlm_linelog_t,filename), NULL, NULL}, { "permissions", PW_TYPE_INTEGER, offsetof(rlm_linelog_t,permissions), NULL, "0600"}, + { "group", PW_TYPE_STRING_PTR, + offsetof(rlm_linelog_t,group), NULL, NULL}, { "format", PW_TYPE_STRING_PTR, offsetof(rlm_linelog_t,line), NULL, NULL}, { "reference", PW_TYPE_STRING_PTR, @@ -198,6 +209,9 @@ static int do_linelog(void *instance, REQUEST *request) char line[1024]; rlm_linelog_t *inst = (rlm_linelog_t*) instance; const char *value = inst->line; + gid_t gid; + struct group *grp; + char *endptr; if (inst->reference) { CONF_ITEM *ci; @@ -261,8 +275,25 @@ static int do_linelog(void *instance, REQUEST *request) buffer, strerror(errno)); return RLM_MODULE_FAIL; } + + if (inst->group != NULL) { + gid = strtol(inst->group, &endptr, 10); + if (*endptr != '\0') { + grp = getgrnam(inst->group); + if (grp == NULL) { + RDEBUG2("Unable to find system group \"%s\"", inst->group); + goto skip_group; + } + gid = grp->gr_gid; + } + + if (chown(buffer, -1, gid) == -1) { + RDEBUG2("Unable to change system group of \"%s\"", buffer); + } + } } + skip_group: /* * FIXME: Check length. */ -- Matthew Newton, Ph.D. <mcn4(a)le.ac.uk> Systems Architect (UNIX and Networks), Network Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp(a)le.ac.uk>

2 3

new configure flag for freeradius-client
by Jonh Wendell 04 Jan '12

04 Jan '12

hello, folks. yesterday I experienced an issue while compiling freeradius-client. thankfully, it was a known one, a bit old one btw: http://lists.cistron.nl/pipermail/freeradius-devel/2008-September/012581.ht… so, I cloned the alan's github repo and created a new configure flag, which allows the user to choose what implementation of gethostby[addr,name] to use. it worked for me, and solved my problem. I'm not sure if it's the best approach to fix the issue, though. as I'm new in this software, maybe you guys have a better solution. I want to hear from you. the code is here: https://github.com/alandekok/freeradius-client/pull/3 btw: forking and doing pull requests on github is the right way of proposing patches? thanks for your attention, -- Jonh Wendell www.vexcorp.com +55 11 4932-5932

1 0