Hello Christian,
what you can do is to run radius in debug mode:
raddebug -r /usr/local/pf/var/run/radiusd.sock > /root/radius.debug
Then try the bogus AP and try with another one and check the debug and
search for the line where freeradius call ntlm_auth and see if the
output is the same. (chrooted_mschap: Executing: /usr/bin/sudo
/usr/sbin/chroot /chroots/...)
Regards
Fabrice
Le 19-02-19 à 11 h 46, Christian McDonald via PacketFence-users a écrit :
Greetings,
I have one access point that keeps rejecting clients with:
chrooted_mschap: Program returned code (1) and output 'The attempted
logon is invalid. This is either due to a bad username or
authentication information. (0xc000006d)'
However, the same client on a different AP with the same credentials
works fine.
All APs are members of the same "switch" group and have identical
configuration both in PacketFence and my controller (UniFi)
--
*R. Christian McDonald *
M: (616) 856-9291
E: [email protected] <mailto:[email protected]>
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
