ERROR: User-Name ... is not the same as MS-CHAP Name
Hi All, FreeRADIUS version 2.1.12 (2.1.12+dfsg-1.2ubuntu8.1) Ubuntu 14.04.3 LTS OpenLDAP 2.4.31 Goal is to use existing sambaLMPassword/sambaNTPassword/sambaEtc. in OpenLDAP server data, to authenticate wireless clients--mostly running MS-Win7. Some MS-WinXP. A few Linux clients. Old version was FreeRADIUS 1.1.1, built from a tarball, running on a Sun Sparc Solaris box, working against an older version of OpenLDAP and Samba. Worked like a champ. Still working. Referring to various on-line "how to"s and my old configs: Got the new server kind of more-or-less running, the trick being in finding.. filter = "(uid=%{mschap:User-Name})" to get clients authenticating via ldap. Then ran into the dreaded Info: [mschap] ERROR: User-Name (hostname\username) is not the same as MS-CHAP Name (username) from EAP-MSCHAPv2 Realms is not possible, because these are all workgroup computers--not part of a domain. So they all send "HOSTNAME\\username", rather than just "username." I can auth with a Linux Mint client, no problem. Searching and searching: I finally ran across a Red Hat bug report thread where RH claimed "It's a bug, it's been patched" and they closed it. So: *Was* it a bug and *has* it been squashed? I have no problem building and installing from a tarball, *if* it will fix the problem. Thanks, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>.
On Oct 1, 2015, at 8:25 PM, Jim Seymour <jseymour@LinxNet.com> wrote:
FreeRADIUS version 2.1.12 (2.1.12+dfsg-1.2ubuntu8.1)
That's 5 years old.
... Then ran into the dreaded
Info: [mschap] ERROR: User-Name (hostname\username) is not the same as MS-CHAP Name (username) from EAP-MSCHAPv2
Upgrade to 2.2.9, which was released this week.
Searching and searching: I finally ran across a Red Hat bug report thread where RH claimed "It's a bug, it's been patched" and they closed it.
So: *Was* it a bug and *has* it been squashed? I have no problem building and installing from a tarball, *if* it will fix the problem.
Yes. Alan DeKok.
On Fri, Oct 2, 2015 at 8:31 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Oct 1, 2015, at 8:25 PM, Jim Seymour <jseymour@LinxNet.com> wrote:
FreeRADIUS version 2.1.12 (2.1.12+dfsg-1.2ubuntu8.1)
Upgrade to 2.2.9, which was released this week.
So: *Was* it a bug and *has* it been squashed? I have no problem building and installing from a tarball, *if* it will fix the problem.
Yes.
@Jim: Is this a new installation intended to replace your old 1.x setup? 2.2.x is EoL, and will only get security fixes in the future. While it makes much sense to stick with 2.x on established systems, you should probably jump straight to 3.0.x (use latest 3.0.x branch from git, or wait a few days until 3.0.10 is released) for new installation. Having said that, see https://launchpad.net/~freeradius/+archive/ubuntu/stable if you want to use 2.2.9 anyway. Might save you some time and effort. -- Fajar
On Fri, 2 Oct 2015 15:18:17 +0700 "Fajar A. Nugraha" <list@fajar.net> wrote: [snip]
@Jim: Is this a new installation intended to replace your old 1.x setup?
It's a new server installation, all of which is replacing the old server: Yes.
2.2.x is EoL, and will only get security fixes in the future. While it makes much sense to stick with 2.x on established systems, you should probably jump straight to 3.0.x (use latest 3.0.x branch from git, or wait a few days until 3.0.10 is released) for new installation.
Assuming 2.2.9 is config-file-compatible with 2.1.12, I'd be inclined to stick with that. I spent a *lot* of time getting done what I've already gotten done. I really, really don't want to go through that all over again.
Having said that, see https://launchpad.net/~freeradius/+archive/ubuntu/stable if you want to use 2.2.9 anyway. Might save you some time and effort.
It will! Thanks! I believe that's the way I'll go. 14.04 LTS is supposed to be supported until Apr. 2019, so I'm inclined to stick with packages to the extent possible. Just getting off an old, long-EOL'd Sun Sparc Solaris system upon which I was *obliged* to build & install from tarballs all the time. Looking to leave that behind to the extent possible. Do I understand correctly that if I install from that PPA, installing "over the top of" the existing install, and choosing to retain my existing radiusd.conf, that all future updates will come from that PPA, rather than the official Ubuntu 14.04 repos? Thanks, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>.
On Oct 2, 2015, at 8:33 AM, Jim Seymour <jseymour@LinxNet.com> wrote:
Assuming 2.2.9 is config-file-compatible with 2.1.12,
The documentation that comes with 2.2.9 says it is.
I'd be inclined to stick with that. I spent a *lot* of time getting done what I've already gotten done. I really, really don't want to go through that all over again.
Upgrading to 3.0 isn't hard. There's even a README which tells you what's changed. It's not a lot.
I believe that's the way I'll go. 14.04 LTS is supposed to be supported until Apr. 2019, so I'm inclined to stick with packages to the extent possible.
Except for the packages that are 5 years old. Which is terrible... Alan DeKok.
Hi,
On Oct 2, 2015, at 8:33 AM, Jim Seymour <jseymour@LinxNet.com> wrote:
Assuming 2.2.9 is config-file-compatible with 2.1.12,
The documentation that comes with 2.2.9 says it is.
theres just one, very obscure setting that is not compatible. i've never seen anyone use that option and its not there by default. alan
It's unfortunate that the stock Ubuntu freeradius packages are so out of date even on the latest (Wily) they're only up to 2.1.12. Ref: http://packages.ubuntu.com/search?keywords=freeradius&searchon=names&suite=a... We switched to the repo at http://packages.networkradius.com/ for 14.04 LTS (Trusty) Hopefully in the future the Ubuntu package maintainers can get their act together and ensure the next LTS has the supported & stable version included as stock. On Fri, Oct 2, 2015 at 5:33 AM, Jim Seymour <jseymour@linxnet.com> wrote:
On Fri, 2 Oct 2015 15:18:17 +0700 "Fajar A. Nugraha" <list@fajar.net> wrote:
[snip]
@Jim: Is this a new installation intended to replace your old 1.x setup?
It's a new server installation, all of which is replacing the old server: Yes.
2.2.x is EoL, and will only get security fixes in the future. While it makes much sense to stick with 2.x on established systems, you should probably jump straight to 3.0.x (use latest 3.0.x branch from git, or wait a few days until 3.0.10 is released) for new installation.
Assuming 2.2.9 is config-file-compatible with 2.1.12, I'd be inclined to stick with that. I spent a *lot* of time getting done what I've already gotten done. I really, really don't want to go through that all over again.
Having said that, see https://launchpad.net/~freeradius/+archive/ubuntu/stable if you want to use 2.2.9 anyway. Might save you some time and effort.
It will! Thanks!
I believe that's the way I'll go. 14.04 LTS is supposed to be supported until Apr. 2019, so I'm inclined to stick with packages to the extent possible.
Just getting off an old, long-EOL'd Sun Sparc Solaris system upon which I was *obliged* to build & install from tarballs all the time. Looking to leave that behind to the extent possible.
Do I understand correctly that if I install from that PPA, installing "over the top of" the existing install, and choosing to retain my existing radiusd.conf, that all future updates will come from that PPA, rather than the official Ubuntu 14.04 repos?
Thanks, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Mark Foster - mdf@extrahop.com Sr. IT Systems Engineer - ExtraHop Networks 206-787-8401 -or- 877-333-9872 x306 [image: http://goto.extrahop.com/sig_target] <http://goto.extrahop.com/sig_target>
On Fri, Oct 2, 2015 at 7:33 PM, Jim Seymour <jseymour@linxnet.com> wrote:
Do I understand correctly that if I install from that PPA, installing "over the top of" the existing install, and choosing to retain my existing radiusd.conf, that all future updates will come from that PPA, rather than the official Ubuntu 14.04 repos?
All package sources have the same priority in ubuntu/debian by default. So you'll get whichever source provides newest version. Since it's highly unlikely that trusty will get a version bump during its lifetime, you'll end up with whatever version is on that PPA. And since 2.2.x is EOLed, 2.2.9 will most likely be the last version available. If you're concerned about updates, go with 3.0.x. -- Fajar
On Thu, 1 Oct 2015 21:31:24 -0400 Alan DeKok <aland@deployingradius.com> wrote:
On Oct 1, 2015, at 8:25 PM, Jim Seymour <jseymour@LinxNet.com> wrote:
FreeRADIUS version 2.1.12 (2.1.12+dfsg-1.2ubuntu8.1)
That's 5 years old.
Yikes! I did not realize that. Jeez, Ubuntu 14.04 LTS was released only early last year, and 14.04.3 on Aug. 6 of this year.
... Then ran into the dreaded
Info: [mschap] ERROR: User-Name (hostname\username) is not the same as MS-CHAP Name (username) from EAP-MSCHAPv2
Upgrade to 2.2.9, which was released this week.
Very well. Thanks!
Searching and searching: I finally ran across a Red Hat bug report thread where RH claimed "It's a bug, it's been patched" and they closed it.
So: *Was* it a bug and *has* it been squashed? I have no problem building and installing from a tarball, *if* it will fix the problem.
Yes.
Great! I only wish I hadn't made Bad Assumptions and messed-around for half the day, yesterday, assuming it was my config. My own fault. Next time I'll pay closer attention to what -XXX' output is telling me and search a little harder. Thanks for the fast follow-up, Alan. Regards, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>.
On Fri, Oct 02, 2015 at 08:21:36AM -0400, Jim Seymour wrote:
That's 5 years old.
Yikes! I did not realize that. Jeez, Ubuntu 14.04 LTS was released only early last year, and 14.04.3 on Aug. 6 of this year.
Most distributions are depressingly slow in keeping up to date with FreeRADIUS.
Upgrade to 2.2.9, which was released this week.
Very well. Thanks!
It should be easy to build Debian/Ubuntu packages for FreeRADIUS from the source. See http://wiki.freeradius.org/building/Build#Building-Debian-packages
I only wish I hadn't made Bad Assumptions and messed-around for half the day, yesterday, assuming it was my config. My own fault. Next time I'll pay closer attention to what -XXX' output is telling me and
You should be good with just -X. More debugging output will just give you stuff you don't need to wade through. Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
participants (6)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Fajar A. Nugraha -
Jim Seymour -
Mark Foster -
Matthew Newton