October 2017 - Freeradius-Users - lists.freeradius.org

new freeradius setup
by Andrew Meyer 26 Oct '17

26 Oct '17

I am running CentOS 7. I am setting up FreeRADIUS again. Documenting it step-by-step. I am only working the test user at the moment but I am getting the following error: Tue Oct 24 19:30:28 2017 : Debug: (0) User-Name = "bob"Tue Oct 24 19:30:28 2017 : Debug: (0) User-Password = "hello"Tue Oct 24 19:30:28 2017 : Debug: (0) NAS-IP-Address = 10.150.10.40Tue Oct 24 19:30:28 2017 : Debug: (0) NAS-Port = 0Tue Oct 24 19:30:28 2017 : Debug: (0) Message-Authenticator = 0x7c0ca39b4c7952c808f3602792b02eb6Tue Oct 24 19:30:28 2017 : Debug: (0) session-state: No State attributeTue Oct 24 19:30:28 2017 : Debug: (0) Empty authorize section. Using default return values.Tue Oct 24 19:30:28 2017 : ERROR: (0) No Auth-Type found: rejecting the user via Post-Auth-Type = RejectTue Oct 24 19:30:28 2017 : Debug: (0) Failed to authenticate the userTue Oct 24 19:30:28 2017 : Auth: (0) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client localhost port 0)Tue Oct 24 19:30:28 2017 : Debug: (0) Using Post-Auth-Type RejectTue Oct 24 19:30:28 2017 : Debug: (0) Post-Auth-Type sub-section not found. Ignoring.Tue Oct 24 19:30:28 2017 : Debug: (0) Delaying response for 1.000000 secondsTue Oct 24 19:30:28 2017 : Debug: Thread 3 waiting to be assigned a requestTue Oct 24 19:30:28 2017 : Debug: Waking up in 0.6 seconds.Tue Oct 24 19:30:29 2017 : Debug: (0) Sending delayed responseTue Oct 24 19:30:29 2017 : Debug: (0) Sent Access-Reject Id 16 from 10.150.10.40:1812 to 10.150.10.40:43969 length 20Tue Oct 24 19:30:29 2017 : Debug: Waking up in 3.9 seconds.Tue Oct 24 19:30:33 2017 : Debug: (0) Cleaning up request packet ID 16 with timestamp +67Tue Oct 24 19:30:33 2017 : Info: Ready to process requests Here is my config from /etc/raddb/users:bob Auth-Type := Accept Cleartext-Password := "hello" Reply-Message := "Hello, %{User-Name}" I tried not using a client config and then ended up putting in the following: client testing { ipaddr = 10.150.0.0/16 secret = testing123 } radtest bob hello 10.150.10.40:1812 0 testing123Sent Access-Request Id 119 from 0.0.0.0:56648 to 10.150.10.40:1812 length 73 User-Name = "bob" User-Password = "hello" NAS-IP-Address = 10.150.10.40 NAS-Port = 0 Message-Authenticator = 0x00 Cleartext-Password = "hello"Received Access-Reject Id 119 from 10.150.10.40:1812 to 0.0.0.0:0 length 20(0) -: Expected Access-Accept got Access-Reject Is there something I missed in the configuration? Thank you,

5 17

Statistic from Status server
by Peter Balsianok 26 Oct '17

26 Oct '17

