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
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
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
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 =
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
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
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
7 matches
Mail list logo
