November 2014 - Freeradius-Users - lists.freeradius.org

Authenticate to AD but only allow certain group
by Brian C. Huffman 16 Aug '25

16 Aug '25

All, I've got authentication working nicely with MSCHAP, but now I'd like to only allow users that are members of a certain AD group. I would prefer to have this happen only when requests come from a specific client (wireless access point). In this case the idea is to have users only be able to get wireless access when they're in a specific AD group. How can I do this in freeradius? Thanks, Brian

7 18

Detailed Logging freeradius Request Packets
by Jean-Francois Mousinho 28 Oct '19

28 Oct '19

Hi, I've tried to find a way of detail logging the packets sent by freeradius to the client in the authentication phase but didn't found a way of doing it. Maybe I've not looked correctly so I'm asking if it's actually possible? I was able to log detailed packets sent by the client (Response packets) but not the ones sent by freeradius to the client (except accounting and proxied ones). Thanks for your time. Jean-François Mousinho

4 6

user-group for rejected users
by Fabricio Viana 21 Mar '17

21 Mar '17

Hello! Let´s suppose the following situations: 1) User exists but the password is wrong 2) User does not exist In both cases the answer is REJECT. It happens that certain hardware is making endless attempts that eventually saturating the server. - It is possible to cause the server, instead of rejecting the users, accept the login but responds ACCEPT with "framed-pool = pool-block" ? or/and - Is there any way to put REJECT users in a given group by default? Thanks! Fabricio

3 3

No Logon Servers error with FreeRADIUS + NTLM
by Stefan Paetow 19 Feb '16

19 Feb '16

Hi, I know this is not a problem with FreeRADIUS, however, there are several people on this list who run FreeRADIUS with Active Directory as a back end and I need their advice on this. I've run into the dreaded "No logon servers (0xc000005e)" error with NTLM. In the past I've found that the computer password for the server expired on AD and that it was either fixed by rejoining, or by tweaking the password's expiry. Do any AD folk on the list know what we can do to get this stable and that this does not occur again? Any ideas will be very useful. :-) With Regards Stefan Paetow Moonshot Industry & Research Liaison Coordinator t: +44 (0)1235 822 125 Janet, the UK's research and education network. Janet(UK) is a trading name of Jisc Collections and Janet Limited, a not-for-profit company which is registered in England under No. 2881024 and whose Registered Office is at Lumen House, Library Avenue, Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238

2 1

Different behaviour of 2.2.0 and 2.2.6 in handling Post-auth-type reject
by Wiesław Bieniek 31 May '15

31 May '15

Hello, I've used default server configured as follows: post-auth { # my module decides to allow or reject request rtdps2 Post-Auth-Type REJECT { attr_filter.access_reject } } When I run this on 2.2.0 I got debug: Thu Nov 27 14:28:44 2014 : Info: ++[rtdps2] returns reject Thu Nov 27 14:28:44 2014 : Info: Using Post-Auth-Type REJECT Thu Nov 27 14:28:44 2014 : Info: # Executing group from file ../etc/raddb/sites-enabled/default Thu Nov 27 14:28:44 2014 : Info: +- entering group REJECT {...} Thu Nov 27 14:28:44 2014 : Info: [attr_filter.access_reject] expand: %{User-Name} -> testing Thu Nov 27 14:28:44 2014 : Debug: attr_filter: Matched entry DEFAULT at line 11 Thu Nov 27 14:28:44 2014 : Info: ++[attr_filter.access_reject] returns updated Sending Access-Reject of id 80 to 192.168.1.4 port 33304 Cisco-AVPair := "h323-return-code=8" Which is correct, but when I run it in 2.2.6 I got: Thu Nov 27 14:19:35 2014 : Info: ++[rtdps2] = reject Thu Nov 27 14:19:35 2014 : Info: +} # group post-auth = reject Sending Access-Reject of id 186 to 192.168.1.4 port 49975 Service-Type = 0 Framed-Protocol = 0 Cisco-AVPair := "h323-return-code=8" Thu Nov 27 14:19:35 2014 : Info: Finished request 0. Which is wrong, because attributes was not filtered out. Am I missing something ? Is this a bug ? What to do to make version 2.2.6 to work the same way 2.2.0 does ? Regards- *Wiesław Bieniek* <http://www.comarch.pl>

3 14

Fwd: Child is hung (max_request)
by srithar jeevadurai 25 Mar '15

25 Mar '15

Hi Team, We need your help to fix our radius server error. I kindly request you to help us on the same. We are facing 'Child is hung' message in our radius server and we have to restart radius server to become normal. As per our analysis the error message comes whenever there are more load on the server. *Configuration: * max_request_time = 30 cleanup_delay = 5 *max_requests = 12800* *max_queue_size = 131072* start_servers = 5 max_servers = 32 min_spare_servers = 3 max_spare_servers = 10 max_requests_per_server = 0 Our system TPS is 100 (at max 120). Since we have kept max_request as 12,800 and max_request_time as 30 seconds, we will be able to support max backlog 3000 (TPS x max_request_time). That is our system can clear first 3000 requests in the queue before it faces 'time expire' (max_request_time). However we have set max_request as 12,800 during high load, system is facing 'child is hung' when the backlog grows more than 3000. Is our above understanding correct? If it is correct, we can resolve our issue by setting max_request as 3000 i.e. during high load, we will not face 'child is hung ' and no need to restart radius server to become normal. Looking forward for your reply. -- Regards, Srithar Durairaj Alternate Mail I.D: srijeevadurai1(a)yahoo.co.in Mobile: +919886251852

8 32

ipaddr, ipv4addr ipv6addr
by Arran Cudbard-Bell 06 Mar '15

06 Mar '15

