OK - problem fixed. For all the clueless like me out there I suspect the problem was: 1) Radiusd needs to be restarted if you change the users file ? What this will show up is if there are any problems in the users file. I am not sure if this is the recommended approach as it is not mentioned anywhere in the troubleshooting or the testing notes. 2) What it did show up when restarting was two issues: A spelling mistake in my Cleartext statement, and it appears as if "tab" must be used and not "space". Again could not find anything in the troubleshooting or other getting started guides so not sure if this is the case. It certainly fixed my problem. If the above are indeed requirements - can they be added to the section for beginners please and hopefully save hours and hours of trying to get something we are unfamiliar with working.? ------------------------------------------ Alan, Thanks for this. I had slavishly followed the testing instructions you refer to. I had uncommented the "bob" user and added in the "testing" user at the top of the users file. I had monitored the testing using -X. I had also pasted in the debugging system with no intelligible response (from my layman perspective). From the debug both the following were received by freeRadius so no issues with firewall or corruption experienced by other. "(9) User-Name = 'bob' (9) User-Password = 'hello'" And (10) User-Name = 'testing' (10) User-Password = 'password' I have now reread the technical guide. Other than a knowledge of freeradius what am I missing ? Your comment: "So... how should the server authenticate a user if it doesn't know (a) who the user is, and (b) what the correct password is for that user?" is valid. I had added these users in the user file and am asking for a hint as to why they are not been seen by freeradius. I have attached the config file and pasted in the bits of interest below. "testing Cleartest-Password := "password" # # Configuration file for the rlm_files module." And bob Cleartext-Password := "hello" Reply-Message := "Hello, %{User-Name}" I am sure it is something so obvious that it is possibly not in the how-to ? -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: Friday, 10 July 2015 12:14 AM To: ross@convergingtrails.com; FreeRadius users mailing list Subject: Re: no-auth type error On Jul 9, 2015, at 7:57 AM, Ross c6 <ross@convergingtrails.com> wrote:
I am sure it is simple. I did do some research and one of the posts was about some of the auth modules not starting. Any suggestions ?
Read the debug output you posted here?
(10) WARNING: pap : No "known good" password found for the user. Not setting Auth-Type
(10) WARNING: pap : Authentication will fail unless a "known good" password is available
So... how should the server authenticate a user if it doesn't know (a) who the user is, and (b) what the correct password is for that user? This is documented: http://freeradius.org/doc/getting_started.html Alan DeKok.
On Jul 9, 2015, at 8:07 PM, Ross c6 <ross@convergingtrails.com> wrote:
OK - problem fixed. For all the clueless like me out there I suspect the problem was:
1) Radiusd needs to be restarted if you change the users file ? What this will show up is if there are any problems in the users file. I am not sure if this is the recommended approach as it is not mentioned anywhere in the troubleshooting or the testing notes.
It's in the documentation. And it's also the standard Unix practice. Configuration files are loaded on start, or re-loaded on HUP. Nothing else.
2) What it did show up when restarting was two issues: A spelling mistake in my Cleartext statement, and it appears as if "tab" must be used and not "space". Again could not find anything in the troubleshooting or other getting started guides so not sure if this is the case. It certainly fixed my problem.
It's in the "man" page for the "users" file.
If the above are indeed requirements - can they be added to the section for beginners please and hopefully save hours and hours of trying to get something we are unfamiliar with working.?
We can add more documentation. But at some point, I have to question the value of re-documenting things which are already extensively documented. Alan DeKok.
participants (2)
-
Alan DeKok -
Ross c6