Complex conditions have been checked in.
With some documentation, too. The old-style: if "ok|fail" { no longer works. If anyone was using it, don't upgrade for a bit. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Alan Dekok wrote:
With some documentation, too.
The old-style:
if "ok|fail" {
no longer works. If anyone was using it, don't upgrade for a bit.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
Now if only the CVS head could bind to ports on Darwin :\ -- 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
A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
Now if only the CVS head could bind to ports on Darwin :\
I had an issue under Linux where is would bind - but that was because another instance was already running - the output error didnt say that though...
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
Restarted the server and everything .. Still no luck.. Try and start CVS head, gives me bind error. Try and start CVS from the 10th everything works fine ... It's not the system it's the code :( -- 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
Alan Dekok wrote:
Arran Cudbard-Bell wrote:
Now if only the CVS head could bind to ports on Darwin :\
If you could narrow it down to the day where it stops working, that would help rather a lot.
Alan DeKok.
The stuff you just checked in seems to have fixed whatever the issue was... Thanks :) Is there any documentation for the new conditionals ? --- Arran
Arran Cudbard-Bell wrote:
The stuff you just checked in seems to have fixed whatever the issue was... Thanks :)
I think it was the udpfromto changes.
Is there any documentation for the new conditionals ?
doc/configurable_failover There should be a new "freeradius-language" man page that documents this. I'm also planning to add the following:\ ... update request { attribute-name = value ... } i.e. "request" or "response" or "config", etc. Also: switch "foo" { case bar { } case baz { } } The config file parse puts the entries into a tree, so that should scale as O(log(N)), which permits fast access to millions of entries, if necessary. Alan DeKok.
doc/configurable_failover
There should be a new "freeradius-language" man page that documents this. I'm also planning to add the following:\
... update request { attribute-name = value ... }
YES ! No more hints files !
i.e. "request" or "response" or "config", etc.
Also:
switch "foo" { case bar {
} case baz { } }
Yep also very useful. Are return codes of modules available ? e.g switch users { case ok { update response { Reply-Message = "User Found in Users" } } case noop { update response { Reply-Message = "User Not Found in Users" } } Excellent work so far :) --- Arran
switch users { case ok { update response { Reply-Message = "User Found in Users" } } case noop { update response { Reply-Message = "User Not Found in Users" } }
Or probably far easier users switch %{return}{ case ok { update response { Reply-Message = "User Found in Users" } } case noop { update response { Reply-Message = "User Not Found in Users" } } Where return is expanded to the return code of the last executed module.
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan Dekok -
Arran Cudbard-Bell