- Freeradius-Users - lists.freeradius.org

Authentication Source Order
by clay＠milos.co.za 26 Oct '21

26 Oct '21

Hi guys I am trying to do something that seems a bit odd as I can't find it in any searches. Perhaps someone else here has done this before. I have FreeRadius successfully connected and working, serving authentication requests from a Mysql DB. It's running on a pfSense firewall and configured via the GUI but I doubt that makes any difference. I'm authenticating users connecting via a secure network to reach services and would like to change the authentication logic. If the MySQL server is down (yes I know it shouldn't be or I should have redundant servers) I would like the Radius server to always return an Access-Accept. I know this seems counter-intuitive for an authentication service but as I said it's via a secure network allowing users supplementary services that are better to give for free for a limited time than not to give at all in case of a backend outage. My thoughts on doing this were trying to authenticate via SQL first and then falling back to "users" file authentication with a RegExp or DEFAULT user to match a user pattern all users. Is this a good way to do it? From what I've seen, FreeRadius tries to use the users file before trying SQL by default but I changed the sites-enabled/default ordering and that seems to work for (notfound || noop) but not for ( fail ). If I use SQL and then (notfound || noop) then "file" and the user exists in the "users" file it works. DEFAULT user works as well for any user. Where I'm going wrong, I think is that in the sites-enabled/default it accepts the "fail" as a module response code but doesn't act on it when the sql1 fails. I've attached the debug log. redundant sql { sql1 } if ( fail ) { files if (notfound || noop) { reject } } } Thanks in advance! \\Clay

3 3

Re: EAP TTLS Woes
by Doug Wussler 22 Oct '21

22 Oct '21

On October 18, 2021, Alan DeKok wrote: > Arran did some tests a while ago. We have a writeup here: https://urldefense.com/v3/__https://networkradius.com/articles/2021/08/04/w… Just wanted to say thanks for that article. Excellent write-up. I have shared it widely. And thank you also for your work on a draft standard to solve all those issues. Solving that would be big! Doug Wussler Florida State University

2 1

Frame-IP-Address is not assigned in EAP
by kabin mool 19 Oct '21

19 Oct '21

Hello freeradius team, Currently I am doing some experiment for my home setup to assign static IP address using freeradius "Frame-IP-Address" but it is not assigned. Can you let me know how and why it is creating this? Also, in response how to remove all the messages and simple reply with Frame-IP-Address only? Request messages : Received Access-Request Id 0 from 192.168.1.1:49671 to 192.168.1.110:1812 length 199 Tue Oct 19 09:34:19 2021 : Debug: (9) User-Name = "bob" Tue Oct 19 09:34:19 2021 : Debug: (9) NAS-IP-Address = 192.168.1.1 Tue Oct 19 09:34:19 2021 : Debug: (9) Called-Station-Id = "" Tue Oct 19 09:34:19 2021 : Debug: (9) Calling-Station-Id = "XXXXXXXXXXXXXXXX" Tue Oct 19 09:34:19 2021 : Debug: (9) NAS-Identifier = "XXXXXXXXX" Tue Oct 19 09:34:19 2021 : Debug: (9) NAS-Port = 122 Tue Oct 19 09:34:19 2021 : Debug: (9) Framed-MTU = 1400 Tue Oct 19 09:34:19 2021 : Debug: (9) State = 0xd5087246dd016bbc3cccb89e1542d61a Tue Oct 19 09:34:19 2021 : Debug: (9) NAS-Port-Type = Wireless-802.11 Tue Oct 19 09:34:19 2021 : Debug: (9) EAP-Message = 0x0209002e190017030300230000000000000004a462aee4b621fe152e45dfee6d01ababa665d70d651f4101369737 Tue Oct 19 09:34:19 2021 : Debug: (9) Message-Authenticator = 0xf047b70fb44507050a2916afb4482524 Response Message : Sent Access-Accept Id 0 from 192.168.1.110:1812 to 192.168.1.1:49671 length 0 Tue Oct 19 09:34:19 2021 : Debug: (9) MS-MPPE-Recv-Key = 0x73891bd4ad6882551acefc226fb0b3d2fcfc9a66f6e098099b3f1b635daad835 Tue Oct 19 09:34:19 2021 : Debug: (9) MS-MPPE-Send-Key = 0x9eea9b7294f8d12d70bce316148439b65cca6050774f58b0064571c6302691e4 Tue Oct 19 09:34:19 2021 : Debug: (9) EAP-Message = 0x03090004 Tue Oct 19 09:34:19 2021 : Debug: (9) Message-Authenticator = 0x00000000000000000000000000000000 Tue Oct 19 09:34:19 2021 : Debug: (9) User-Name = "bob" Tue Oct 19 09:34:19 2021 : Debug: (9) Framed-IP-Address = 192.168.1.240 Tue Oct 19 09:34:19 2021 : Debug: (9) Finished request Kabin

