From: Chris Jensen <cjensen@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: No more auth succeeded log messages
Date: Fri, 16 Jul 2004 03:14:51 +0000 [thread overview]
Message-ID: <fa61edfd04071520142d9d46c0@mail.gmail.com> (raw)
In-Reply-To: <fa61edfd04071520071163c16b@mail.gmail.com>
Hi,
Previously, ppp was generating log messages like
> Jul 5 08:52:24 vpntest pppd[15519]: CHAP peer authentication succeeded for username
Which we were grepping out of the logs to see who was logging on and
when. Users are being authenticated via the radius plugin using
MS-CHAPv2.
However, the last couple of days there have been no such messages.
The kernel was upgraded from 2.4.20 to 2.6.7 at the same time this
seems to have started, and ppp was reinstalled, but I'm pretty sure it
remained at the same version (though I did have to download the
tarball again as I'd deleted it from the first install).
Is there a simple way to enable logging of CHAP usernames that I'm missing?
Thanks for any assistance.
Chris
prev parent reply other threads:[~2004-07-16 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 3:07 No more auth succeeded log messages Chris Jensen
2004-07-16 3:14 ` Chris Jensen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa61edfd04071520142d9d46c0@mail.gmail.com \
--to=cjensen@gmail.com \
--cc=linux-ppp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).