RE: AD Authentication + radius + foundryAP
I don't like leaving things unresolved and just laying around like so
many other post that I have ran across. I guess Alan DeKok scares them
off with the It's in plain view dumb ass attitude. I'm sure after
answering the questions over and over again, it is about the only
response that someone can give who it just tired of the same old
questions and wants a challenge.
With that being said...
On Ubuntu 10.04 w/ updates, FreeRadius 2.1.8, Windows XP/7, and W2K AD
The wiki has a HowTo on AD
http://wiki.freeradius.org/FreeRADIUS_Active_Directory_Integration_HOWTO
At the very top of this page there is:
Updated tutorial for freeradius 2.x is at:
http://deployingradius.com/documents/configuration/active_directory.html
This is all well and good, but I jumped straight to that link. There
seems to be some information that is left out and that is important in
the Updated tutorial.
With all of the frustration I nuked all of FreeRadius from the server
using 'aptitude purge freeradius freeradius-common freeradius-utils'.
This cleaned up all of my changes. Then I reinstalled FreeRadius.
From here I followed the Updated tutorial until I got to: Configuring
FreeRADIUS to use ntlm_auth for MS-CHAP. When I reached this section,
and I had everything working, I went back to the original HowTo and read
though it. (note to self: don't just a head just because a HowTo seems
to good to be true.
The Updated tutorial doesn't let you know anything about peap,
with_ntdomain_hack, the default setting of eap, or setting up clients.
So it is not, in my opinion a complete walk though.
There is light though. Once you I got to the point where ntlm_auth was
working for me, I started back on the wiki HowTo and went to the section
'Configuration of clients.conf'.
Set the client up.
Client foundryAP {
Ipaddr = 192.168.0.1
Secret = testing123
}
In the Configuration of radius.conf section (this parts seems more like
the 1. Config) the 'with_ntdomain_hack = yes' this was found in the
~/modules/mschap file. You don't need 'auth-type = MS-CHAP'.
For ntlm_auth I'm using:
ntlm_auth = /usr/bin/ntlm_auth --request-nt-key
--username=%{mschap:User-Name} --challenge=%{mschap:Challenge:-00}
--nt-response=%{mschap:NT-Response:-00}
--require-membership-of=DOMAIN+group
The eap.conf section of the HowTo was spot on. I also set the clients
up, this was pointed out to me earlier in this tread twice, so make sure
your client is setup correctly as well.
Currently everything is working. I'm able to authenticate though radius
using Windows 2000 AD.
Resolved.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: AD Authentication + radius + foundryAP
Mark Pipkin wrote: With all of the frustration I nuked all of FreeRadius from the server using 'aptitude purge freeradius freeradius-common freeradius-utils'. This cleaned up all of my changes. Then I reinstalled FreeRadius. i.e. start from the default configuration. From here I followed the Updated tutorial until I got to: Configuring FreeRADIUS to use ntlm_auth for MS-CHAP. When I reached this section, and I had everything working, I went back to the original HowTo and read though it. (note to self: don't just a head just because a HowTo seems to good to be true. And then follow the documentation. It *will* work. The Updated tutorial doesn't let you know anything about peap, with_ntdomain_hack, the default setting of eap, or setting up clients. So it is not, in my opinion a complete walk though. Sure. It documents one piece of the server functionality. For the rest, documentation generally exists. Currently everything is working. I'm able to authenticate though radius using Windows 2000 AD. Resolved. Exactly. The frustration I generally show is people (a) butchering the default configs, (b) refusing to follow the docs, and (c) arguing when told don't do that. It's really not hard. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: AD Authentication + radius + foundryAP
hi, a quick look at your output shows that your server is configured to have a defauly type of EAP that doesnt match what your client is trying to use. there is then a reattempt after the NAK - and your client is using LEAP. it fails at the LEAP stage in the EAP module - check your eap.conf or, if you arent supposed to be using LEAP then check your client! ;-) alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
RE: AD Authentication + radius + foundryAP
Post the debugging output into the form at:
http://networkradius.com/freeradius.html
And read the highlighted lines. It should be obvious what's going
on.
Module: Instantiating attr_filter.access_reject
attr_filter attr_filter.access_reject {
attrsfile = /etc/freeradius/attrs.access_reject
was highlighted in read. To you it might be obvious what this means. To
me, I don't really understand it, except that later one in the debug I
get :
Using Post-Auth-Type Reject
+- entering group REJECT {...}
[attr_filter.access_reject] expand: %{User-Name} - ATL\pipkin_m
I don't know much about FreeRadius. I have never had to work with a
radius server of any type before. I do apologize, but while this stuff
might be obvious to someone that created it or works in radius servers
every day of the week, I am not that person. So to me, the only obvious
thing is that I get rejected at leap, while another radius server that
is running FreeRadius 1.x on Getoo is working just find with mschapv2.
Also read my Active Directory guide at:
http://deployingradius.com/documents/configuration/active_directory.htm
l
It contains detailed documentation and explanations for how to get
this to work.
I did follow this how-to the first time around and it got me to this
point. That is in my first statement in asking for help.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: AD Authentication + radius + foundryAP
Mark Pipkin wrote:
was highlighted in read. To you it might be obvious what this means. To
me, I don't really understand it, except that later one in the debug I
get :
You're supposed to read the output. Only looking at *part* of it
means you can only solve *part* of the problem.
Here's the key pieces of your original post:
...
pap] WARNING! No known good password found for the user.
Authentication may fail because of this.
++[pap] returns noop
Found Auth-Type = EAP
+- entering group authenticate {...}
[eap] Request found, released from the list
[eap] EAP/leap
[eap] processing type leap
rlm_eap_leap: No Cleartext-Password or NT-Password configured for this user
...
What does that look like to you?
Are the debug messages helpful?
Do they accurately describe the problem, and give you hints for the
solution?
I don't know much about FreeRadius. I have never had to work with a
radius server of any type before. I do apologize, but while this stuff
might be obvious to someone that created it or works in radius servers
every day of the week, I am not that person. So to me, the only obvious
thing is that I get rejected at leap, while another radius server that
is running FreeRadius 1.x on Getoo is working just find with mschapv2.
The PC is choosing LEAP, not FreeRADIUS.
Configure the PC to use LEAP, as was suggested in *another* response
to your post.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
RE: AD Authentication + radius + foundryAP
What does that look like to you? Looks like it is trying to use PAP to authenticate with. Though PAP is local only, at least from what I can tell, and there is no local user/pass for this account. Then it looks like it rolls to a EAP/leap authentication method. At this point it fails. Are the debug messages helpful? If I truly understood more, then I'm sure that they would be. That are not as helpful for me; I have a lack of understanding at this point in time. Do they accurately describe the problem, and give you hints for the solution? I just see the problem as not working. I don't understand why it didn't even attempt mschapv2 when eap default was set to peap and peap default was set to mschapv2. I don't know much about FreeRadius. I have never had to work with a radius server of any type before. I do apologize, but while this stuff might be obvious to someone that created it or works in radius servers every day of the week, I am not that person. So to me, the only obvious thing is that I get rejected at leap, while another radius server that is running FreeRadius 1.x on Getoo is working just find with mschapv2. The PC is choosing LEAP, not FreeRADIUS. I'm using Win7. Are you telling me that the PC is the one that is picking the security for the radius and not the Foundry Wireless AP controller? Configure the PC to use LEAP, as was suggested in *another* response to your post. I read that post. I thought the he was referring to the Foundry AP controller. You just told me that it was the fault of the PC though. Mark Pipkin - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: AD Authentication + radius + foundryAP
Mark Pipkin wrote: What does that look like to you? Looks like it is trying to use PAP to authenticate with. i.e. you haven't *read* the warning message. You just saw pap and WARNING, and stopped there. To be excruciatingly simple: RADIUS servers authenticate users by KNOWING what the correct password is. If the server doesn't have a KNOWN GOOD password, it can't authenticate the user. The message says that there is no *KNOWN GOOD* password, and therefore it likely will not be able to authenticate anyone. Though PAP is local only, at least from what I can tell, and there is no local user/pass for this account. Then it looks like it rolls to a EAP/leap authentication method. At this point it fails. No. The LEAP message has the same meaning as the PAP message. And you're again ignoring the *content* of the message. Why? Are the debug messages helpful? If I truly understood more, then I'm sure that they would be. That are not as helpful for me; I have a lack of understanding at this point in time. Read them. It helps. Really. Do they accurately describe the problem, and give you hints for the solution? I just see the problem as not working. I don't understand why it didn't even attempt mschapv2 when eap default was set to peap and peap default was set to mschapv2. My messages explained why. The PC is choosing LEAP, not FreeRADIUS. I'm using Win7. Are you telling me that the PC is the one that is picking the security for the radius and not the Foundry Wireless AP controller? Did my message contain the phrase Foundry Wireless AP? Or did my message contain the acronym PC? Configure the PC to use LEAP, as was suggested in *another* response to your post. I read that post. I thought the he was referring to the Foundry AP controller. You just told me that it was the fault of the PC though. Exactly. If you READ my messages, you get answers to questions. Like the question you asked above about when you say PC, do you really mean PC? Honestly, I fail to understand why there is *any* confusion here. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