2 2

Unlag coding
by mohamed almeshal 19 Oct '21

19 Oct '21

dear Savers ... I'm doing some coding inside freeradius core files , where I can find guideline and coding tips finally if I need some one from network radius to verify my coding how much I will pay ???. Thanks , Mohammed

2 1

FW: EAP TTLS woes
by adrian.p.smith＠bt.com 18 Oct '21

18 Oct '21

>> >> I am testing EAP TTLS with Android and finding some mixed results. >> >> Using identical WifiConfig on the devices I see an error on some: >> ... >> Thu Sep 23 15:01:12 2021 : Debug: (4813) eap_ttls: <<< recv TLS 1.1 >> [length 0002] Thu Sep 23 15:01:12 2021 : ERROR: (4813) eap_ttls: TLS >> Alert read:fatal:internal error > Hmm... useful errors. :( > TBH I'd suggest using the head of v3.0.x from git, or the packages at .... > You're running 3.0.21 or earlier, and 3.0.22 added a lot more TLS debugging messages. So it's much easier to tell what's going on. > Right now, all we know is that it's "magic OpenSSL stuff". > Alan DeKok. Thanks Alan - in the process of building 3.0.23 for our machine.

3 9

Re: Having trouble with "passwd" authentication
by Darcy Boese 15 Oct '21

15 Oct '21

> Both of these will mean you need to update your passwd config to use > 'Stripped-User-Name' instead of 'User-Name'. That was it! Editing "mods-enabled/passwd" to use "Stripped-User-Name" in the place of just "User-Name" did exactly what I needed here. And yes, in this particular circumstance, all I need is that the username and password match regardless of the domain. I do have to say I miss the relative simplicity and utility of the deprecated "unix", whereby users could have different permissions based on their unix group's name, but I don't think I'm going to get very far attempting that with 3.0, especially not when I'm trying to validate information against copies in /etc/radius/passwd /etc/radius/shadow /etc/radius/group instead of the system's own.

1 0

Having trouble with "passwd" authentication
by Darcy Boese 15 Oct '21

15 Oct '21

I've got an old freeradius server that's been plugging along for a long time. It pulls in the files /etc/passwd /etc/shadow and /etc/group from an external server, all copied into an /etc/radius/ folder, and authenticates pppoe sessions. I don't need help with this old server, but I need to replicate its functionality at a new location. So I have installed a completely fresh freeradius 3.0 server, and after a lot of tinkering and quite a bit of hair-pulling, I managed to get it into a state where it will authenticate usernames and passwords against the /etc/radius/shadow file. To get that far, I'd modified the "mods-enabled/passwd" to read: passwd shadow { filename = /etc/radius/shadow format = "*User-Name:Crypt-Password:" hash_size = 100 ignore_nislike = no allow_multiple_keys = no } and in the "sites-available/default" file where it listed "unix" (approx line 400 in the "authorize" section) I listed "shadow" instead. Easy peasy, so to speak. But there's still one major hitch that I cannot seem to get straight. Getting authentication to work when the username has an attached "realm" is failing, and I'm utterly boggled for now as to where or what I need to change, because it's totally different from the old but still-plugging-along server. So this works: radtest <username> <password> localhost 5000 testing123 but this fails: radtest <username@domain> <password> localhost 5000 testing123 As far as I can gather, there's no "nostrip" option enabled anywhere, yet the realm isn't being stripped before being matched via the passwd module. Help please?

3 2

Backporting TLS fixes to Fedora and RHEL
by Antonio Torres 15 Oct '21

15 Oct '21

Hello everyone, I'm the maintainer for FreeRADIUS in RHEL and Fedora. We have found an issue when using FreeRADIUS 3.0.21 and OpenSSL 3.0. Running eapol_test with the attached config (EAP-TTLS-TLS) fails with the following errors (logs attached): (9) eap_ttls: ERROR: Invalid ACK received: 256 (9) eap_ttls: ERROR: [eaptls verify] = invalid (9) eap_ttls: ERROR: [eaptls process] = invalid (9) eap: ERROR: Failed continuing EAP TTLS (21) session. EAP sub-module failed Tried updating to 3.0.23 and the issue seems to be fixed. However due to the updates policy we can't do a full upgrade, so we have to backport fixes to 3.0.21. I am having issues finding the commit(s) that fix this issue, so any help would be appreciated. I'm not sure this is related, but we are hitting an error with the same error message as this one but using MSCHAPv2. Here's the report: https://bugzilla.redhat.com/show_bug.cgi?id=2014525 This is still valid in the latest FreeRADIUS release (3.0.25). Thank you!

4 7

Work with clear password , but not with MD5 ( but both work with radtest)
by webmaster＠techshop-lille.fr 14 Oct '21

14 Oct '21

Hello ! I'm using Freeradius 2.1.12 with mysql Backend and a Ubiquity/Unify network for authenticating my wireless users Actually it work fine with users in Sql DB with User-Password := value Off course i wanted to change it for a MD5 version So i changed User-Password with MD5-Password Radtest is working fine , with both users using the MD5 and Clear Text password , replying me with auth and VLAN ID but when i try to authenticate with real world Wireless users , only the users with clear text password are working the test users with MD5 password only work with radtest I've parsed the log , and here is what seem to be different from real world vs radtest : -------------------- [pap] Normalizing MD5-Password from hex encoding [pap] WARNING: Auth-Type already set. Not setting to PAP ++[pap] returns noop Found Auth-Type = EAP # Executing group from file /etc/freeradius/sites-enabled/inner-tunnel +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/mschapv2 [eap] processing type mschapv2 [mschapv2] # Executing group from file /etc/freeradius/sites-enabled/inner-tunnel [mschapv2] +- entering group MS-CHAP {...} [mschap] No Cleartext-Password configured. Cannot create LM-Password. [mschap] No Cleartext-Password configured. Cannot create NT-Password. [mschap] Creating challenge hash with username: stephaneb [mschap] Told to do MS-CHAPv2 for stephaneb with NT-Password [mschap] FAILED: No NT/LM-Password. Cannot perform authentication. [mschap] FAILED: MS-CHAP2-Response is incorrect ++[mschap] returns reject [eap] Freeing handler ++[eap] returns reject Failed to authenticate the user. ----------------------------- Can you help me ? thanks a lot !

3 2

OpenLDAP module fails to load
by Antonio Torres 13 Oct '21

13 Oct '21

Hello everyone, I am the maintainer of the FreeRADIUS package for Fedora and RHEL. We are currently trying to fix this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1983063 Apparently, it appears since this OpenLDAP commit, related to the TLS connection start: https://git.openldap.org/openldap/openldap/-/commit/735e1ab14 If we build the OpenLDAP package without the LDAP_USE_NON_BLOCKING_TLS flag, the issue disappears, so it is probably related to the async connection. I've seen there has been some work on the async LDAP connection process, but I'm not entirely sure whether it is related, and it is only in v4: https://github.com/FreeRADIUS/freeradius-server/pull/4240 I'm wondering whether FreeRADIUS needs to adapt to these changes or the issue is entirely on the OpenLDAP side. What do you think? Thank you!

2 4