John Morris wrote:
> It surprises me that the debug output doesn't appear to mention the
> failure of the NAS secret.
It does. There's a big WARNING during the authentication portion.
> I would have thought I would have gotten
> then that message and that the auth would have stopped there.
Is there a way to define NAS info / secrets in a SQL database and have
it as part of the standard queries? Am guessing the perl / python
options would let you do it from that (pls correct me tho if not
right!) but can it just be done without writing code?
Tia
Andy
On 25/10/2007, John Morris <[EMAI
Debug output like this usually points to non-matching RADIUS secrets. Check
the radius secret in your switch config as well as the secret configured in
your nas SQL table. Freeradius only reads the nas table on startup, so if
you make changes to that table, you must restart the daemon for those
On Thursday 25 October 2007 17:26:10 John Morris wrote:
> I then added a second switch to the freeradius client configuration (nas
> table), and encountered a problem. The password was being rejected. So I
> ran Freeradius -X so I could see what was going on.
>
> On the failed password attempt (s
4 matches
Mail list logo
