Re: User login restrictions based on SSID
Hi Alan De & Alan Buxey, There is some confusion going on here. I have already attached freeradius -X output (as text file) in my first mail itself, to which Alan De replied "If only there was some kind of debug log, where you could see what the server was doing". I assumed he already gone thru the attachment and want to see the radius.log. Thus i have posted contents of radius.log If you want me to send the freeradius -X output again, i'll post it here. I understand you guys are busy with other activities and I appreciate your involvement here on the mailing list. cheers, Eby -------------------------------------------- On Wed, 25/5/16, A.L.M.Buxey@lboro.ac.uk <A.L.M.Buxey@lboro.ac.uk> wrote: Subject: Re: User login restrictions based on SSID To: "Eby Mani" <eby_km@yahoo.com> Cc: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Date: Wednesday, 25 May, 2016, 2:51 PM Hi,
If the SQL can't connect, how authentication work as user details are stored in db?. I was able to login thru Radius and i have not enabled Radius caching of anysort on my WLAN controller.
well, it cant. but if you read the output, you'll see it has connected this time. i guess your SQL wasnt running last time..... just read the output!
Following is today's radius.log, there isn't much info, is there a command to log more info regarding this ?.
run in debug mode, not just as a service radiusd -X or freeradius -X on debian/ubuntu package builds.
Wed May 25 14:54:09 2016 : Auth: Login incorrect: [sales/<via Auth-Type = EAP>] (from client aruba port 0 via TLS tunnel) Wed May 25 14:54:09 2016 : Auth: Login incorrect: [sales/<via Auth-Type = EAP>] (from client aruba port 0 cli 38192fb2eb02)
in full debug mode you'd see why this failed.
Wed May 25 16:00:08 2016 : Auth: Login OK: [eby] (from client aruba port 0 via TLS tunnel)
Wed May 25 16:00:08 2016 : Auth: Login OK: [eby] (from client aruba port 0 cli e02a82e1afbf)
and that worked alan
If you want me to send the freeradius -X output again, i'll post it here. I understand you guys are busy with other activities and I appreciate your involvement here on the mailing list.
They are telling you to *READ* the freeradius -X output because it is *very* likely to tell you what the problem is.
run in debug mode, not just as a service
radiusd -X
or freeradius -X on debian/ubuntu package builds.
See above.
Wed May 25 14:54:09 2016 : Auth: Login incorrect: [sales/<via Auth-Type = EAP>] (from client aruba port 0 cli 38192fb2eb02)
Run FreeRADIUS in debug mode (as user 'radiusd' or 'freerad' depending on your distribution). Then wait for this authentication to occur again (or trigger it).
Wed May 25 16:00:08 2016 : Auth: Login OK: [eby] (from client aruba port 0 via TLS tunnel)
Wed May 25 16:00:08 2016 : Auth: Login OK: [eby] (from client aruba port 0 cli e02a82e1afbf)
Ditto. Trigger this auth as well. See what the problem is. The earlier error I saw was MySQL-related... I.e. The server was either not running or available. When that happens, obviously you won't be able to auth. But as the above auth shows (for 'eby'), that worked, so your server became available or was started between 14:54:09 and 16:00:08. Stefan Paetow Moonshot Industry & Research Liaison Coordinator t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: stefanp@jabber.dev.ja.net skype: stefan.paetow.janet jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc¹s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
Hi,
There is some confusion going on here. I have already attached freeradius -X output (as text file) in my first mail itself, to which Alan De replied "If only there was some kind of debug log, where you could see what the server was doing".
you obviously didnt pick up the sarcasm.... 'you have a log file...read it...it contains text that says exactly why its not working' alan
On May 25, 2016, at 11:20 AM, Eby Mani via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
There is some confusion going on here. I have already attached freeradius -X output (as text file) in my first mail itself, to which Alan De replied "If only there was some kind of debug log, where you could see what the server was doing". I assumed he already gone thru the attachment and want to see the radius.log. Thus i have posted contents of radius.log
If you want me to send the freeradius -X output again, i'll post it here. I understand you guys are busy with other activities and I appreciate your involvement here on the mailing list.
I will make this very clear. If you won't read the debug output, then we won't read it, either. We are not here to do all of your work for you. You need to *read* the debug output. Alan DeKok.
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Eby Mani -
Stefan Paetow