wrong password failures not logged

[Stefano Zanmarchi]

Hi Alan,
but this happens only with freeradius 3 which is running in parallel with a
freeradius 2 server, and when the request from the same supplicant with a
wrong password reaches the freeradius 2 server the "login incorrect"
message appears in its logs!

Moreover, the following lines do not cause the freeradius 3 server to send
Access-Reject?
(7) mschap: Client is using MS-CHAPv2
(7) mschap: ERROR: MS-CHAP2-Response is incorrect
(7)     [mschap] = reject
(7)   } # Auth-Type MS-CHAP = reject
(7) MSCHAP-Error: ?E=691 R=1 C=6e8acc35f6597bba35a458c113c9cb09 V=3
M=Authentication failed

Thank you,
Stefano


On Thu, Mar 31, 2016 at 3:29 PM, Alan DeKok <aland at deployingradius.com>
wrote:

> On Mar 31, 2016, at 9:04 AM, Stefano Zanmarchi <zanmarchi at gmail.com>
> wrote:
> > I've realized that quite often when users fail authentication due to
> wrong
> > password this does not result in a "Login incorrect" message in the logs.
>
>   "Login incorrect" only occurs when the server sends an Access-Reject.
>
>   EAP requires many packet exchanges, and the client may simply give up
> part way through.  In that case, it won't show a "login incorrect" message.
>
>   Alan DeKok.
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html