June 2012 - Freeradius-Users - lists.freeradius.org

unable to authenticate with Crypt-Password
by abrooks 05 Jun '12

05 Jun '12

Hello I cannot get my freeradius server to authenticate using a users file which is used successfully on a couple of older servers. I'm trying to replace one of the old machines with a VM running on a ubuntu host using VirtualBox. I am running a ubuntu 10.04 64 bit virtual server with FreeRADIUS Version 2.1.8, for host x86_64-pc-linux-gnu, built on Jan 5 2010 at 02:56:18 installed using apt-get install. I use a users list to authenticate. My users file is commented out except for 3 lines: bob Cleartext-Password := "hello" $INCLUDE users.1003512 $INCLUDE users.1033872 -bob was added for testing users.1003512 and user1033827 are identically formatted. Here is a sample from users.1033872: abrooks1(a)iroam.uk Crypt-Password == "$1$BbFRsHhY$.Qcjjczle/i94ILxuajvT/" Auth-Type = Crypt-Local, User-Service-Type = Framed-User, Framed-Protocol = PPP, Framed-Address = 255.255.255.254, Framed-Netmask = 255.255.255.255, Framed-Routing = None, Framed-Compression = Van-Jacobsen-TCP-IP, Framed-MTU = 1500 abrooks2(a)iroam.uk Crypt-Password == "$1$mqZm0XU5$4ZGIcC.9AdoDvqdGQDpNo0" User-Service-Type = Framed-User, Framed-Protocol = PPP, Framed-Address = 255.255.255.254, Framed-Netmask = 255.255.255.255, Framed-Routing = None, Framed-Compression = Van-Jacobsen-TCP-IP, Framed-MTU = 1500 I use these same users files on two older, working Freeradius servers. I always get rejected using radtest: radtest abrooks2(a)iroam.uk 1234512345 localhost 1812 mysecret /etc/freeradius# freeradius -X start FreeRADIUS Version 2.1.8, for host x86_64-pc-linux-gnu, built on Jan 5 2010 at 02:56:18 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/otp including configuration file /etc/freeradius/modules/attr_filter including configuration file /etc/freeradius/modules/checkval including configuration file /etc/freeradius/modules/expiration including configuration file /etc/freeradius/modules/acct_unique including configuration file /etc/freeradius/modules/counter including configuration file /etc/freeradius/modules/digest including configuration file /etc/freeradius/modules/mac2vlan including configuration file /etc/freeradius/modules/preprocess including configuration file /etc/freeradius/modules/detail including configuration file /etc/freeradius/modules/sradutmp including configuration file /etc/freeradius/modules/always including configuration file /etc/freeradius/modules/ldap including configuration file /etc/freeradius/modules/smsotp including configuration file /etc/freeradius/modules/krb5 including configuration file /etc/freeradius/modules/mschap including configuration file /etc/freeradius/modules/inner-eap including configuration file /etc/freeradius/modules/ippool including configuration file /etc/freeradius/modules/unix including configuration file /etc/freeradius/modules/mac2ip including configuration file /etc/freeradius/modules/pam including configuration file /etc/freeradius/modules/perl including configuration file /etc/freeradius/modules/files including configuration file /etc/freeradius/modules/chap including configuration file /etc/freeradius/modules/detail.log including configuration file /etc/freeradius/modules/expr including configuration file /etc/freeradius/modules/detail.example.com including configuration file /etc/freeradius/modules/etc_group including configuration file /etc/freeradius/modules/ntlm_auth including configuration file /etc/freeradius/modules/radutmp including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login including configuration file /etc/freeradius/modules/cui including configuration file /etc/freeradius/modules/policy including configuration file /etc/freeradius/modules/echo including configuration file /etc/freeradius/modules/sql_log including configuration file /etc/freeradius/modules/realm including configuration file /etc/freeradius/modules/passwd including configuration file /etc/freeradius/modules/attr_rewrite including configuration file /etc/freeradius/modules/pap including configuration file /etc/freeradius/modules/smbpasswd including configuration file /etc/freeradius/modules/exec including configuration file /etc/freeradius/modules/logintime including configuration file /etc/freeradius/modules/linelog including configuration file /etc/freeradius/modules/wimax 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/inner-tunnel including configuration file /etc/freeradius/sites-enabled/default main { user = "freerad" group = "freerad" allow_core_dumps = no } including dictionary file /etc/freeradius/dictionary main { prefix = "/usr" localstatedir = "/var" logdir = "/var/log/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 = yes dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "mysecret" 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 { authhost = LOCAL accthost = LOCAL } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "mysecret" nastype = "other" } client 192.168.0.0/16 { require_message_authenticator = no secret = "mysecret" shortname = "private-network-2" } client 192.168.1.112 { require_message_authenticator = no secret = "mysecret" shortname = "Roamer" } client 192.139.22.14 { require_message_authenticator = no secret = "mysecret" shortname = "Roamer-Exterior" } 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 = yes } Module: Linked to module rlm_chap Module: Instantiating chap Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/var/log/freeradius/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/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 = "/etc/freeradius/certs/random" fragment_size = 1024 include_length = yes check_crl = no cipher_list = "DEFAULT" make_cert_command = "/etc/freeradius/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/freeradius/users" acctusersfile = "/etc/freeradius/acct_users" preproxy_usersfile = "/etc/freeradius/preproxy_users" compat = "no" } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/var/log/freeradius/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/freeradius/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server { modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating preprocess preprocess { huntgroups = "/etc/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: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating detail detail { detailfile = "/var/log/freeradius/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/freeradius/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 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1 port 45526, id=57, length=69 User-Name = "abrooks2(a)iroam.uk" User-Password = "1234512345" NAS-IP-Address = 127.0.1.1 NAS-Port = 1812 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] Looking up realm "iroam.uk" for User-Name = "abrooks2(a)iroam.uk" [suffix] No such realm "iroam.uk" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[unix] returns notfound [files] users: Matched entry abrooks2(a)iroam.uk at line 11 ++[files] 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 No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> abrooks2(a)iroam.uk 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 57 to 127.0.0.1 port 45526 Waking up in 4.9 seconds. Cleaning up request 0 ID 57 with timestamp +4 Ready to process requests. Cleartext Password test: I enter this radtest: radtest bob hello localhost 1812 mysecret Here is my freeradius -X output: rad_recv: Access-Request packet from host 127.0.0.1 port 34596, id=1, length=55 User-Name = "bob" User-Password = "hello" NAS-IP-Address = 127.0.1.1 NAS-Port = 1812 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "bob", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[unix] returns notfound [files] users: Matched entry bob at line 1 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns updated Found Auth-Type = PAP +- entering group PAP {...} [pap] login attempt with password "hello" [pap] Using clear text password "hello" [pap] User authenticated successfully ++[pap] returns ok +- entering group post-auth {...} ++[exec] returns noop Sending Access-Accept of id 1 to 127.0.0.1 port 34596 Finished request 2. Going to the next request Waking up in 4.9 seconds. -- View this message in context: http://freeradius.1045715.n5.nabble.com/unable-to-authenticate-with-Crypt-P… Sent from the FreeRadius - User mailing list archive at Nabble.com.

