What will be new in v3.0.3
It's been a busy week. In addition to releasing new documentation (http://networkradius.com/doc/), we've been adding more functionality to the server core. As of now, pretty much all of "unlang" is syntax checked when the server starts. This means that errors in conditional checks will be caught: if ("%{no-such-module:foo}" == "bar") { will now cause the server to print a descriptive error, and fail to start. The same applies for update statements: update reply { Filter-Id := "%{no-such-module:foo}" } And switch statements: switch "%{no-such-module:foo}" { and case statements: case "%{no-such-module:foo}" As a side note, "case" statements now support dynamic expansions, which they didn't before. Both "switch" and "case" statements support attribute references: switch &User-Name { case &Filter-Id { ... Will match if User-Name == Filter-Id. This capability gives a bit more flexibility in the use of "switch" and "case". These are small changes. But they should have a large impact on usability. When there's a typo in the configuration, the server will produce a MUCH better error message than it did for version 3.0.2. Alan DeKok.
Good morning, * Alan DeKok <aland@deployingradius.com> [2014-03-28 21:15]:
As of now, pretty much all of "unlang" is syntax checked when the server starts. ... The same applies for update statements:
update reply { Filter-Id := "%{no-such-module:foo}" }
It looks like this breaks the default accounting policy update statement: .../etc/radiusd.conf[134]: Failed parsing expanded string: .../etc/radiusd.conf[134]: %{md5:%{User-Name},%{Acct-Session-ID},...} .../etc/radiusd.conf[134]: ^ Unknown module Is this intended? If yes, how should the Acct-Session-ID be computed now? Julius
On 1 Apr 2014, at 10:01, Julius Plenz <plenz@cis.fu-berlin.de> wrote:
Good morning,
* Alan DeKok <aland@deployingradius.com> [2014-03-28 21:15]:
As of now, pretty much all of "unlang" is syntax checked when the server starts. ... The same applies for update statements:
update reply { Filter-Id := "%{no-such-module:foo}" }
It looks like this breaks the default accounting policy update statement:
.../etc/radiusd.conf[134]: Failed parsing expanded string: .../etc/radiusd.conf[134]: %{md5:%{User-Name},%{Acct-Session-ID},...} .../etc/radiusd.conf[134]: ^ Unknown module
Is this intended? If yes, how should the Acct-Session-ID be computed now?
Is the expr module loaded? Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Hi, Arran! * Arran Cudbard-Bell <a.cudbardb@freeradius.org> [2014-04-01 11:45]:
It looks like this breaks the default accounting policy update statement:
.../etc/radiusd.conf[134]: Failed parsing expanded string: .../etc/radiusd.conf[134]: %{md5:%{User-Name},%{Acct-Session-ID},...} .../etc/radiusd.conf[134]: ^ Unknown module
Is this intended? If yes, how should the Acct-Session-ID be computed now?
Is the expr module loaded?
Ah, thanks! That seems to be the problem. The server starts up just fine now. Julius
participants (3)
-
Alan DeKok -
Arran Cudbard-Bell -
Julius Plenz