I must have been blind, as I permanently overlooked the existance of
Auth-Type := Accept.
Your suggestion solved the problem immediately.
Thank you very much.
Norbert
Dusty Doris wrote:
although I have not yet found the culprit, it is calming to know the
reason behind. I have read this and t
although I have not yet found the culprit, it is calming to know the reason
behind. I have read this and that documentation about freeradius during the
past time, but this one I think, did never cross my way. Is there a document,
where this behaviour is described?
I believe its your users fil
Norbert Wegener <[EMAIL PROTECTED]> wrote:
> although I have not yet found the culprit, it is calming to know the
> reason behind. I have read this and that documentation about freeradius
> during the past time, but this one I think, did never cross my way. Is
> there a document, where this beh
Alan DeKok wrote:
Norbert Wegener <[EMAIL PROTECTED]> wrote:
I do not see the usual eap messages flying around, but nevertheless
radius sends an Access-Accept:
...
modcall: leaving group authorize (returns updated) for request 0
rad_check_password: Found Auth-Type Accept
Norbert Wegener <[EMAIL PROTECTED]> wrote:
> I do not see the usual eap messages flying around, but nevertheless
> radius sends an Access-Accept:
...
> modcall: leaving group authorize (returns updated) for request 0
> rad_check_password: Found Auth-Type Accept
Who sets that? The server doe
test, I get an error:
STA 00:00:00:00:00:02: Received RADIUS packet matched with a pending
request, round trip time 0.24 sec
No Message-Authenticator attribute found
Incoming RADIUS packet did not have correct Message-Authenticator - dropped
STA 00:00:00:00:00:02: No RADIUS RX handler found
6 matches
Mail list logo
