On Tue, Aug 14, 2007 at 01:24:15AM -0500, Scott Lambert wrote:
On Mon, Aug 13, 2007 at 11:48:06PM -0500, Scott Lambert wrote:
The failure happens in rlm_pap when the user does not specify a realm. I don't see the cause of the failure in the debug output. I'm probably not interpreting the output correctly. <snip> Here are the authentication tests.
lambert@sysmon ~ 22:30:33 Mon Aug 13 $ radtest lambert@example3.net password1 radtest.example1.net 2 blahblah 2 Sending Access-Request of id 82 to radtest.example1.net port 1645 User-Name = "lambert@example3.net" User-Password = "password1" NAS-IP-Address = 255.255.255.255 NAS-Port = 2 Framed-Protocol = PPP rad_recv: Access-Accept packet from host radtest.example1.net:1645, id=82, length=32 Framed-Protocol = PPP Framed-Compression = Van-Jacobson-TCP-IP
lambert@sysmon ~ 22:33:43 Mon Aug 13 $ radtest lambert password1 radtest.example1.net 2 blahblah 2 Sending Access-Request of id 99 to radtest.example1.net port 1645 User-Name = "lambert" User-Password = "password1" NAS-IP-Address = 255.255.255.255 NAS-Port = 2 Framed-Protocol = PPP rad_recv: Access-Reject packet from host radtest.example1.net:1645, id=99, length=20
One of they guys at work suggested that it might be because I have an account on the machine. He was right. I disabled the unix module in the authentication section now all users work correctly. This unlang stuff is great! -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org