freeradius 2.1.12 - EAP Trouble - files is used with LEAP, not PEAP, and AD/mschap is used with PEAP, not LEAP
# freeradius -v freeradius: FreeRADIUS Version 2.1.12, for host x86_64-pc-linux-gnu, built on Feb 24 2014 at 14:57:57 Copyright (C) 1999-2011 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. /etc/freeradius/files contains: *testuser Cleartext-Password := "password"* # radexample with user "testuser" and password "password" - as it exists in /etc/freeradius/users works: # radexample login: testuser Password: password "testuser" RADIUS Authentication OK (log01.txt) but # ./rad_eap_test -H 10.160.4.50 -P 1812 -S testing123 -u testuser -p password -m IEEE8021X -e PEAP -2 MSCHAPV2 -v access-reject; 1 fails (log02.txt), but I wanted to have it handled by "files". but with LEAP it works: # ./rad_eap_test -H 10.160.4.50 -P 1812 -S testing123 -u testuser -p password -m IEEE8021X -e LEAP -2 MSCHAPV2 -v access-accept; 0 RADIUS message: code=2 (Access-Accept) identifier=3 length=149 Attribute 26 (Vendor-Specific) length=59 Value: 00 00 00 09 01 35 6c 65 61 70 3a 73 65 73 73 69 6f 6e 2d 6b 65 79 3d 82 68 87 56 16 2a 3d 5a 79 ae c4 db ee d3 2c db 38 83 9a 9f 81 a7 70 03 55 00 c4 b1 cb 45 78 ea ce 63 Attribute 79 (EAP-Message) length=42 Value: 02 04 00 28 11 01 00 18 24 16 99 a0 97 e6 72 86 eb 2d 2e 97 5a ef 9c c7 e2 00 cf b4 95 8a fa 42 74 65 73 74 75 73 65 72 Attribute 80 (Message-Authenticator) length=18 Value: e2 d3 98 f4 75 a9 44 6b 04 e2 d8 ef 6b 54 4f b1 Attribute 1 (User-Name) length=10 Value: 'testuser' (log03.txt). And - with AD User, LEAP does not work # ./rad_eap_test -H 10.160.4.50 -P 1812 -S testing123 -u wlan_test -p test -m IEEE8021X -e LEAP -2 MSCHAPV2 -v access-reject; 1 (log04.txt) while with AD User PEAP is working: # ./rad_eap_test -H 10.160.4.50 -P 1812 -S testing123 -u wlan_test -p test -m IEEE8021X -e PEAP -2 MSCHAPV2 -v access-accept; 0 RADIUS message: code=2 (Access-Accept) identifier=9 length=171 Attribute 26 (Vendor-Specific) length=58 Value: 00 00 01 37 11 34 81 3f 5f f6 c1 df a3 6f 6e bc 39 89 09 c8 5f da bd a7 e4 86 45 0e a9 b7 b1 e9 0d 88 1a 4c 15 d7 9a 8a db 25 87 bd 4f b2 33 11 e6 b2 0b 68 b1 c6 7f 91 Attribute 26 (Vendor-Specific) length=58 Value: 00 00 01 37 10 34 89 ca ed f6 a0 75 fc 03 b8 91 24 91 ab a0 ba ae 25 72 b0 66 6d b0 69 b0 72 43 83 61 c2 30 fc 4c 62 9f 44 5c 23 00 c3 1b 40 d3 cf 12 3c 55 4d dd 4a 93 Attribute 79 (EAP-Message) length=6 Value: 03 09 00 04 Attribute 80 (Message-Authenticator) length=18 Value: e9 5f 92 1a 6f 01 26 29 b2 b3 9c 87 61 e8 e3 ca Attribute 1 (User-Name) length=11 Value: 'wlan_test' What is wrong here? I want to handle first files, then mschap/ntlm_auth Authentication. Any help is appreciated. Thomas
On Sun, Jul 26, 2015 at 03:40:46PM +0200, freerad wrote:
freeradius: FreeRADIUS Version 2.1.12, for host x86_64-pc-linux-gnu, built
Ancient. You should upgrade.
*testuser Cleartext-Password := "password"* ...
What is wrong here? I want to handle first files, then mschap/ntlm_auth Authentication.
See modules/mschap: testuser Cleartext-Password := "password", MS-CHAP-Use-NTLM-Auth := No Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
2015-07-26 16:28 GMT+02:00 Matthew Newton <mcn4@leicester.ac.uk>:
testuser Cleartext-Password := "password", MS-CHAP-Use-NTLM-Auth := No
Cool. this did the trick :) But for LEAP I still get the reject for the AD User: ./rad_eap_test -H 10.160.4.50 -P 1812 -S testing123 -u wlan_test -p test -m IEEE8021X -e LEAP -2 MSCHAPV2 -i tiritest -v access-reject; 1 Radius Debug tells: [eap] processing type leap rlm_eap_leap: No Cleartext-Password or NT-Password configured for this user [eap] Handler failed in EAP/leap Full Log attached (log07.txt) Best regards, Thomas.
Hi, why LEAP? do you have a valid, real reason for using that broken protocol? your server is not going into inner-tunnel to authenticate the user... which is interesting so its broken somehow ...and it looks like you are trying to install this new.... so upgrade - you should be using version 3 alan
No, I have no reason for LEAP, just to have it handled correctly. But interesting, as innertunnel is not taken into account, where is the error in configuration? When migrating / setting up freerad 3, is there a good document to upgrade ? Best regards, Thomas. 2015-07-27 9:56 GMT+02:00 <A.L.M.Buxey@lboro.ac.uk>:
Hi,
why LEAP? do you have a valid, real reason for using that broken protocol?
your server is not going into inner-tunnel to authenticate the user... which is interesting so its broken somehow
...and it looks like you are trying to install this new.... so upgrade - you should be using version 3
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
When migrating / setting up freerad 3, is there a good document to upgrade ?
you starty from scratch...so its much like FR2 - the main difference is that some of the files ahve changed location/name and that some of the modules have new functions and connection options - so most documents work okay and you just need to read the README.rst file which covers all the new changes/features. alan
participants (3)
-
A.L.M.Buxey@lboro.ac.uk -
freerad -
Matthew Newton