April 2009 - Freeradius-Users - lists.freeradius.org

how can I create a user programatically?
by Matthew Carriere 08 Apr '09

08 Apr '09

I have a web application that I would like to use to provision users with. Has anyone done this? What tables would need to accessed in the schema to do this? I am hoping this isn't too difficult.... Matthew.

2 1

Is my switch really communicating .1x with Freeradius?
by john 08 Apr '09

08 Apr '09

Hello all, I am struggling to get a windowsXP client to authenticate to freeradius. I've set up winbind/samba and radtest works from the command line on the freeradius server. However the client doesn't seem to be able to contact the server when attached to a switch which supports .1x. During testing with wireshark I noticed that my switch (a 3com 3226) is sending EAP failure messages in response to the XP clients eap request. I don't see anything in the debug output of the freeradius server when I run it with /usr/sbin/freeradius -X It seems to me that my 3Com switch isn't really communicating with the freeradius server. Can someone help me figure out how to make sure that my NAS is talking to the server? Thanks! John

3 3

Re: Certificate Authentication WindowsXP SP3
by Marten Groeneveld 08 Apr '09

08 Apr '09

Please be so kind to ignore my previous mail. I have done lots of mistakes I have now corrected myself by reading previous posts in this mailinglist. Thank you all for your help! Marten

1 0

Certificate Authentication WindowsXP SP3
by Marten Groeneveld 08 Apr '09

08 Apr '09

