MSCHAP not working after weekly restart
Hello everyone, we have a ubuntu 14.04 with freeradius 2.1.12+dfsg-1.2ubuntu8.1 configured to use Active Directory to do authentication (using winbind and ntlm_auth), eap, pap and mschap. Weekly the freeradius is restarted (with a signal HUP) by logrotate and usually it works fine. But sometimes MSCHAP authentication stop working after the restart (both plain with radtest and with PEAP from wireless client) while PAP continues working. We can detect the problem running `radtest -t pap ...` (it works) and `radtest -t mschap ...` (it doesn't). The response we get is:
rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=204, length=38 MS-CHAP-Error = "\000E=691 R=1"
and the log says:
Login incorrect (mschap: External script says )
Restarting the freeradius solves the problem (with service freeradius restart). I'm unable to reproduce it (it just happens sometimes, like once every two months) and I can't get a debug log with `freeradius -X` because restarting solves the problem. I've been able to log the parameters passed to the external program ntlm_auth that are:
--request-nt-key --username=someuser --challenge=00 --nt-response=00 --domain=OUR_DOMAIN
the configuration is:
ntlm_auth = "/usr/bin/ntlm_auth --request-nt-key --username=%{reply:AD-Samaccountname} --challenge=%{%{mschap:Challenge}:-00} --nt-response=%{%{mschap:NT-Response}:-00} --domain=OUR_DOMAIN"
so I think that for some reason the mschap module brokes down and stops putting the right values in the dictionary. I noticed that this (for now) happened only with weekly logrotate restarts and not with manual restarts (when I update the configuration). Another thing I noticed is that it happens only at the primary radius server (~500k authentications every week, some local and some proxied) and not on the secondary (~40k authentications every week, basically just monitoring). The two radius server share the same configuration (as in "I copied the files") and software version. Any hint in how to debug it? (or resolve it) Thanks for reading my mail and for any help you could provide. Regards, Enrico Polesel
On Jun 12, 2016, at 7:30 AM, Enrico Polesel <polesel@poisson.phc.unipi.it> wrote:
we have a ubuntu 14.04 with freeradius 2.1.12+dfsg-1.2ubuntu8.
That's many years out of date. I really wish that Ubuntu would use a recent version of the server.
We can detect the problem running `radtest -t pap ...` (it works) and `radtest -t mschap ...` (it doesn't). The response we get is:
rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=204, length=38 MS-CHAP-Error = "\000E=691 R=1"
and the log says:
Login incorrect (mschap: External script says )
Upgrade to 2.2.9.
Any hint in how to debug it? (or resolve it)
We're not going to debug issues that were found and fixed 5 years ago. Upgrade to 2.2.9, and the problem will be fixed. Alan DeKok.
Thank you for reply On Sun, Jun 12, 2016 at 09:13:38AM -0400, Alan DeKok wrote:
That's many years out of date. I really wish that Ubuntu would use a recent version of the server.
Yes I know, unfortunately is what we have now.
Upgrade to 2.2.9.
I'll try to upgrade ubuntu to 16.04 to get freeradius 2.2.8+dfsg-0.1build2. It's not 2.2.9 but usually (at least for other software) ubuntu maintainers backport bug patches.
We're not going to debug issues that were found and fixed 5 years ago. Yes, of course. I just hoped there was a known solution.
Upgrade to 2.2.9, and the problem will be fixed.
Thank you again for your help. Regards, Enrico Polesel
On Jun 12, 2016, at 9:55 AM, Enrico Polesel <polesel@poisson.phc.unipi.it> wrote:
I'll try to upgrade ubuntu to 16.04 to get freeradius 2.2.8+dfsg-0.1build2. It's not 2.2.9 but usually (at least for other software) ubuntu maintainers backport bug patches.
You can build 2.2.9 on Ubuntu 14.04. See wiki.freeradius.org. It's not difficult. Alan DeKok.
participants (2)
-
Alan DeKok -
Enrico Polesel