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 <[EMAIL PROTECTED]> wrote: > > 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 changes > to take effect. > > Kevin Bonner > > Kevin, > > Thanks for the prompt reply. I went ahead and went to failing switches, > cleared the radius-server entries and started from scratch. I had done this > before, and it didn't fix the problem. But this time everything is working. > > It surprises me that the debug output doesn't appear to mention the failure > of the NAS secret. I would have thought I would have gotten then that message > and that the auth would have stopped there. > > Regards, > > John > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
