RE: Class attribute questions
I just wanted to make sure that I wasn't missing something, and that there isn't an easier way to get at the ASCII inside the octet stream. Edit the dictionary, and change "octets" to "string"?
I saw discussion in a previous thread (Handling of the 'Class' attribute, this post in particular, http://lists.freeradius.org/mailman/htdig/freeradius-users/2003-July/021 267.html) that implied this was frowned upon, at least when interacting with other RADIUS servers (which is what I'm using FreeRADIUS for), but also because the RFC recommends that it should be treated as undistinguished octets.
2) The rfc's allow for more than one Class attribute (at least in Accounting-Request packets). How does FreeRADIUS treat references to %{Class} when this happens? i.e. Is there a syntax to refer to each instance of the Class attr or get a count of how many are in the packet? The CVS snapshots allow this. 1.0.x doesn't. See doc/variables.txt
I read through the current doc/variables.txt in CVS. Looks great. Is this a 1.1.x kind of feature or will it find it's way into a later 1.0.x? Thanks for the reply. -Shawn
"Shawn K. O'Shea" <shawno@airpath.com> wrote:
I saw discussion in a previous thread (Handling of the 'Class' attribute, this post in particular, http://lists.freeradius.org/mailman/htdig/freeradius-users/2003-July/021 267.html) that implied this was frowned upon, at least when interacting with other RADIUS servers
Editing the FreeRADIUS dictionary files will have *zero* impact on other RADIUS servers.
I read through the current doc/variables.txt in CVS. Looks great. Is this a 1.1.x kind of feature or will it find it's way into a later 1.0.x?
1.1.x and following. Alan DeKok.
participants (2)
-
Alan DeKok -
Shawn K. O'Shea