S-IP-Address = 127.0.0.1
NAS-Port = 0
# Executing section authorize from file
/etc/freeradius/sites-enabled/default
+- entering group authorize {...}
++[preprocess] returns ok
[auth_log] expand:
/var/log/freeradius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d ->
/var/log/f
Hi,
> Hello friends, I tell them:
> When I try to authenticate using mschap I encounter this
> error''NT_STATUS_WRONG_PASSWORD: Wrong Password'', yet when I do the
> test using authentic pap without problems. I'm trying to authenticate my
> freeradius server with active directory server.
> Greet
Hello friends, I tell them:
When I try to authenticate using mschap I encounter this
error''NT_STATUS_WRONG_PASSWORD: Wrong Password'', yet when I do the
test using authentic pap without problems. I'm trying to authenticate my
freeradius server with active directory server.
Greetings and waiti
On Thu, Dec 1, 2011 at 3:58 AM, Jim Pazarena wrote:
> Ahh. the FreeBSD docs indicate that the default for password encryption
> is MD5.
>
> Now I need to learn how to "use" MD5 within freeradius.
> Suggestions would be most appreciated.
FR should support MD5 just fine. Take a look at raddb/module
Alan,
I updated the ports tree in FreeBSD which upgraded FreeRadius to 2.1.12 from
2.1.10. After installation I am successful on doing basic PAP
Authentication. It solved this issue.
Thank You so much!
--
View this message in context:
http://freeradius.1045715.n5.nabble.com/Error-Failed-to
Alan DeKok wrote, On 2011-11-30 9:47 AM:
Jim Pazarena wrote:
This is most baffling. When I ran cistron, it just "worked"; but I switched
No. FreeRADIUS is 64-bit clean.
My guess is that the passwords on 64-bit FreeBSD are *not* encrypted
with the "crypt" function. There is some other
Hi,
> No. FreeRADIUS is 64-bit clean.
>
> My guess is that the passwords on 64-bit FreeBSD are *not* encrypted
> with the "crypt" function. There is some other API necessary to do
> password checks.
BSD is a little different ;-)
http://www.bsdcertification.org/downloads/user_management.pd
Jim Pazarena wrote:
> This is most baffling. When I ran cistron, it just "worked"; but I switched
> to 64-bit FreeBSD, and cistron doesn't like a 64-bit OS.
Cistron is old...
> I tried the login with 3 user IDs including my own, and all fail.
> Any suggestions would be most appreciated. Is it p
Коньков Евгений wrote:
>
> while using this verion
> FreeRADIUS Version 2.1.3, for host i386-portbld-freebsd7.1, built on Jan 6
> 2009 at 10:52:08
> I can run radius as
> /usr/local/bin/screen -d -m /usr/bin/nice -n -20 /r/radiusd debug
What is "/r/radiusd debug" ?
> but with
> FreeRADIUS
while using this verion
FreeRADIUS Version 2.1.3, for host i386-portbld-freebsd7.1, built on Jan 6
2009 at 10:52:08
I can run radius as
/usr/local/bin/screen -d -m /usr/bin/nice -n -20 /r/radiusd debug
but with
FreeRADIUS Version 2.1.10, for host i386-portbld-freebsd9.0, built on Nov 28
201
Am 30.11.2011 15:53, schrieb Alan DeKok:
> Andreas Rudat wrote:
>> in my enviroment I got three AP's runnning, all with the same essid,
>> after a while the connection seems lost
> WHAT connection?
>
> If it's the connection between the AP and the PC, this isn't a RADIUS
> issue.
I only saw tha
Andreas Rudat wrote:
> in my enviroment I got three AP's runnning, all with the same essid,
> after a while the connection seems lost
WHAT connection?
If it's the connection between the AP and the PC, this isn't a RADIUS
issue.
> and a reconnection starts to
> another AP and then I get the r
To save other the trouble I will ask the obvious:
1) what does the RADIUS debug log say, please post it here IN FULL, do not clip
out the portion you think you need.
2) have you checked the config on the client and the AP?
3) What part of this problem do you think is a RADIUS issue, and why?
Hi,
in my enviroment I got three AP's runnning, all with the same essid,
after a while the connection seems lost and a reconnection starts to
another AP and then I get the resumption error but I have no idea why I
lost the connection. No Errors in radius debug and a good reception is
given.
The re
14 matches
Mail list logo