Hello I want to set up a radius server with freeradius and am running into some problems. I have setup the certificates like described in certs/README (configuring the .cnf files and then doing 'make ca.der' 'make server.pem" and 'make client.pem') and have imported ca.der, server.crt and client.crt on a notebook running Windows XP SP3. Here is the output of freeradius -X freeradius -X FreeRADIUS Version 2.1.5, for host i486-pc-linux-gnu, built on Apr 6 2009 at 16:27:46 Copyright (C) 1999-2008 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/detail.example.com including configuration file /etc/freeradius/modules/digest including configuration file /etc/freeradius/modules/chap including configuration file /etc/freeradius/modules/exec including configuration file /etc/freeradius/modules/expiration including configuration file /etc/freeradius/modules/realm including configuration file /etc/freeradius/modules/smbpasswd including configuration file /etc/freeradius/modules/checkval including configuration file /etc/freeradius/modules/mac2ip including configuration file /etc/freeradius/modules/mac2vlan including configuration file /etc/freeradius/modules/policy including configuration file /etc/freeradius/modules/attr_filter including configuration file /etc/freeradius/modules/inner-eap including configuration file /etc/freeradius/modules/detail.log including configuration file /etc/freeradius/modules/echo including configuration file /etc/freeradius/modules/sqlcounter_expire_on_login including configuration file /etc/freeradius/modules/linelog including configuration file /etc/freeradius/modules/acct_unique including configuration file /etc/freeradius/modules/expr including configuration file /etc/freeradius/modules/logintime including configuration file /etc/freeradius/modules/ippool including configuration file /etc/freeradius/modules/unix including configuration file /etc/freeradius/modules/counter including configuration file /etc/freeradius/modules/radutmp including configuration file /etc/freeradius/modules/etc_group including configuration file /etc/freeradius/modules/mschap including configuration file /etc/freeradius/modules/ldap including configuration file /etc/freeradius/modules/wimax including configuration file /etc/freeradius/modules/pap including configuration file /etc/freeradius/modules/attr_rewrite including configuration file /etc/freeradius/modules/preprocess including configuration file /etc/freeradius/modules/smsotp including configuration file /etc/freeradius/modules/files including configuration file /etc/freeradius/modules/krb5 including configuration file /etc/freeradius/modules/otp including configuration file /etc/freeradius/modules/detail including configuration file /etc/freeradius/modules/always including configuration file /etc/freeradius/modules/passwd including configuration file /etc/freeradius/modules/sradutmp including configuration file /etc/freeradius/modules/perl including configuration file /etc/freeradius/modules/pam including configuration file /etc/freeradius/modules/sql_log 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/control-socket including configuration file /etc/freeradius/sites-enabled/inner-tunnel including configuration file /etc/freeradius/sites-enabled/default group = freerad user = freerad 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 allow_core_dumps = no 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 = no zombie_period = 40 status_check = "status-server" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 irt = 2 mrt = 16 mrc = 5 mrd = 30 } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } client 192.168.224.100/24 { require_message_authenticator = no secret = "mypasswordishere" shortname = "lancomtest" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating expr Module: Linked to module rlm_expiration Module: Instantiating expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating chap Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/var/log/freeradius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "tls" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no max_sessions = 2048 } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } Module: Linked to sub-module rlm_eap_tls Module: Instantiating eap-tls tls { rsa_key_exchange = no dh_key_exchange = yes rsa_key_length = 512 dh_key_length = 512 verify_depth = 0 pem_file_type = yes private_key_file = "/etc/freeradius/certs/server.key" certificate_file = "/etc/freeradius/certs/server.pem" CA_file = "/etc/freeradius/certs/ca.pem" private_key_password = "key to server cert is here" 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" } 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 { 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 } 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/freeradius/freeradius.sock" } } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /var/run/freeradius/freeradius.sock Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 192.168.224.100 port 3072, id=94, length=180 User-Name = "NTB-KTM-01\\Administrator" Service-Type = Framed-User NAS-IP-Address = 192.168.224.100 NAS-Port = 1 NAS-Port-Id = "1" Called-Station-Id = "00-0B-6B-30-31-56:LANCOM" Calling-Station-Id = "00-21-6B-2A-72-AA" NAS-Identifier = "LANCOML-54g" NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0201001d014e54422d4b544d2d30315c41646d696e6973747261746f72 Message-Authenticator = 0xad489223ce9bdd57116a69b80d04a0cc +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "NTB-KTM-01\Administrator", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 1 length 29 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[unix] returns notfound ++[files] returns noop ++[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 Found Auth-Type = EAP +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Requiring client certificate [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 94 to 192.168.224.100 port 3072 EAP-Message = 0x010200060d20 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x09b1011d09b30c50d61b870248979c7b Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.224.100 port 3072, id=100, length=175 User-Name = "NTB-KTM-01\\Administrator" Service-Type = Framed-User NAS-IP-Address = 192.168.224.100 NAS-Port = 1 NAS-Port-Id = "1" State = 0x09b1011d09b30c50d61b870248979c7b Called-Station-Id = "00-0B-6B-30-31-56:LANCOM" Calling-Station-Id = "00-21-6B-2A-72-AA" NAS-Identifier = "LANCOML-54g" NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020200060319 Message-Authenticator = 0xbd1c68bdf127aee5ad8bbf8674a71914 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "NTB-KTM-01\Administrator", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 2 length 6 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[unix] returns notfound ++[files] returns noop ++[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 Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP NAK [eap] EAP-NAK asked for EAP-Type/peap [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 100 to 192.168.224.100 port 3072 EAP-Message = 0x010300061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x09b1011d08b21850d61b870248979c7b Finished request 1. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.224.100 port 3072, id=52, length=249 User-Name = "NTB-KTM-01\\Administrator" Service-Type = Framed-User NAS-IP-Address = 192.168.224.100 NAS-Port = 1 NAS-Port-Id = "1" State = 0x09b1011d08b21850d61b870248979c7b Called-Station-Id = "00-0B-6B-30-31-56:LANCOM" Calling-Station-Id = "00-21-6B-2A-72-AA" NAS-Identifier = "LANCOML-54g" NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0203005019800000004616030100410100003d030149dc65059309f2c91ab12b1481406b0c3f660db2dea70dfe1ad2601328ddbf5800001600040005000a000900640062000300060013001200630100 Message-Authenticator = 0x77384e41c923602ef44928acde1df80e +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "NTB-KTM-01\Administrator", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 3 length 80 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS TLS Length 70 [peap] Length Included [peap] eaptls_verify returned 11 [peap] (other): before/accept initialization [peap] TLS_accept: before/accept initialization [peap] <<< TLS 1.0 Handshake [length 0041], ClientHello [peap] TLS_accept: SSLv3 read client hello A [peap] >>> TLS 1.0 Handshake [length 002a], ServerHello [peap] TLS_accept: SSLv3 write server hello A [peap] >>> TLS 1.0 Handshake [length 0813], Certificate [peap] TLS_accept: SSLv3 write certificate A [peap] >>> TLS 1.0 Handshake [length 0004], ServerHelloDone [peap] TLS_accept: SSLv3 write server done A [peap] TLS_accept: SSLv3 flush data [peap] TLS_accept: Need to read more data: SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 52 to 192.168.224.100 port 3072 EAP-Message = 0x0104040019c000000850160301002a02000026030149dc5d3b965d5723bc2b8d422288943ffa14bb977304d05a2fbf288bdead9cf10000040016030108130b00080f00080c00038e3082038a30820272a003020102020102300d06092a864886f70d0101040500308182310b3009060355040613024445311630140603550408130d4e69656465727361636873656e310f300d060355040713064c4b4c656572310f300d060355040a13064c4b4c6565723126302406092a864886f70d010901161774686f6d61732e6c656e676572406c6b6c6565722e64653111300f060355040313084c4b4c6565724341301e170d3039303430373038323333365a EAP-Message = 0x170d3130303430373038323333365a3075310b3009060355040613024445311630140603550408130d4e69656465727361636873656e310f300d060355040a13064c4b4c656572311530130603550403130c4c4b4c6565725261645372763126302406092a864886f70d010901161774686f6d61732e6c656e676572406c6b6c6565722e646530820122300d06092a864886f70d01010105000382010f003082010a02820101009e8db00c810126209f387a4d72ea6367bd35d8e00c0d853e3fcb2eef0687d04b4baf781b8dad2b05c3a55722385a60745c44a3775a6200378a5c4d49923d9dc3278f8f53de427d0a696720420aacbecb73cf771526b6 EAP-Message = 0x4cea2c36b7231b84fce023a1bd49f24888acb9db7709457c8e52e8ad04f509d5711acfc03ca61f9ee05f83229624688f3d4f47938ac00006576f675c2cbb11561f0d654ab3c42eb35b1ccee9eb04f39c2d194270895f38543ea9210c15f03ed31094ac4ea2f9493b0cf4b1e365002e6ac16dec2dd90a89ddf59f236dd5f0e7adca3358c6ba8910b5a0e187b6d72f8199ec5596a8c886306428e65384c64c9d8448899b135a6b475511b70203010001a317301530130603551d25040c300a06082b06010505070301300d06092a864886f70d010104050003820101008d78b0409b38f13e5247e8bfa2ec875b0b3aa8b078c93499685a329dd5db172edd EAP-Message = 0xf7044fa6c0dc973477d38b16017b700fb902dc1105aab27dc8df584114382f6feb5ff82d60c34944038e2c8c9a35e17608fb86059a993f5c11c1f562e62ebf084c02949afc475200cf6d905206281790557f8240dfe0b51cfa9f62f6441f7a1f9948ff755f6d233b7ca3dd1b17e791c5696ed87605d4ec4f3391c9f0bcad28a3fb38fab46c8727c1ba333fb97cef6cc98c5513dd7182bc84dde8b3e942237c68707609f4add151c10a695e52276545b5b924c6463a76672840eec790e7bf628fca86949f5bfa801239b56b7da6a885d3cb6b1274fdccec51fa3b322f31b730000478308204743082035ca003020102020900a0d66505b6fc09c7300d06 EAP-Message = 0x092a864886f70d0101050500 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x09b1011d0bb51850d61b870248979c7b Finished request 2. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.224.100 port 3072, id=134, length=175 User-Name = "NTB-KTM-01\\Administrator" Service-Type = Framed-User NAS-IP-Address = 192.168.224.100 NAS-Port = 1 NAS-Port-Id = "1" State = 0x09b1011d0bb51850d61b870248979c7b Called-Station-Id = "00-0B-6B-30-31-56:LANCOM" Calling-Station-Id = "00-21-6B-2A-72-AA" NAS-Identifier = "LANCOML-54g" NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020400061900 Message-Authenticator = 0xb1b616b078da871a9cfa265c77bca404 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "NTB-KTM-01\Administrator", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 4 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 134 to 192.168.224.100 port 3072 EAP-Message = 0x010503fc1940308182310b3009060355040613024445311630140603550408130d4e69656465727361636873656e310f300d060355040713064c4b4c656572310f300d060355040a13064c4b4c6565723126302406092a864886f70d010901161774686f6d61732e6c656e676572406c6b6c6565722e64653111300f060355040313084c4b4c6565724341301e170d3039303430373038313332315a170d3130303430373038313332315a308182310b3009060355040613024445311630140603550408130d4e69656465727361636873656e310f300d060355040713064c4b4c656572310f300d060355040a13064c4b4c6565723126302406092a86 EAP-Message = 0x4886f70d010901161774686f6d61732e6c656e676572406c6b6c6565722e64653111300f060355040313084c4b4c656572434130820122300d06092a864886f70d01010105000382010f003082010a0282010100de3334b9b2070fd570e6b885e2a0e65153f3e91eafd959ef18569a4b23a48856ca4f56fde415142acc09ef84132121a16a288bce815aaa25344aa2ee7fd3a5c76326366b169028e81bbfceda6ae036a9c8f6d87dbf59905cc2d6a97b707aee04f1bb5b090b8cbed7e919a8e0c36048a2ed7b2d2b7f12479bb7982144b86a8614414eab0e705750310b30126f2a9bcf25df9e1a89b31257c9c379c1d4d8b37653679360f69d7455a63d EAP-Message = 0xe157aa7327f6a3777bf8af781f1def2b3a1a958856c19f7ef9b998262ec290c985ad622a3fd7f2868e73e1c28d93e83c19a2c92980ec23ec09f3a5e3cc3fe973544434ec7b0da8d6feef9cf2c0f52382edc777ee81c1c50203010001a381ea3081e7301d0603551d0e04160414aacc35075d5a53fb5a8e743785787f36d2b43c213081b70603551d230481af3081ac8014aacc35075d5a53fb5a8e743785787f36d2b43c21a18188a48185308182310b3009060355040613024445311630140603550408130d4e69656465727361636873656e310f300d060355040713064c4b4c656572310f300d060355040a13064c4b4c6565723126302406092a86 EAP-Message = 0x4886f70d010901161774686f6d61732e6c656e676572406c6b6c6565722e64653111300f060355040313084c4b4c6565724341820900a0d66505b6fc09c7300c0603551d13040530030101ff300d06092a864886f70d0101050500038201010081d8f8d981692ad0182ae8aa0588f68f0e743202b708f5135bade85ff76af4c7685ade98fcdf6cd6de3c2c869cdd797e32fef739ca01e2435cceba60193f9061bde47a4cdb01c0f921e7c33fac42cb00ea2fc7def0b72b14944cdbf96504f6d6ca9a3814ae9cbf2d940c629ebffe99806077c8ad07ba7ebe2f629cfe14331370659f21c111c717e8c6804acaae323e7a88e0965e1c162fe95362704ee3 EAP-Message = 0xc0bf137a048e16c5 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x09b1011d0ab41850d61b870248979c7b Finished request 3. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.224.100 port 3072, id=170, length=175 User-Name = "NTB-KTM-01\\Administrator" Service-Type = Framed-User NAS-IP-Address = 192.168.224.100 NAS-Port = 1 NAS-Port-Id = "1" State = 0x09b1011d0ab41850d61b870248979c7b Called-Station-Id = "00-0B-6B-30-31-56:LANCOM" Calling-Station-Id = "00-21-6B-2A-72-AA" NAS-Identifier = "LANCOML-54g" NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020500061900 Message-Authenticator = 0x4a35aa0f4dd5c701c749d472b76bcfe2 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "NTB-KTM-01\Administrator", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 5 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 170 to 192.168.224.100 port 3072 EAP-Message = 0x0106006a1900d8f29ce2f96793d198e4346cbdc1ad31a5896f1407adade2d006cafdef4925eccb0d6a86abbd2fef7cca9910f2c67f9a213298110190b9e48e58d644465df8b7523705aeb6cd2ccf98754ab520aa87fa08f5a6292d4b6dfce7922616030100040e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x09b1011d0db71850d61b870248979c7b Finished request 4. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 192.168.224.100 port 3072, id=211, length=491 User-Name = "NTB-KTM-01\\Administrator" Service-Type = Framed-User NAS-IP-Address = 192.168.224.100 NAS-Port = 1 NAS-Port-Id = "1" State = 0x09b1011d0db71850d61b870248979c7b Called-Station-Id = "00-0B-6B-30-31-56:LANCOM" Calling-Station-Id = "00-21-6B-2A-72-AA" NAS-Identifier = "LANCOML-54g" NAS-Port-Type = Wireless-802.11 EAP-Message = 0x02060140198000000136160301010610000102010025711a02e7bc25aab9f85d277a7962bfff21e7998ac13bf4b25c7bbcb4711dfb0705ceb2b37733bf6cd96f85f1d3038ccb4fb3f4c7826a552962f0390b4d1777f4978bdc953b22158ac3c11d1e6144bb99c31be7cd96439ce84667aa79c93dc2f42b6be743a9562845c2133dc349b07e67f18e5e91617514704d79518ee08374f2965b204100bc4a305c427416f23ccfe95012079a07322cb3bdf6d2cb87be8d963f2ea6c578a3d5a1f7db95d1da024d3fdcb84444af07faaf378cae363388f25833acd8d75d384abb68d3e93891afa41b60acbc360984537dcfe304eaab9feed8c426b9332ec1e2 EAP-Message = 0x965e211b8e065d4a472778ae3a88efaf50d6193c62790a021403010001011603010020282065075d35d042dbb9f894d4773611edd9bc35b034d6fd2c216c60398fcb57 Message-Authenticator = 0x36cb41a6a8775c88e1e443b7d3c46a97 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "NTB-KTM-01\Administrator", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 6 length 253 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS TLS Length 310 [peap] Length Included [peap] eaptls_verify returned 11 [peap] <<< TLS 1.0 Handshake [length 0106], ClientKeyExchange [peap] TLS_accept: SSLv3 read client key exchange A [peap] <<< TLS 1.0 ChangeCipherSpec [length 0001] [peap] <<< TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 read finished A [peap] >>> TLS 1.0 ChangeCipherSpec [length 0001] [peap] TLS_accept: SSLv3 write change cipher spec A [peap] >>> TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 write finished A [peap] TLS_accept: SSLv3 flush data [peap] (other): SSL negotiation finished successfully SSL Connection Established [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 211 to 192.168.224.100 port 3072 EAP-Message = 0x0107003119001403010001011603010020bfc854b14959d8369186ec615304b1f082d3d77bcc479f59c9efde6dc5e9b766 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x09b1011d0cb61850d61b870248979c7b Finished request 5. Going to the next request Waking up in 4.8 seconds. Cleaning up request 0 ID 94 with timestamp +10 Cleaning up request 1 ID 100 with timestamp +10 Cleaning up request 2 ID 52 with timestamp +10 Cleaning up request 3 ID 134 with timestamp +10 Cleaning up request 4 ID 170 with timestamp +10 Cleaning up request 5 ID 211 with timestamp +10 Ready to process requests. rad_recv: Access-Request packet from host 192.168.224.100 port 3072, id=166, length=175 I hope I have included sufficient information of the problem. Thanks for your help. Best Regards Marten

1 0

Help with LDAP groupOfNames?
by Jason Antman 08 Apr '09

08 Apr '09

Sorry to re-post, but I'm still banging my head against the wall with this... If anyone could help, or provide a pointer to something that (obviously) I'm missing, it would be greatly appreciated. Hi, I've googled this to no avail (have been working on it for about 4 hours now). I'm running FreeRADIUS 1.1.0 (SuSE package) and OpenLDAP 2.3.19. I have an access point that will do captive portal, but only via RADIUS, not via LDAP natively. I already have an LDAP server running, so I just added a new groupOfNames called "WirelessUsers". Basically, *all* I want RADIUS to do is check the username and password, and assuming they are correct, either allow or deny based on whether the user is a member of "WirelessUsers". According to radtest, I have it working with LDAP, but it allows everyone with a valid username and password access, regardless of the WirelessUsers group - and I'm not seeing anything related to that group in the LDAP logs. I can't seem to find anything online for freeradius1 relating to groupOfNames, so I've just been trying random things that I found online (for raddb/users) hoping one would work. radiusd.conf: ldap { server = "127.0.0.1" basedn = "dc=example,dc=com" filter = "(&(objectClass=posixAccount)(uid=%{Stripped-User-Name:-%{User-Name}}))" start_tls = no dictionary_mapping = ${raddbdir}/ldap.attrmap ldap_connections_number = 5 password_attribute = userPassword groupname_attribute = cn groupmembership_filter = (|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn}))) groupmembership_attribute = "memberof" timeout = 4 timelimit = 3 net_timeout = 1 } users: #DEFAULT Auth-Type == LDAP # Fall-Through = Yes DEFAULT LDAP-Group == "WirelessUsers" Auth-Type := Reject #DEFAULT Ldap-Group != "WirelessUsers", Auth-Type := Reject # Reply-Message = "Sorry, your account has not yet been enabled for wireless access." #DEFAULT Huntgroup-Name == "wirelessusers", Ldap-Group=="WirelessUsers", Auth-Type = LDAP #DEFAULT Auth-Type := Reject #DEFAULT Ldap-Group == "WirelessUsers" # Fall-Through = no DEFAULT Ldap-Group == WirelessUsers Fall-Through = no DEFAULT Auth-Type := Reject I've tried all of the commented out stuff also, and none of it worked. All I want is (assuming username & password are correct) allow anyone who is in "WirelessUsers" group, deny everyone else. I'm sure this is horribly simple, but I just can't seem to figure it out from the docs or from extensive googling. Thanks for any help, Jason Antman

2 1

Redundant Load Balanced LDAP authentication fails when Primary is down
by Allers, Justin 08 Apr '09

08 Apr '09

Hello, I have two freeradius v2.1.3-1 servers setup to run with redundant load balancing with two Windows Active Directory LDAP servers for authentication. When the LDAP servers are running the radius will load-balance between them and authenticate fine. If I shut the primary LDAP server down radius doesn't authenticate properly against the second LDAP server. I have tested the secondary LDAP as the the primary in the radius configuration and it works fine. If I change the radius config to have a bogus primary name it will then authenticate with the secondary fine. But when it has the correct name and the primary is down the authentication fails. I believe it may have something to do with ntlm_auth but I don't understand why as in the other test instances with the bogus name it works. Below is the LDAP portion of my server along with a part of the debug of what happens when I shutdown the primary LDAP server. If anyone has any suggestions it would be much appreciated. Thank you, Justin Radius.conf ************************************************************************************************* ldap ds-01 { server = "ldap1.domain.org" port = 3268 identity = " bob(a)domain.org " password = "****" basedn = "dc=domain,dc=org" filter = "(sAMAccountname=%{mschap:User-Name:-%{User-Name}})" ldap_connections_number = 5 timeout = 4 timelimit = 3 net_timeout = 1 tls { start_tls = no } dictionary_mapping = ${confdir}/ldap.attrmap edir_account_policy_check = no groupname_attribute = cn groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))" groupmembership_attribute = memberOf } ldap ds-02 { server = "ldap2.domain.org" port = 3268 identity = "****" password = "****" basedn = "dc=domain,dc=org" filter = "(sAMAccountname=%{mschap:User-Name:-%{User-Name}})" ldap_connections_number = 5 timeout = 4 timelimit = 3 net_timeout = 1 tls { start_tls = no } dictionary_mapping = ${confdir}/ldap.attrmap edir_account_policy_check = no groupname_attribute = cn groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))" groupmembership_attribute = memberOf } instantiate { exec expr expiration logintime redundant-load-balance redundant_ldap { ds-01 ds-02 } } **************************************************************************************************** Debug file portion that points to ntlm_auth (as you can see the redundancy works except the ms-chap portion) **************************************************************************************************** ++- entering redundant-load-balance group redundant_ldap {...} [ds-01] performing user authorization for DoeJ [ds-01] expand: (sAMAccountname=%{mschap:User-Name:-%{User-Name}}) -> (sAMAccountname=DoeJ) [ds-01] expand: dc=domain,dc=org -> dc=domain,dc=org rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: attempting LDAP reconnection rlm_ldap: (re)connect to ldap1.domain.org:3268, authentication 0 rlm_ldap: bind as bob(a)domain.org/**** to ldap1.domain.org:3268 rlm_ldap: bob(a)domain.org bind to ldap1.domain.org:3268 failed: Can't contact LDAP server rlm_ldap: (re)connection attempt failed [ds-01] search failed rlm_ldap: ldap_release_conn: Release Id: 0 +++[ds-01] returns fail [ds-02] performing user authorization for DoeJ [ds-02] expand: (sAMAccountname=%{mschap:User-Name:-%{User-Name}}) -> (sAMAccountname=DoeJ) [ds-02] expand: dc=domain,dc=org -> dc=domain,dc=org rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in dc=domain,dc=org, with filter (sAMAccountname=DoeJ) [ds-02] looking for check items in directory... [ds-02] looking for reply items in directory... WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? [ds-02] user DoeJ authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 +++[ds-02] returns ok ++- redundant-load-balance group redundant_ldap returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/mschapv2 [eap] processing type mschapv2 [mschapv2] +- entering group MS-CHAP {...} [mschap] No Cleartext-Password configured. Cannot create LM-Password. [mschap] No Cleartext-Password configured. Cannot create NT-Password. [mschap] Told to do MS-CHAPv2 for DoeJ with NT-Password [mschap] WARNING: Deprecated conditional expansion ":-". See "man unlang" for details [mschap] expand: --username=%{Stripped-User-Name:-%{mschap:User-Name}} -> --username=DoeJ [mschap] mschap2: 4d [mschap] expand: --challenge=%{mschap:Challenge:-00} -> --challenge=92aa0495d9c105f7 [mschap] expand: --nt-response=%{mschap:NT-Response:-00} -> --nt-response=ab395391ee828796a6b2458cf767e8fa87eb8530457f7b67 Exec-Program output: No logon servers (0xc000005e) Exec-Program-Wait: plaintext: No logon servers (0xc000005e) Exec-Program: returned: 1 [mschap] External script failed. [mschap] FAILED: MS-CHAP2-Response is incorrect ++[mschap] returns reject [eap] Freeing handler ++[eap] returns reject Failed to authenticate the user. Login incorrect: [domain\\DoeJ] (from client switch-man-lan port 0 via TLS tunnel) ****************************************************************************************************

2 1

Authorization question
by Larry Ross 07 Apr '09

07 Apr '09

Hello all :) So after getting my testing box current with FR 2.1.5 I have my config 97% there, but I am having a interesting situation occur that I am hoping is fairly straight forward. Overview of config. User accounts authenticated against Kerberos KDC (Working 100%) User Account Attributes held in LDAP, LM Hash for PEAP, Blacklist (if you are in there you are denied) (working 100%) I cannot inject values into LDAP, would like to but cannot... So all that is left is a little authorization work. In my passwd module I have the following. (made sense to have the group name appear as if it came from the authenticator... hence the ~) passwd noc_group { filename = /usr/local/etc/raddb/group format = "~Group-Name:*,User-Name" hashsize = 50 ignorenislike = yes allowmultiplekeys = yes delimiter = ":" } the "Group" file is formatted NOC:Usernamea,Usernameb etc Here is where I get a touch lost. The noc_group section appears to be working, when I look at the debug output it is properly finding the usernames in the list and reports [noc_group] Added Group-Name: 'NOC' to request_items ++[noc_group] returns ok Now where to go from here... Let me start by where I would like to go... I would like to have a block of vendor specific radius attributes sent back in the access accept (assuming they passed authentication...) This way when folks log into network devices they are granted the correct level of access (like with our switches... Some people are granted read only access to verify certain aspects, and admins who get read write, so while I am starting with the admin group there will be other groups with different vendor specific attr's I would like to have sent for them.) I am assuming unlang will be the way to go however when I attempt to utilize this method I fail (Radius will not start as currently I am simply trying to append a Reply message when NOC-Group scores a hit. I have tried this in the post-auth section within default in sites-enabled. if (%{request:Group-Name} == "NOC") { Reply-Message = 'Noc-Group Match' } I receive "Unknown action 'NOC-Group Match' and radius does not load. (Error Initializing Modules) So where should I be placing the unlang code and what parameters does it understand and can pass to and from the daemon. Thank you Larry

2 3

Proxy everything but eap-md5 via Unlang?
by Stephen Bowman 07 Apr '09

07 Apr '09

Is there a way to match on the EAP type in unlang? I need to be able to proxy everything except incoming eap-md5 requests (which need to be handled remotely).

2 1

Multiple sessions with same session_id
by Clare Scally 07 Apr '09

07 Apr '09

Hi, We are currently moving from Cistron Radius on Freebsd 6.2 to Freeradius 2.0.5 on Freebsd 6.2. We have 2 freeradius servers and 1 Cistron server on our live network. On our Dial up system, on Cistron records 1 Start/ 1 Stop per Acct-Session-ID sent from a NAS. On Freeradius 2.0.5 it seems that the same session can have multiple Starts and Stops against one Acct-Session-ID. Is this normal behaviour and should these multiple tickets with the same session be recorded as 1 session? We have both running con currently and are seeing the multiplte Starts/Stops only on the Freeradius setup. There have been no configuration changes to the NAS to create the extra tickets. I have looked for documentation on this but cannot find any answers so if anyone can point me to documentation or confirm or deny that this is normal in Freeradius. Thanks, Clare Scally, Eircom, Senior System Administrator, ISP Hosting & Managed Services, Internet House, Temple Bar, Dublin 2 Tel: 01-7010911 Mob: 085-1744297

2 1

problem with rlm_dbm_parser and DEFAULT Realms
by Seamus Bridgeman 07 Apr '09

07 Apr '09

Using freeradius2.1.3 and rlm_dbm module Having a problem with rlm_dbm_parser to create dbm file. Testing with 3 DEFAULT Realm records and two username/password. Seems to be overwriting DEFAULT Realm as only last one exists. rlm_dbm_parser reports all records read and no errors but rlm_dbm_cat shows only last Default. radclient tests naturally only succeed with DEFAULT domain_three Is there a know issue here on creating dbm files or have I missed some setting to allow multiple DEFAULT Realm=xxx records in dbm file. Desired approach is - dbm file with large numbers of DEFAULT Realm and all with no fallthru. - we have no other (catch-all) DEFAULTs with explicit accept or reject - ideally usernames matching these realms (proxy.conf) and DEFAULT Realm should respond with Accept straight away - no searching full subscriber base dbm file and then DEFAULT match. (e.g treat DEFAULT Realm =xxx as distinct from generic DEFAULT) - ideally have DEFAULT Realm=xxx be read in to hash/memory from separate file and DBM users just have subscriber base (user/pass). This way every time users.db updated/re-created/re-read - does not impact DEFAULT Realm=xxx records. The later Realms more static - subscriber base changes more dynamic. - Also using dbm as faster/ less memory resources and no need to restart radiusd as dbm files change - and do change constantly.. This possible? Logs below: Test users file -------------------- DEFAULT Realm == "domain_one", Auth-Type := Accept Tunnel-Type:1 = L2TP, Tunnel-Medium-Type:1 = IP, Tunnel-Server-Endpoint:1 = "xxx.xxx.xxx.xxx", Tunnel-Client-Auth-Id:1 = "realm1", Tunnel-Password:1 = "xxx", Tunnel-Assignment-Id:1 = "xxx", Tunnel_Algorithm = 2, Tunnel_Domain = 1 DEFAULT Realm == "domain_two", Auth-Type := Accept Tunnel-Type:1 = L2TP, Tunnel-Medium-Type:1 = IP, Tunnel-Server-Endpoint:1 = "xxx.xxx.xxx.xxx", Tunnel-Client-Auth-Id:1 = "realm2", Tunnel-Password:1 = "xxx", Tunnel-Assignment-Id:1 = "xxx", Tunnel_Algorithm = 2, Tunnel_Domain = 1 DEFAULT Realm == "domain_three", Auth-Type := Accept Tunnel-Type:1 = L2TP, Tunnel-Medium-Type:1 = IP, Tunnel-Server-Endpoint:1 = "xxx.xxx.xxx.xxx", Tunnel-Client-Auth-Id:1 = "realm3", Tunnel-Password:1 = "xxx", Tunnel-Assignment-Id:1 = "xxx", Tunnel_Algorithm = 2, Tunnel_Domain = 1 userone@one Cleartext-Password := "pass" Class = "xxxclass1xxx", Service-Type = Framed-User, Framed-Protocol = PPP usertwo@norealm Cleartext-Password := "pass", Calling-Station-Id == "123456" Service-Type = Framed-User, Framed-Protocol = PPP, Framed-IP-Address = 10.10.10.0, Framed-IP-Netmask = 255.255.255.240, ------------------------------------------------------------------ rlm_dbm_parser logs: %% # /usr/local/freeradius/bin/rlm_dbm_parser -c -xxx -i /usr/local/freeradius/etc/raddb/users_generic -o /usr/local/freeradius/etc/raddb/users Use dictionary in: /usr/local/freeradius/etc/raddb Found user: DEFAULT Found user: DEFAULT Found user: DEFAULT Found user: userone@one Found user: usertwo@norealm Record loaded: 5 Lines parsed: 41 Record skiped: 0 Warnings: 0 Errors: 0 %%# rlm_dbm_cat logs - only shows last DEFAULT Realm ------------------------------ %% # /usr/local/freeradius/bin/rlm_dbm_cat -f /usr/local/freeradius/etc/raddb/users DEFAULT Realm == "domain_three", Auth-Type := Accept Tunnel-Type:1 = L2TP, Tunnel-Medium-Type:1 = IPv4, Tunnel-Server-Endpoint:1 = "xxx.xxx.xxx.xxx", Tunnel-Client-Auth-Id:1 = "realm3", Tunnel-Password:1 = "xxx", Tunnel-Assignment-Id:1 = "xxx", Tunnel_Algorithm = 2, Tunnel_Domain = 1 userone@one Cleartext-Password := "pass" Class = "xxxclass1xxx", Service-Type = Framed-User, Framed-Protocol = PPP usertwo@norealm Cleartext-Password := "pass", Calling-Station-Id == "123456" Service-Type = Framed-User, Framed-Protocol = PPP, Framed-IP-Address = 10.10.10.0, Framed-IP-Netmask = 255.255.255.240 %%# ----------------------- Havent included radiusd -X logs as issue seems to be creating dbm file and hence before using Radius. radclient tests are successful when matching 3 records that do exit in dbm file. Problem is two missing records

2 3