Is there any particular reason why we don't by default store NAS-Identifier in the SQL db? -- Peter Nixon http://peternixon.net/
Peter Nixon wrote:
Is there any particular reason why we don't by default store NAS-Identifier in the SQL db?
No and I do :) Though it's worth doing a update request { NAS-Identifier = "%{Client-Shortname}" } Somewhere in authorize / post-auth , so you always have a friendly identifier for the nas.
Arran Cudbard-Bell wrote:
Peter Nixon wrote:
Is there any particular reason why we don't by default store NAS-Identifier in the SQL db?
No and I do :)
Though it's worth doing a
update request { NAS-Identifier = "%{Client-Shortname}" }
Somewhere in authorize / post-auth , so you always have a friendly identifier for the nas.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
Or in the query %{%{NAS-Identifier}:-%{Client-Shortname}} If you don't need to log it anywhere else.
Alan DeKok wrote:
Peter Nixon wrote:
Is there any particular reason why we don't by default store NAS-Identifier in the SQL db?
It might not exist. It's nearly meaningless.
Yes but see previous posts. I\t makes it far easier to identify a NAS if you have a proper identifier.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
Peter Nixon wrote:
Is there any particular reason why we don't by default store NAS-Identifier in the SQL db?
I think it depends on the local setup. On my site I get a NAS-IP-Address and no NAS-Identifier. It won't hurt to add it to the DB queries, but I'm unsure it would be useful for most of the users. -- Nicolas Baradakis
participants (4)
-
Alan DeKok -
Arran Cudbard-Bell -
Nicolas Baradakis -
Peter Nixon