Thanks Alan. I will do that. the users seem to be consistent, meaning, if user fails, they always fail.. and for many, I did confirm in historic log, they used to succeed.. Also, my 3.0.8 is in docker container, on redhat 6, while 3.0.9 on redhat 7, no docker. To be user, I just removed 3.0.9 from one redhat 7 VM, and installed 3.0.8. and managed to reproduce the issue: user axa3 fails on 3.0.9, I disable that instance, axa3 tries again, this time goes to 3.0.8 and is accepted. I will send you full debug of both sessions off list. Thanks a lot, Mohamed, On Sun, Jul 26, 2015 at 7:50 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Jul 26, 2015, at 7:44 AM, Mohamed Lrhazi <Mohamed.Lrhazi@georgetown.edu> wrote:
I am now pretty confident my 3.0.9 config is the same as 3.0.8.. but the issue is still happening. A user is accepted on 3.0.8, but rejected on 3.0.9 with the error:
Is it only a few users? Or is it random?
To make it harder to debug, not all users are failing to authenticate on 3.0.9... just some! I assume the issue is with the config and the supplicants... but how can I track this down?
Send me a PCAP file of the RADIUS traffic, off-list. I may be able to reproduce it from that.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html