> Depends on the NAS. But yeah, doing this breaks things. The best thing you >
> can do is log the error in the post-auth section.
In V1 of FR, the rlm_mschap module used to create a Module-Failure-Message
request attribute containing the output of ntlm_auth, if ntlm_auth failed
(rlm_ldap does
On 14/08/2009 07:51, Alan DeKok wrote:
Michael Bryant wrote:
unlang? set a variable to the value of MS-CHAP-Error and then set the
Reply-Message
to be some text with that variable in it.
Unfortunately, this sends it back in the next packet, which is an
Access-Challenge, not in the final Acces
Michael Bryant wrote:
>> unlang? set a variable to the value of MS-CHAP-Error and then set the
>> Reply-Message
>> to be some text with that variable in it.
>>
> Unfortunately, this sends it back in the next packet, which is an
> Access-Challenge, not in the final Access-Reject.
Sending Reply-M
>
> unlang? set a variable to the value of MS-CHAP-Error and then set the
> Reply-Message
> to be some text with that variable in it.
>
Unfortunately, this sends it back in the next packet, which is an
Access-Challenge, not in the final Access-Reject.
Also, for some strange reason, the post-au
Hi,
> Hi,
> Using the default eap/peap & inner-tunnel configuration, a failure gives rise
> to
> this:
>
> Exec-Program output: Logon failure (0xc06d)
> Exec-Program-Wait: plaintext: Logon failure (0xc06d)
> Exec-Program: returned: 1
> [mschap] External script failed.
> [mschap] FAILED:
Hi,
Using the default eap/peap & inner-tunnel configuration, a failure gives rise to
this:
Exec-Program output: Logon failure (0xc06d)
Exec-Program-Wait: plaintext: Logon failure (0xc06d)
Exec-Program: returned: 1
[mschap] External script failed.
[mschap] FAILED: MS-CHAP2-Response is inc
6 matches
Mail list logo