Hi, I want to retrieve statistic for particular home server via Status-Server. but server sends empty answer. At the end of debug log you can find request. Help please, thx Debug log: FreeRADIUS Version 3.0.13 Copyright (C) 1999-2017 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 For more information about these matters, see the file named COPYRIGHT Starting - reading configuration files ... including dictionary file /app/radius/freeradius-3.0.13/share/freeradius/dictionary including dictionary file /app/radius/freeradius-3.0.13/share/freeradius/dictionary.dhcp including dictionary file /app/radius/freeradius-3.0.13/share/freeradius/dictionary.vqp including dictionary file /app/radius/conf/auth-test/dictionary including configuration file /app/radius/conf/auth-test/radiusd.conf including configuration file /app/radius/conf/auth-test/templates.conf including configuration file /app/radius/conf/auth-test/proxy.conf including configuration file /app/radius/conf/auth-test/clients.conf including files in directory /app/radius/conf/auth-test/mods-enabled/ including configuration file /app/radius/conf/auth-test/mods-enabled/unpack including configuration file /app/radius/conf/auth-test/mods-enabled/files including configuration file /app/radius/conf/auth-test/mods-enabled/expr including configuration file /app/radius/conf/auth-test/mods-enabled/preprocess including configuration file /app/radius/conf/auth-test/mods-enabled/chap including configuration file /app/radius/conf/auth-test/mods-enabled/attr_filter including configuration file /app/radius/conf/auth-test/mods-enabled/always including configuration file /app/radius/conf/auth-test/mods-enabled/linelog including configuration file /app/radius/conf/auth-test/mods-enabled/perl including configuration file /app/radius/conf/auth-test/mods-enabled/ldap including configuration file /app/radius/conf/auth-test/mods-enabled/realm including configuration file /app/radius/conf/auth-test/mods-enabled/pap including files in directory /app/radius/conf/auth-test/policy-enabled/ including configuration file /app/radius/conf/auth-test/policy-enabled/RAN-BACKUP including configuration file /app/radius/conf/auth-test/policy-enabled/accounting including configuration file /app/radius/conf/auth-test/policy-enabled/SkyToll.new including configuration file /app/radius/conf/auth-test/policy-enabled/huntgroup including configuration file /app/radius/conf/auth-test/policy-enabled/post-proxy including configuration file /app/radius/conf/auth-test/policy-enabled/FixedLTE including configuration file /app/radius/conf/auth-test/policy-enabled/username including configuration file /app/radius/conf/auth-test/policy-enabled/nas including configuration file /app/radius/conf/auth-test/policy-enabled/SkyToll including files in directory /app/radius/conf/auth-test/sites-enabled/ including configuration file /app/radius/conf/auth-test/sites-enabled/control-socket including configuration file /app/radius/conf/auth-test/sites-enabled/default including configuration file /app/radius/conf/auth-test/sites-enabled/status main { name = "auth-test" prefix = "/app/radius/freeradius-v3" localstatedir = "/app_log/radius/auth-test/" sbindir = "/app/radius/freeradius-v3/sbin" logdir = "/app_log/radius/auth-test/" run_dir = "/app_log/radius/auth-test/" libdir = "/app/radius/freeradius-v3/lib" radacctdir = "/app_log/radius/auth-test//radacct" panic_action = "gdb -silent -x /app/radius/conf/auth-test/panic.gdb %e %p 2>&1 | tee /app_log/radius/auth-test//gdb-auth-test-%p.log" hostname_lookups = no max_request_time = 7 cleanup_delay = 2 max_requests = 25600 pidfile = "/app_log/radius/auth-test//radius.pid" checkrad = "/app/radius/freeradius-v3/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = yes auth_badpass = yes auth_goodpass = yes colourise = yes msg_denied = "You are already logged in - access denied" } resources { } security { max_attributes = 200 reject_delay = 0.000000 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 } WARNING: Ignoring "response_window = 30.000000", forcing to "response_window = 7.000000" home_server vse_server1_prod { ipaddr = 10.14.135.145 port = 1812 type = "auth" secret = <<< secret >>> response_window = 30.000000 response_timeouts = 1 max_outstanding = 65536 zombie_period = 40 status_check = "request" ping_interval = 30 check_interval = 6 check_timeout = 4 num_answers_to_alive = 3 revive_interval = 300 username = "orange-system" password = "incorrect" limit { max_connections = 16 max_requests = 0 lifetime = 0 idle_timeout = 0 } coa { irt = 2 mrt = 16 mrc = 5 mrd = 30 } } WARNING: Ignoring "response_window = 30.000000", forcing to "response_window = 7.000000" home_server vse_server2_prod { ipaddr = 10.14.135.146 port = 1812 type = "auth" secret = <<< secret >>> response_window = 30.000000 response_timeouts = 1 max_outstanding = 65536 zombie_period = 40 status_check = "request" ping_interval = 30 check_interval = 6 check_timeout = 4 num_answers_to_alive = 3 revive_interval = 300 username = "orange-system" password = "incorrect" limit { max_connections = 16 max_requests = 0 lifetime = 0 idle_timeout = 0 } coa { irt = 2 mrt = 16 mrc = 5 mrd = 30 } } WARNING: Ignoring "response_window = 30.000000", forcing to "response_window = 7.000000" home_server_pool prod_pool_vse { type = load-balance home_server = vse_server1_prod home_server = vse_server2_prod } realm vsetest.sk { auth_pool = prod_pool_vse nostrip } realm vseazd.sk { auth_pool = prod_pool_vse nostrip } realm vseusec.sk { auth_pool = prod_pool_vse nostrip } realm vsegps.sk { auth_pool = prod_pool_vse nostrip } realm vsesec.sk { auth_pool = prod_pool_vse nostrip } realm vseewo.sk { auth_pool = prod_pool_vse nostrip } realm vseims.sk { auth_pool = prod_pool_vse nostrip } realm vsdvip.sk { auth_pool = prod_pool_vse nostrip } realm LOCAL { authhost = LOCAL accthost = LOCAL } realm NULL { authhost = LOCAL accthost = LOCAL } realm DEFAULT { authhost = LOCAL accthost = LOCAL } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = <<< secret >>> nas_type = "other" proto = "*" limit { max_connections = 16 lifetime = 0 idle_timeout = 30 } } Debugger not attached # Creating Auth-Type = PERL # Creating Auth-Type = PAP # Creating Auth-Type = CHAP # Creating Autz-Type = Status-Server # Instantiating module "files" from file /app/radius/conf/auth-test/mods-enabled/files reading pairlist file /app/radius/conf/auth-test/mods-config/files/authorize reading pairlist file /app/radius/conf/auth-test/mods-config/files/authorize reading pairlist file /app/radius/conf/auth-test/mods-config/files/accounting reading pairlist file /app/radius/conf/auth-test/mods-config/files/pre-proxy # Instantiating module "preprocess" from file /app/radius/conf/auth-test/mods-enabled/preprocess # Instantiating module "attr_filter.post-proxy" from file /app/radius/conf/auth-test/mods-enabled/attr_filter reading pairlist file /app/radius/conf/auth-test/mods-config/attr_filter/post-proxy # Instantiating module "attr_filter.pre-proxy" from file /app/radius/conf/auth-test/mods-enabled/attr_filter reading pairlist file /app/radius/conf/auth-test/mods-config/attr_filter/pre-proxy # Instantiating module "attr_filter.access_reject" from file /app/radius/conf/auth-test/mods-enabled/attr_filter reading pairlist file /app/radius/conf/auth-test/mods-config/attr_filter/access_reject # Instantiating module "attr_filter.access_challenge" from file /app/radius/conf/auth-test/mods-enabled/attr_filter reading pairlist file /app/radius/conf/auth-test/mods-config/attr_filter/access_challenge # Instantiating module "attr_filter.accounting_response" from file /app/radius/conf/auth-test/mods-enabled/attr_filter reading pairlist file /app/radius/conf/auth-test/mods-config/attr_filter/accounting_response # Instantiating module "reject" from file /app/radius/conf/auth-test/mods-enabled/always # Instantiating module "fail" from file /app/radius/conf/auth-test/mods-enabled/always # Instantiating module "ok" from file /app/radius/conf/auth-test/mods-enabled/always # Instantiating module "handled" from file /app/radius/conf/auth-test/mods-enabled/always # Instantiating module "invalid" from file /app/radius/conf/auth-test/mods-enabled/always # Instantiating module "userlock" from file /app/radius/conf/auth-test/mods-enabled/always # Instantiating module "notfound" from file /app/radius/conf/auth-test/mods-enabled/always # Instantiating module "noop" from file /app/radius/conf/auth-test/mods-enabled/always # Instantiating module "updated" from file /app/radius/conf/auth-test/mods-enabled/always radiusd: #### Loading Virtual Servers #### server { # from file /app/radius/conf/auth-test/radiusd.conf } # server server default { # from file /app/radius/conf/auth-test/sites-enabled/default # Loading authenticate {...} # Loading authorize {...} # Loading pre-proxy {...} # Loading post-auth {...} } # server default server status { # from file /app/radius/conf/auth-test/sites-enabled/status # Loading authorize {...} } # server status radiusd: #### Opening IP addresses and Ports #### listen { type = "control" listen { socket = "/app/radius/conf/auth-test/control.socket" mode = "rw" peercred = yes } } listen { type = "auth" ipv4addr = * port = 10812 limit { max_pps = 0 max_connections = 16 lifetime = 0 idle_timeout = 30 } } listen { type = "auth" ipv4addr = * port = 10645 limit { max_pps = 0 max_connections = 16 lifetime = 0 idle_timeout = 30 } } listen { type = "status" ipaddr = 127.0.0.1 port = 28121 client admin { ipaddr = 127.0.0.1 require_message_authenticator = no secret = <<< secret >>> limit { max_connections = 16 lifetime = 0 idle_timeout = 30 } } } Listening on command file /app/radius/conf/auth-test/control.socket Listening on auth address * port 10812 bound to server default Listening on auth address * port 10645 bound to server default Listening on status address 127.0.0.1 port 28121 bound to server status Listening on proxy address * port 33049 Ready to process requests (0) Received Status-Server Id 246 from 127.0.0.1:40048 to 127.0.0.1:28121 length 74 (0) Message-Authenticator = 0x4c348183f7bb200825f992012e53b89e (0) FreeRADIUS-Statistics-Type = 131 (0) FreeRADIUS-Stats-Server-IP-Address = 10.14.135.145 (0) FreeRADIUS-Stats-Server-Port = 1812 (0) # Executing group from file /app/radius/conf/auth-test/sites-enabled/status (0) Autz-Type Status-Server { (0) [ok] = ok (0) } # Autz-Type Status-Server = ok (0) Sent Access-Accept Id 246 from 127.0.0.1:28121 to 127.0.0.1:40048 length 0 (0) Finished request Waking up in 1.9 seconds. (0) Cleaning up request packet ID 246 with timestamp +35

3 11

Cisco + Radius
by Yahn do Amaral Almeida Pinheiro 26 Oct '17

26 Oct '17

I'm trying to use the cisco to authenticate in freeradius, but it's not working. When I test a request, it appears in the radius debug that the password is wrong, but I'm sure it's right. Would you have any documents that could tell me about configuring Radius + Cisco? And, what is cisco-vsa-hack?

3 3

Multiple Windows Domains
by Brian Smith - IN2IT 26 Oct '17

26 Oct '17

Hello All Doing a little research. We have a customer that has 5 different Windows Active Directory domains (separate companies) all using their own IP address ranges. What they want to achieve, irrespective on where the users physically reside is for the radius server to identify the user from their login details and then issue out the correct IP address for that company. Has anyone done anything like this using FreeRadius? Regards Brian Smith IN 2 IT Tel: +27 11 453 9136 Fax: +27 11 453 1788 Connect with me on Facebook <https://www.facebook.com/BrianSmithIN2IT> https://www.facebook.com/BrianSmithIN2IT <http://www.in2it.co.za/> in2itlogo <http://www.facebook.com/pages/in2itcoza/146008768784049> facebook <https://www.linkedin.com/company/in2it-> linkedin PLEASE NOTE: For Technical queries, log your request via the IN2IT Ticket system. This may be found on <http://www.in2it.co.za> www.in2it.co.za under the Log Support option. This is the preferred system for support for reasons of transparency. Whatsapp, email and SMS requests do not guarentee immediate action. Tickets may be created telephonically, please phone should the above system not be available.

3 2

Checking for disabled ad account
by Alex Sharaz 26 Oct '17

26 Oct '17

Hi I’ve configured EAP-TLS with ocsp validation in FR 3.0.16 I’ve now been told that I need to also check that the username associated with the account hasn’t been disabled in our AD service. Same FR server also does EAP-PEAP auth against AD Any suggestions as to how I might do this ? Rgds Alex Sent from my iPhone 6 plus

3 3

FreeRADIUS 3.0.15 fails to respond with TLS 1.0 (Debian testing)
by Thomas d'Otreppe 25 Oct '17

25 Oct '17

Hi, it looks like FreeRADIUS 3.0.15 doesn't work anymore on Debian testing (with OpenSSL). I tried connecting an Android 6.0 client to FreeRADIUS and from what I understand from the following log, it fails responding to one part of the request because it tries to use TLS 1.0 (eap_peap: ERROR: Failed in __FUNCTION__ (SSL_read): error:1417D102:SSL routines:tls_process_client_hello:unsupported protocol) and AFAIK, TLS 1.0 is not supported anymore in OpenSSL: (0) Received Access-Request Id 37 from 192.168.0.254:46065 to 192.168.0.100:1812 length 139 (0) User-Name = "me" (0) NAS-IP-Address = 192.168.0.254 (0) NAS-Port = 0 (0) Called-Station-Id = "D0-7D-0D-0F-1B-22:MyAP" (0) Calling-Station-Id = "12-34-56-78-90-AB" (0) Framed-MTU = 1400 (0) NAS-Port-Type = Wireless-802.11 (0) Connect-Info = "CONNECT 0Mbps 802.11" (0) EAP-Message = 0x02000007016d65 (0) Message-Authenticator = 0xb909500b8d92f535dd010ce46c878d47 (0) # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default (0) authorize { (0) policy filter_username { (0) if (&User-Name) { (0) if (&User-Name) -> TRUE (0) if (&User-Name) { (0) if (&User-Name =~ / /) { (0) if (&User-Name =~ / /) -> FALSE (0) if (&User-Name =~ /@[^@]*@/ ) { (0) if (&User-Name =~ /@[^@]*@/ ) -> FALSE (0) if (&User-Name =~ /\.\./ ) { (0) if (&User-Name =~ /\.\./ ) -> FALSE (0) if ((&User-Name =~ /@/) && (&User-Name !~ /(a)(.+)\.(.+)$/)) { (0) if ((&User-Name =~ /@/) && (&User-Name !~ /(a)(.+)\.(.+)$/)) -> FALSE (0) if (&User-Name =~ /\.$/) { (0) if (&User-Name =~ /\.$/) -> FALSE (0) if (&User-Name =~ /(a)\./) { (0) if (&User-Name =~ /(a)\./) -> FALSE (0) } # if (&User-Name) = notfound (0) } # policy filter_username = notfound (0) [preprocess] = ok (0) [chap] = noop (0) [mschap] = noop (0) [digest] = noop (0) suffix: Checking for suffix after "@" (0) suffix: No '@' in User-Name = "me", looking up realm NULL (0) suffix: No such realm "NULL" (0) [suffix] = noop (0) eap: Peer sent EAP Response (code 2) ID 0 length 7 (0) eap: EAP-Identity reply, returning 'ok' so we can short-circuit the rest of authorize (0) [eap] = ok (0) } # authorize = ok (0) Found Auth-Type = eap (0) # Executing group from file /usr/local/etc/raddb/sites-enabled/default (0) authenticate { (0) eap: Peer sent packet with method EAP Identity (1) (0) eap: Calling submodule eap_peap to process data (0) eap_peap: Initiating new EAP-TLS session (0) eap_peap: [eaptls start] = request (0) eap: Sending EAP Request (code 1) ID 1 length 6 (0) eap: EAP session adding &reply:State = 0xf60008ccf601110e (0) [eap] = handled (0) } # authenticate = handled (0) Using Post-Auth-Type Challenge (0) # Executing group from file /usr/local/etc/raddb/sites-enabled/default (0) Challenge { ... } # empty sub-section is ignored (0) Sent Access-Challenge Id 37 from 192.168.0.100:1812 to 192.168.0.254:46065 length 0 (0) EAP-Message = 0x010100061920 (0) Message-Authenticator = 0x00000000000000000000000000000000 (0) State = 0xf60008ccf601110e4d96bfb0034242b4 (0) Finished request Waking up in 4.9 seconds. (1) Received Access-Request Id 38 from 192.168.0.254:46065 to 192.168.0.100:1812 length 260 (1) User-Name = "me" (1) NAS-IP-Address = 192.168.0.254 (1) NAS-Port = 0 (1) Called-Station-Id = "D0-7D-0D-0F-1B-22:MyAP" (1) Calling-Station-Id = "12-34-56-78-90-AB" (1) Framed-MTU = 1400 (1) NAS-Port-Type = Wireless-802.11 (1) Connect-Info = "CONNECT 0Mbps 802.11" (1) EAP-Message = 0x0201006e198000000064160301005f0100005b0301f3660ce76c4adfd99ae7f539e1867cd020b0da3f818c40bf2116c330cdb148c100001cc00ac0140039c009c0130033c007c0110035002f00050004000a00ff0100001600170000000b00020100000a00080006001700180019 (1) State = 0xf60008ccf601110e4d96bfb0034242b4 (1) Message-Authenticator = 0xc2e06b9b63ab56c6fbe401b903304705 (1) session-state: No cached attributes (1) # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default (1) authorize { (1) policy filter_username { (1) if (&User-Name) { (1) if (&User-Name) -> TRUE (1) if (&User-Name) { (1) if (&User-Name =~ / /) { (1) if (&User-Name =~ / /) -> FALSE (1) if (&User-Name =~ /@[^@]*@/ ) { (1) if (&User-Name =~ /@[^@]*@/ ) -> FALSE (1) if (&User-Name =~ /\.\./ ) { (1) if (&User-Name =~ /\.\./ ) -> FALSE (1) if ((&User-Name =~ /@/) && (&User-Name !~ /(a)(.+)\.(.+)$/)) { (1) if ((&User-Name =~ /@/) && (&User-Name !~ /(a)(.+)\.(.+)$/)) -> FALSE (1) if (&User-Name =~ /\.$/) { (1) if (&User-Name =~ /\.$/) -> FALSE (1) if (&User-Name =~ /(a)\./) { (1) if (&User-Name =~ /(a)\./) -> FALSE (1) } # if (&User-Name) = notfound (1) } # policy filter_username = notfound (1) [preprocess] = ok (1) [chap] = noop (1) [mschap] = noop (1) [digest] = noop (1) suffix: Checking for suffix after "@" (1) suffix: No '@' in User-Name = "me", looking up realm NULL (1) suffix: No such realm "NULL" (1) [suffix] = noop (1) eap: Peer sent EAP Response (code 2) ID 1 length 110 (1) eap: Continuing tunnel setup (1) [eap] = ok (1) } # authorize = ok (1) Found Auth-Type = eap (1) # Executing group from file /usr/local/etc/raddb/sites-enabled/default (1) authenticate { (1) eap: Expiring EAP session with state 0xf60008ccf601110e (1) eap: Finished EAP session with state 0xf60008ccf601110e (1) eap: Previous EAP request found for state 0xf60008ccf601110e, released from the list (1) eap: Peer sent packet with method EAP PEAP (25) (1) eap: Calling submodule eap_peap to process data (1) eap_peap: Continuing EAP-TLS (1) eap_peap: Peer indicated complete TLS record size will be 100 bytes (1) eap_peap: Got complete TLS record (100 bytes) (1) eap_peap: [eaptls verify] = length included (1) eap_peap: (other): before SSL initialization (1) eap_peap: TLS_accept: before SSL initialization (1) eap_peap: TLS_accept: before SSL initialization (1) eap_peap: <<< recv TLS 1.2 [length 005f] (1) eap_peap: >>> send TLS 1.0 Alert [length 0002], fatal protocol_version (1) eap_peap: ERROR: TLS Alert write:fatal:protocol version tls: TLS_accept: Error in error (1) eap_peap: ERROR: Failed in __FUNCTION__ (SSL_read): error:1417D102:SSL routines:tls_process_client_hello:unsupported protocol (1) eap_peap: ERROR: System call (I/O) error (-1) (1) eap_peap: ERROR: TLS receive handshake failed during operation (1) eap_peap: ERROR: [eaptls process] = fail (1) eap: ERROR: Failed continuing EAP PEAP (25) session. EAP sub-module failed (1) eap: Sending EAP Failure (code 4) ID 1 length 4 (1) eap: Failed in EAP select (1) [eap] = invalid (1) } # authenticate = invalid (1) Failed to authenticate the user (1) Using Post-Auth-Type Reject (1) # Executing group from file /usr/local/etc/raddb/sites-enabled/default (1) Post-Auth-Type REJECT { (1) attr_filter.access_reject: EXPAND %{User-Name} (1) attr_filter.access_reject: --> me (1) attr_filter.access_reject: Matched entry DEFAULT at line 11 (1) [attr_filter.access_reject] = updated (1) [eap] = noop (1) policy remove_reply_message_if_eap { (1) if (&reply:EAP-Message && &reply:Reply-Message) { (1) if (&reply:EAP-Message && &reply:Reply-Message) -> FALSE (1) else { (1) [noop] = noop (1) } # else = noop (1) } # policy remove_reply_message_if_eap = noop (1) } # Post-Auth-Type REJECT = updated (1) Delaying response for 1.000000 seconds Waking up in 0.3 seconds. Waking up in 0.6 seconds. (1) Sending delayed response (1) Sent Access-Reject Id 38 from 192.168.0.100:1812 to 192.168.0.254:46065 length 44 (1) EAP-Message = 0x04010004 (1) Message-Authenticator = 0x00000000000000000000000000000000 Waking up in 3.9 seconds. (0) Cleaning up request packet ID 37 with timestamp +23 (1) Cleaning up request packet ID 38 with timestamp +23 Am I correct? If yes, is there any solution/workaround? Should I open a bug report? I tried to look for forcing TLS 1.2 but it doesn't seem to be an option anywhere (it can be disabled though). Thanks, Thomas

3 5

Multiple VLAN value per user
by Germán Espinoza Tuesta 25 Oct '17

25 Oct '17

Hi, Most of dynamic VLAN assignment implementations use these RADIUS attributes to work: Considering a user from VLAN 100: Tunnel-Type = 13, #VLAN Tunnel-Medium-Type = 6, #IEEE-802 Tunnel-Private-Group-Id = "100" Is there a way for freeradius to return multiple values in Tunnel-Private-Group-Id. I'm working in a project where I want a user to belong to multiple vlans. At the moment, working with a sql database. I'll appreciate your help, thanks in advance. Best regards, Germán Espinoza

3 4

No EAP session matching state ...
by Fikais Ladislav 25 Oct '17

25 Oct '17

Hello, I've migrated from FRv2 to 3.0.15 and there is a lot of "No EAP session matching state..." messages and auth rejects. The strange thing is the first request for some user is received with State attribute (which is wrong, right?) so the FR doesn't know this session and sends reject. Full debug from about one minute is here: https://dec59.ruk.cuni.cz/~fikais/fr/r1c3x.log I know that after daemon reload the EAP sessions are lost but it works this way even if it runs for hours... Am I doing something wrong? Thanks. Ladislav Fikais Charles University Computer Centre Petrská 3, Praha 1 110 00, Czech Republic

2 6

Filter attributes at rest module
by Mikhail Gaidamaka 25 Oct '17

25 Oct '17

Hi, all! I'm using rest module to connect to my java restful service with json format request. It works good, but i get troubles with EAP-TLS - it tries to encode ALL request content. How I can skip unused attributes (EAP-Message and other specific attrs). I have tried to use attr_filter module, but it do 'noop'. How I can limit attributes, that will be encoded to json?

3 3

Attribute filtering with regex problem
by John Horne 24 Oct '17

24 Oct '17

Hello, (Using Freeradius 3.0.13) I have been modifying our 'mods-config/attr_filter/post-proxy' filter file to allow through a couple of 'Service-Type' attribute values after proxying. However, to allow more than one value the only way I can get it to work is to specify the value as 'ANY'. (Running 'radiusd -X' shows the access-accept packet being sent out with the attribute.) In particular, I have been trying to use a regular expression but the attribute always gets filtered out. This works: Service-Type =* ANY, I have also tried: Service-Type =~ /Framed-User|Login-User/, also Service-Type =~ "Framed-User|Login-User", also Service-Type =~ "/Framed-User|Login-User/", even Service-Type =~ Framed-User|Login-User, These all failed. Running 'radiusd -X' showed no error or warning with the filter files syntax for the entry, but showed the acess-accept packet being sent out without the attribute. I finally repeated the above regex entries just using 'Framed-User' (in case the '|' was causing a problem). These too caused the attribute to be filtered out. So my question is, what is the correct syntax for using '=~' with a regex in the post-proxy filter file? Thanks, John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

2 2