f0rud wrote:
> No its exactly 2.1.9 from GIT(last update 1 or 2 days ago after you fix
> some problem.) and I'm happy with ignoring the check. so leave it be.
Well... 2.1.9 works with 1.1.8. So something is broken on your local
system if they behave differently.
Alan DeKok.
-
List info/subs
On Thu, 2010-06-10 at 16:39 +0200, Alan DeKok wrote:
> f0rud wrote:
> > Thats the problem, version 1.1.8 have no problem!(This time I check this
> > myself. with the code from download page.)
>
> OK... you haven't said which version of FreeRADIUS you're using. Let
> me guess: it's not 2.1.9.
>
f0rud wrote:
> Thats the problem, version 1.1.8 have no problem!(This time I check this
> myself. with the code from download page.)
OK... you haven't said which version of FreeRADIUS you're using. Let
me guess: it's not 2.1.9.
>>> I see the code for another messages (for ex: PW_AUTHENTICATION
On Thu, 2010-06-10 at 14:12 +0200, Alan DeKok wrote:
> f0rud wrote:
> > I found the "calc_replydigest" function in radius.c always return 2
> > (digest_cmp failed) Since this function is new in code , then its the
> > problem and the diff. with version 1.x
>
> The "digest_cmp" is failing because
f0rud wrote:
> I found the "calc_replydigest" function in radius.c always return 2
> (digest_cmp failed) Since this function is new in code , then its the
> problem and the diff. with version 1.x
The "digest_cmp" is failing because the packet is wrong.
Try the old code from an earlier version
Hi all
I found the "calc_replydigest" function in radius.c always return 2
(digest_cmp failed) Since this function is new in code , then its the
problem and the diff. with version 1.x
For fixing my problem, I just by pass this test for PW_DISCONNECT_ACK
(not a good idea I know but what else I can
On Wed, 2010-06-09 at 15:16 +0200, Bjørn Mork wrote:
> f0rud writes:
>
> > So Mikrotik accept this (and then I can say shared secret is OK),
>
> Sure? Did you try deliberately using a wrong secret to verify that the
> NAS validates the request?
>
Yes, with wrong secret , NAS add my request to
f0rud writes:
> So Mikrotik accept this (and then I can say shared secret is OK),
Sure? Did you try deliberately using a wrong secret to verify that the
NAS validates the request?
> but
> radclient report this as failed. how its possible? in this case server
> is NAS and accept the request , w
On Wed, 2010-06-09 at 13:53 +0200, Alan DeKok wrote:
> So... fix the shared secret. Nothing else will solve the problem.
It is "fixed" The Mikrotik report that OK and Disconnect the user and
log the entry as a success.
20:25:11 pppoe,ppp,info : terminating... - administrator
request
20:25:11 p
I had the same problem with FR 2.x and the shared secret is correct. FR
1.x works fine, clients.conf is correct,
I didn't had much time to deal with this problem so I didn't want to
bother you on this list. ..
Alan DeKok wrote:
f0rud wrote:
work fine, Mikrotik dissconnect user wit
f0rud wrote:
> work fine, Mikrotik dissconnect user with successs BUT i get this :
>
> Sending Disconnect-Request of id 107 to 192.168.0.6 port 1700
> Acct-Session-Id = "8141"
> User-Name = "testuser"
> rad_recv: Disconnect-ACK packet from host 192.168.0.6 port 1700, id=107,
> leng
Hi all.
Somehow I'm new in freeradius. and beacuse I live in Iran I can't access
this mail archive from web easy.(They are censored whole mail archive
and I don't know why!!) So I ask this here and sorry if its a duplicate
message :)
using mikrotik RuterOS and any thing is OK, the problem is Dissc
12 matches
Mail list logo