The behaviour of the ipaddr config item has changed slightly for 3.0.4. If the ipaddr value contains ':' or '[' or ']', it will be treated as an IPv6 address. If it fails to parse as an IPv6 address the server will refuse to start. If the ipaddr value does not contain any ipv6 chars the server will first check to see if it looks like an ipv4 address. If it does, the server will parse it, if it doesn't and DNS resolution is enabled, it will instead attempt to resolve it. If DNS resolution is not enabled the server will refuse to start. If a matching A record is available it will be used, else if a AAAA record is available else the server will refuse to start. If instead of the ipaddr config item the ipv4addr config item is used the server will check if it looks like an IPv4 address. If it does, the server will parse it, if it doesn't and DNS resolution is enabled, it will instead attempt to resolve it. If DNS resolution is not enabled the server will refuse to start. If a matching A record is available it will be used, else the server will refuse to start. If instead of the ipaddr config item the ipv6addr config item is used the server will check if it looks like an IPv6 address. If it does, the server will parse it, if it doesn't and DNS resolution is enabled, it will instead attempt to resolve it. If DNS resolution is not enabled the server will refuse to start. If a matching AAAA record is available it will be used, else the server will refuse to start. The behaviour is similar for the client, home_server and listen sections. Though those config items in client sections may have an optional /[0-9]{1,3} suffix to map clients to ranges of IP addresses. This should also work with things like example.org/96 though i'm not entirely sure why you'd ever want to do that. 'netmask' is now deprecated but will still function as expected until 3.1.0. These changes should make it slightly easier to manage v4/v6 transitions. Wildcard clients 0.0.0.0 <ipaddr>/0 '*' are not supported. -Arran Arran Cudbard-Bell <a.cudbardb(a)freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

5 15

How to configure FreeRADIUS for Kerberos and LDAP
by Brendan Kearney 27 Jan '15

27 Jan '15

i have put together a doc to assist in the configuration of FreeRADIUS to use Kerberos for authentication (AuthN) and LDAP for authorization (AuthZ). I have modelled the configs after my environment, and taken into account the design and implementations choices i have made. others may have different needs, so some directives or values may need to be changed based on those needs. i make no guarantees that my configs will work in your environment. i have tried to use simple language, but be concise, precise and accurate. if points are ambiguous, lacking clarity or leave room for misinterpretation, please provide constructive feedback. if steps are sub-optimal, incorrect or contain typographical errors, please keep me honest, and indicate where the errors have occurred. i release this doc into the ether and lay no claim to its format, the data contained within it nor to the intellectual property rights of the rightful owners of any trademark, servicemark or copyright. thank you, brendan kearney

2 2

3.0.4: proxy-to-vserver and proxied post-auth?
by Stefan Winter 10 Dec '14

10 Dec '14

Hello, I've migrated almost all my virtual servers - but one - to 3.0.4. There's one thing which I had expected to work, but it doesn't, but I do recall some discussions around this on the list; but not what the final verdict was. My proxied-to vserver needs to do some stuff in post-auth. However it looks like post-auth is not actually called; instead, only the post-auth of the original vserver is. Is that desired/expected behaviour in 3.0.4? The symptoms of this boils down to these two lines: Debug: (55) modsingle[authenticate]: returned from pap (rlm_pap) for request 55 Debug: (55) [pap] = ok Debug: (55) } # Auth-Type PAP = ok Debug: (55) Empty post-proxy section. Using default return values. Debug: (55) Found Auth-Type = Accept Debug: (55) Auth-Type = Accept, accepting the user Debug: (55) # Executing section post-auth from file /usr/local/freeradius/config/raddb/sites-enabled/AAI The PAP instance there is the one from the proxied-to vserver; must be, as it knows my password and the retrieval of that password is unique to the vserver in question. The next line speaks about empty post-proxy; that looks like the initial vserver kicks in right after authenticate { } with its PAP is finished. It then executes post-auth from the initial vserver, not the one from proxied-to (the proxied-to vserver is called "staff", not "AAI"). That's not helpful for my setup :-( So... just wondering if this is a bug or if I'm going to need a majorish rethink of my post-auth logic here... Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 PGP key updated to 4096 Bit RSA - I will encrypt all mails if the recipient's key is known to me http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66

2 3

Re: 4. Freeradius version 2.1.12 with TTLS support (Prasad Jadhav)
by Rui Ribeiro 30 Nov '14

30 Nov '14

Hi Prasad, Do not use 2.1.12, it is old and has known bugs. Install 2.2.6. You are not telling us what protocol you are using to authenticate. For TTLS, you do not need certificates installed on the client side, only for EAP-TLS. However, I what you probably want is really EAP-TTLS; decide what backend are you using to authenticate and elaborate better your next question please. Regards, -- Rui Ribeiro Senior Sysadm ISCTE-IUL https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434 > ------------------------------ > > Message: 4 > Date: Thu, 20 Nov 2014 04:37:33 +0000 > From: Prasad Jadhav <Prasad.Jadhav(a)alepo.com> > To: "freeradius-users(a)lists.freeradius.org" > <freeradius-users(a)lists.freeradius.org> > Subject: Freeradius version 2.1.12 with TTLS support > Message-ID: > < > b223a7693f66454f8160761343be73be(a)BY1PR0801MB0983.namprd08.prod.outlook.com > > > > Content-Type: text/plain; charset="us-ascii" > > Hi, > > I configured the freeradius version 2.1.12 with TTLS support. > > Note: for testing purpose using self signed certificate > > having following question > > 1. do I need to create certificate for per client machine base or per > client username base. > > 2. Which certificates need to install on client side (OS: Windows 8) for > TTLS > > > Regards, > Prasad Jadhav > >

2 2