3 4

accounting in syslog
by Luo, Frank Y.F. Mr. 05 Jun '12

05 Jun '12

Is there a way to send accounting log to syslog instead of detail file in radacct? Also instead of sending it to sql db, i tried to use sql-file but it results in a lot of sql command (we really don't want to run the sql command later). INSERT INTO radacct (AcctSessionId, UserName, NASIPAddress, FramedIPAddress, AcctStartTime, AcctStopTime, AcctSessionTime, AcctTerminateCause) VALUES ('4fc645a8/00:25:00:3e:e6:c2/188601', 'luoy', '172.18.47.242', '172.25.128.186', '2012-05-30 12:07:04', '0', '0', ''); INSERT INTO radacct (AcctSessionId, UserName, NASIPAddress, FramedIPAddress, AcctStartTime, AcctStopTime, AcctSessionTime, AcctTerminateCause) VALUES ('4fc645d8/10:40:f3:1c:a3:b4/188604', '1040f31ca3b4', '172.18.47.242', '172.24.146.51', '2012-05-30 12:07:52', '0', '0', ' '); Also noticing the UserName part, a lot of times that a binary username is logged, like here "1040f31ca3b4", instead of the real name. How to fix this? THanks for the help Frank

4 5

Freeradius dont't send VSA attribute
by CHEBIHI Abdelhakim (EXT ALTEN - IGTL) 05 Jun '12

05 Jun '12

Hi, and how i put this VSA in the reply details please? Thanks On Tue, Jun 5, 2012 at 1:49 PM, CHEBIHI Abdelhakim (EXT ALTEN - IGTL) <ext.alten.abdelhakim.chebihi at sncf.fr <http://lists.freeradius.org/mailman/listinfo/freeradius-users> > wrote: > tom Cleartext-Password := "tom123" > Service-Type = Login-User, > Juniper-Local-User-Name := "readonly-users", > > when i launch freeradius -X, and i connect with tom from the router i see > that the user logs Ok But freeradius don't send the vsa attribute????: So put the VSA attributes in the reply details for user tom? Radius is returning precisely what you configured it to return. ------- Ce message et toutes les pièces jointes sont établis à l'intention exclusive de ses destinataires et sont confidentiels. L'intégrité de ce message n'étant pas assurée sur Internet, la SNCF ne peut être tenue responsable des altérations qui pourraient se produire sur son contenu. Toute publication, utilisation, reproduction, ou diffusion, même partielle, non autorisée préalablement par la SNCF, est strictement interdite. Si vous n'êtes pas le destinataire de ce message, merci d'en avertir immédiatement l'expéditeur et de le détruire. ------- This message and any attachments are intended solely for the addressees and are confidential. SNCF may not be held responsible for their contents whose accuracy and completeness cannot be guaranteed over the Internet. Unauthorized use, disclosure, distribution, copying, or any part thereof is strictly prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete it.

1 0

Freeradius dont't send VSA attribute
by CHEBIHI Abdelhakim (EXT ALTEN - IGTL) 05 Jun '12

05 Jun '12

Hi all, i'm configuring a user with class Attribute like this on freeradius: tom Cleartext-Password := "tom123" Service-Type = Login-User, Juniper-Local-User-Name := "readonly-users", when i launch freeradius -X, and i connect with tom from the router i see that the user logs Ok But freeradius don't send the vsa attribute????: I see this on the console: Sending Access-Accept of id 65 to 172.16.1.11 port 62458 Finished request 5. I see on the net and i normally see this: Sending Access-Accept of id 65 to 172.16.1.11 port 62458 Juniper-Local-User-Name = "readonly-users" Finished request 5. Do I have to change something on the configuration file to enable sending VSA Attribute? Thanks. ------- Ce message et toutes les pièces jointes sont établis à l'intention exclusive de ses destinataires et sont confidentiels. L'intégrité de ce message n'étant pas assurée sur Internet, la SNCF ne peut être tenue responsable des altérations qui pourraient se produire sur son contenu. Toute publication, utilisation, reproduction, ou diffusion, même partielle, non autorisée préalablement par la SNCF, est strictement interdite. Si vous n'êtes pas le destinataire de ce message, merci d'en avertir immédiatement l'expéditeur et de le détruire. ------- This message and any attachments are intended solely for the addressees and are confidential. SNCF may not be held responsible for their contents whose accuracy and completeness cannot be guaranteed over the Internet. Unauthorized use, disclosure, distribution, copying, or any part thereof is strictly prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete it.

2 1

How to configure Solaris 10 Radius Authentication client.
by Alek Barsky 04 Jun '12

04 Jun '12

Hi Guys, I need to configure bunch of Solaris servers to use RADIUS PAM for Authentication/Authorization. I followed instructions in http://freeradius.org/pam_radius_auth/ and was able to configure Authentication portion of this task. There is one problem - the only way I can receive login shell on this box - if user already exists. I suspect I need to pass some variables from RADIUS server to my Solaris RADIUS client. Does anybody know what are they? Thanks, Alek. This e-mail (and attachment(s)) is confidential, proprietary, may be subject to copyright and legal privilege and no related rights are waived. If you are not the intended recipient or its agent, any review, dissemination, distribution or copying of this e-mail or any of its content is strictly prohibited and may be unlawful. All messages may be monitored as permitted by applicable law and regulations and our policies to protect our business. E-mails are not secure and you are deemed to have accepted any risk if you communicate with us by e-mail. If received in error, please notify us immediately and delete the e-mail (and any attachments) from any computer or any storage medium without printing a copy. Ce courriel (ainsi que ses pièces jointes) est confidentiel, exclusif, et peut faire l’objet de droit d’auteur et de privilège juridique; aucun droit connexe n’est exclu. Si vous n’êtes pas le destinataire visé ou son représentant, toute étude, diffusion, transmission ou copie de ce courriel en tout ou en partie, est strictement interdite et peut être illégale. Tous les messages peuvent être surveillés, selon les lois et règlements applicables et les politiques de protection de notre entreprise. Les courriels ne sont pas sécurisés et vous êtes réputés avoir accepté tous les risques qui y sont liés si vous choisissez de communiquer avec nous par ce moyen. Si vous avez reçu ce message par erreur, veuillez nous en aviser immédiatement et supprimer ce courriel (ainsi que toutes ses pièces jointes) de tout ordinateur ou support de données sans en imprimer une copie.

3 2

Freeraduis as accounting proxy
by peterpz 04 Jun '12

04 Jun '12

Hello, I'm trying to set up my freeradius to be an accounting proxy. No it only receives acct packets and saves data in log files. The configuration is below: radiusd.conf: accounting { detail fail } detail { detailfile = ${radacctdir}/%{Client-IP-Address}/detail-%Y%m%d%H.log } client.conf: client 126.18.130.8 { secret = faultcenter shortname = fault-center } I added the following to the proxy.conf, but freeradius don't sends any accounting packets: realm LOCAL { type = radius authhost = 126.20.50.230:1812 accthost = 126.20.50.230:1813 secret = fault } realm NULL { type = radius authhost = 126.20.50.230:1812 accthost = 126.20.50.230:1813 secret = fault } realm DEFAULT { type = radius authhost = 126.20.50.230:1812 accthost = 126.20.50.230:1813 secret = fault } Can somebody help? -- View this message in context: http://freeradius.1045715.n5.nabble.com/Freeraduis-as-accounting-proxy-tp57… Sent from the FreeRadius - User mailing list archive at Nabble.com.

2 3

Proxy-State in a CoA proxied request
by fab junkmail 03 Jun '12

03 Jun '12

Hi All. I have tried filtering out Proxy-State attribute for proxied CoA in pre.proxy section but it does not seem to work for me. Debug mentions the following which makes me think it is not using the DEFAULT section of attrs.pre-proxy: [attr_filter.pre-proxy] expand: %{Realm} -> ++[attr_filter.pre-proxy] returns noop (more debug in context below) Have you got this filtering to work Frédéric? If so, can you show me relevant parts of your config that shows how to make it work? Does anyone have any advice on how I can fix my config to be able to filter out (or not add) Proxy-State attribute for proxied CoA? I have included relevant parts of my config and debug below. Regards, Anthony !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! FreeRADIUS Version 2.1.12 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! contents of sites-enabled/coa: listen { type = coa ipaddr = * port = 1700 server = coa } server coa { recv-coa { if ("%{NAS-IP-Address}" == "10.0.72.14") { update control { Home-Server-Pool := bng01-coa-pool } } if ("%{NAS-IP-Address}" == "10.0.72.15") { update control { Home-Server-Pool := bng02-coa-pool } } ok } send-coa { ok } pre-proxy { attr_filter.pre-proxy pre_proxy_log } } contents of attrs.pre-proxy: DEFAULT User-Name =* ANY, Acct-Session-Id =* ANY, NAS-IP-Address =* ANY, Cisco-AVPair =* ANY partial contents of modules/attr_filter: attr_filter attr_filter.pre-proxy { attrsfile = ${confdir}/attrs.pre-proxy relaxed = no } !!!!!!!!!!!!!!!!! example radsniff: # radsniff -p 1700 -x Device: [eth0] PCAP filter: [udp port 1700 or 1701] RADIUS secret: [testing123] CoA-Request Id 239 10.0.91.203:49184 -> 10.0.91.204:1700 (1 packets) +0.000 User-Name = "test(a)testdomain.com" Acct-Session-Id = "00000016" Cisco-AVPair = "ip:sub-qos-policy-out=UNSHAPE" NAS-IP-Address = 10.0.72.14 CoA-Request Id 243 10.0.91.204:1814 -> 10.0.72.14:1700 (2 packets) +0.000 User-Name = "test(a)testdomain.com" Acct-Session-Id = "00000016" Cisco-AVPair = "ip:sub-qos-policy-out=UNSHAPE" NAS-IP-Address = 10.0.72.14 Proxy-State = 0x323339 CoA-NAK Id 243 10.0.72.14:1700 -> 10.0.91.204:1814 (3 packets) +0.001 Reply-Message = "Unsupported Attribute" Error-Cause = Unsupported-Attribute CoA-NAK Id 239 10.0.91.204:1700 -> 10.0.91.203:49184 (4 packets) +0.001 Reply-Message = "Unsupported Attribute" Error-Cause = Unsupported-Attribute !!!!!!!!!!!!!! example debug: Ready to process requests. rad_recv: CoA-Request packet from host 10.0.91.203 port 50769, id=33, length=101 User-Name = "test(a)testdomain.com" Acct-Session-Id = "00000016" Cisco-AVPair = "ip:sub-qos-policy-out=UNSHAPE" NAS-IP-Address = 10.0.72.14 server coa { # Executing section recv-coa from file /etc/freeradius/sites-enabled/coa +- entering group recv-coa {...} ++? if ("%{NAS-IP-Address}" == "10.0.72.14") expand: %{NAS-IP-Address} -> 10.0.72.14 ? Evaluating ("%{NAS-IP-Address}" == "10.0.72.14") -> TRUE ++? if ("%{NAS-IP-Address}" == "10.0.72.14") -> TRUE ++- entering if ("%{NAS-IP-Address}" == "10.0.72.14") {...} +++[control] returns noop ++- if ("%{NAS-IP-Address}" == "10.0.72.14") returns noop ++? if ("%{NAS-IP-Address}" == "10.0.72.15") expand: %{NAS-IP-Address} -> 10.0.72.14 ? Evaluating ("%{NAS-IP-Address}" == "10.0.72.15") -> FALSE ++? if ("%{NAS-IP-Address}" == "10.0.72.15") -> FALSE ++[ok] returns ok } # server coa # Executing section pre-proxy from file /etc/freeradius/sites-enabled/coa +- entering group pre-proxy {...} [attr_filter.pre-proxy] expand: %{Realm} -> ++[attr_filter.pre-proxy] returns noop [pre_proxy_log] expand: /var/log/freeradius/radacct/%{Client-IP-Address}/pre-proxy-detail-%Y%m%d -> /var/log/freeradius/radacct/10.0.91.203/pre-proxy-detail-20120601 [pre_proxy_log] /var/log/freeradius/radacct/%{Client-IP-Address}/pre-proxy-detail-%Y%m%d expands to /var/log/freeradius/radacct/10.0.91.203/pre-proxy-detail-20120601 [pre_proxy_log] expand: %t -> Fri Jun 1 07:58:56 2012 ++[pre_proxy_log] returns ok Sending CoA-Request of id 162 to 10.0.72.14 port 1700 User-Name = "test(a)testdomain.com" Acct-Session-Id = "00000016" Cisco-AVPair = "ip:sub-qos-policy-out=UNSHAPE" NAS-IP-Address = 10.0.72.14 Proxy-State = 0x3333 Proxying request 0 to home server 10.0.72.14 port 1700 Sending CoA-Request of id 162 to 10.0.72.14 port 1700 User-Name = "test(a)testdomain.com" Acct-Session-Id = "00000016" Cisco-AVPair = "ip:sub-qos-policy-out=UNSHAPE" NAS-IP-Address = 10.0.72.14 Proxy-State = 0x3333 Going to the next request Waking up in 0.9 seconds. rad_recv: CoA-NAK packet from host 10.0.72.14 port 1700, id=162, length=49 Reply-Message = "Unsupported Attribute" Error-Cause = Unsupported-Attribute WARNING: Empty post-proxy section. Using default return values. server coa { # Executing section send-coa from file /etc/freeradius/sites-enabled/coa +- entering group send-coa {...} ++[ok] returns ok } # server coa Sending CoA-NAK of id 33 to 10.0.91.203 port 50769 Reply-Message = "Unsupported Attribute" Error-Cause = Unsupported-Attribute Finished request 0.

3 4

Linux distro for Freeradius
by Turamarth 02 Jun '12

02 Jun '12

To install freeradius una VM what linux distro recommend? im looking for a one that takes low resources from machine, for now the only use for it will be freeradius.

4 3

Checkrad and Cisco WLC 4400 NAS
by Patrick Machauer 02 Jun '12

02 Jun '12

Hi, i've got a problem with simultaneous-use and a Cisco WLC4400. If i choose nastype=other in clients.conf the radaact table gets queried and if there is a running session for that user ( acctstoptime IS NULL) the user gets rejected ( defined for the users group in radgroupcheck simultaneous-use := 1 ). So far so good, but if i choose nastype=cisco, the user can log in as often as wanted. Checkrad gets executed and logs the following: /var/log/radius/checkrad.log ----------snip----------------------------------------------- Fri Jun 1 15:18:27 2012 checkrad cisco 141.72.65.21 1 machauer(a)staff.dhbw-mannheim.de 4fc8c577/a0:0b:ba:dd:25:8a/44 snmpget: /usr/bin/snmpget -r 1 -t 5 -v2c -c 'xxxxxxxxxx' 141.72.65.21 .iso.org.dod.internet.private.enterprises.9.2.9.2.1.18.1 user at port S1: No snpwalk: /usr/bin/snmpwalk -r 1 -t 5 -v2c -c 'xxxxxxxxxx' 141.72.65.21 .iso.org.dod.internet.private.enterprises.9.10.19.1.3.1.1.3 Returning 0 (login ok) ------------snap------------------------------------------------ If i execute the snmpget command by hand, i get the following: SNMPv2-SMI::enterprises.9.2.9.2.1.18.1 = No Such Object available on this agent at this OID The MIB on this device seems to be different than on other cisco devices :-( Has anyone an updated checkrad version which can get active usersessions from Cisco WLC or a hint how checkrad needs to be edited to do so ? Using nastype=other is no option, because the NAS only sends sessiontimeouts every 10 Minutes and i always have a time lag between radacct sessions and NAS sessions. Help would be really great ! Yours Patrick Machauer Rechenzentrum Duale Hochschule Baden-Württemberg Mannheim Baden-Wuerttemberg Cooperative State University Mannheim Rechenzentrum Coblitzallee 1-9 68163 Mannheim Tel.: +49 (0)621 4105 - 1278 Fax: +49 (0)621 4105 - 1278 E-Mail: machauer(a)dhbw-mannheim.de <mailto:machauer@dhbw-mannheim.de> Web: http://www.rz.dhbw-mannheim.de <http://www.rz.dhbw-mannheim.de>

1 0

Problem with FreeRadius and D-Link switch
by Jarosław Kłopotek 02 Jun '12

02 Jun '12

Hi all! I've got a problem with freeradius configuration: I've to build a login to D-Link 3526 using FreeRadius Server I've run freeradius -X my output is: #v+ ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop ++[digest] returns noop [suffix] No '@' in User-Name = "yarii", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop [files] users: Matched entry DEFAULT at line 172 ++[files] 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/freeradius/sites-enabled/default +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> yarii 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 #v- My settings from radius is: yarii Cleartext-Password := "somepass" Crypt-Password := "something", Auth-Type:= Local, Mikrotik-Group = full, Service-Type = Login-User, cisco-avpair = "shell:priv-lvl=15", User-Level = "5" Anybody can help me? Where to find the problem? Best wishes -- Jarosław 'YArii' Kłopotek mob +48 607 893 111 GG:1336231 INTERDUO s.c. ul. Lubelska 36B/40 21-100 Lubartów tel 81 477 54 54

2 3