I've never had cause to look at it before, but I discovered today that accouting doesn't support huntgroups; specifically, an attempt to match on Huntgroup-Name in acct_users Is this expected? How does one normally specify Acct-Type based on a huntgroup, if (say) the Class attribute is already being used?
Phil Mayers wrote:
I've never had cause to look at it before, but I discovered today that accouting doesn't support huntgroups; specifically, an attempt to match on Huntgroup-Name in acct_users
Is this expected?
The "preprocess" module doesn't do huntgroups for accounting requests. This should be relatively easy to fix.
How does one normally specify Acct-Type based on a huntgroup, if (say) the Class attribute is already being used?
In 2.0, much of the huntgroup functionality can be done with a little bit of magic: client foo { ipaddr = 127.0.0.1 secret = x huntgroup = foo # invent ANYTHING here! foo = bar, x = y, etc. } Then in unlang: ... if ("%{client:huntgroup}" == "foo") { ... } i.e. you can use the configuration files to add arbitrary "tags" to a client, and then check them at run time. Alan DeKok.
In 2.0, much of the huntgroup functionality can be done with a little bit of magic:
client foo { ipaddr = 127.0.0.1 secret = x huntgroup = foo # invent ANYTHING here! foo = bar, x = y, etc. }
Then in unlang:
... if ("%{client:huntgroup}" == "foo") { ... }
i.e. you can use the configuration files to add arbitrary "tags" to a client, and then check them at run time.
Woah, get that working with SQL and you have an insanely useful feature. Oooo what VLANS does this NAS support, hmm i'll just check the client VLAN tags. Where is this NAS located, hmm i'll just check the arbitrarily populated location tag. Who was meant to be updating the client list SQL features for 2.0 ?
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Arran Cudbard-Bell (A.Cudbard-Bell@sussex.ac.uk) Authentication, Authorisation and Accounting Officer Infrastructure Services | ENG1 E1-1-08 University Of Sussex, Brighton EXT:01273 873900 | INT: 3900
Arran Cudbard-Bell wrote:
Woah, get that working with SQL and you have an insanely useful feature. Oooo what VLANS does this NAS support, hmm i'll just check the client VLAN tags. Where is this NAS located, hmm i'll just check the arbitrarily populated location tag.
Err... why? You can do that already: if ("%{sql: SELECT ... WHERE client = %{client:shortname} ...}" .... Alan DeKok.
Hi,
Arran Cudbard-Bell wrote:
Woah, get that working with SQL and you have an insanely useful feature. Oooo what VLANS does this NAS support, hmm i'll just check the client VLAN tags. Where is this NAS located, hmm i'll just check the arbitrarily populated location tag.
Err... why? You can do that already:
if ("%{sql: SELECT ... WHERE client = %{client:shortname} ...}" ....
yep - but i think the default schema for clients didnt have these extra features added. at least someone mentioned synchronising them recently more importantly for other people - do these attributes get passed through the message structure for PERL and Python? alan
A.L.M.Buxey@lboro.ac.uk wrote:
yep - but i think the default schema for clients didnt have these extra features added. at least someone mentioned synchronising them recently
more importantly for other people - do these attributes get passed through the message structure for PERL and Python?
Nope. They're only in the configuration file, and only available via the run-time expansion. But you *can* do: update request { Client-Foo = "%{client:foo}" } Which is good enough for most purposes. Alan DeKok.
Alan DeKok wrote:
Arran Cudbard-Bell wrote:
Woah, get that working with SQL and you have an insanely useful feature. Oooo what VLANS does this NAS support, hmm i'll just check the client VLAN tags. Where is this NAS located, hmm i'll just check the arbitrarily populated location tag.
Err... why? You can do that already:
if ("%{sql: SELECT ... WHERE client = %{client:shortname} ...}" ....
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Yeah ... I know. It's just with static information, you don't really want to be querying the database again and again for each query. Lodging the information against the client is far more efficient, especially with VLAN information which isn't going to be changing regularly. -- Arran Cudbard-Bell (A.Cudbard-Bell@sussex.ac.uk) Authentication, Authorisation and Accounting Officer Infrastructure Services | ENG1 E1-1-08 University Of Sussex, Brighton EXT:01273 873900 | INT: 3900
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Arran Cudbard-Bell -
Phil Mayers