On Thu, 22 Sep 2016 14:53:27 +0000 Alan DeKok <aland@deployingradius.com> wrote:
Upgrade to a recent version of the server.
Fair enough thanks, I'll advocate for using a recent stable tarball instead of a packaged version.
Features which are undocumented are ones which probably don't work.
Hah, apparently. Legacy installs are confusing, especially when they did things they shouldn't have done. There is another place in the config that has this and doesn't result in any noticeable errors: authorized { eap { ok = return } *shrug* Time to go through the config and validate everything else that might be a little wonky. Thanks for your help, John
On Sep 22, 2016, at 11:02 AM, John Kristoff <jtk@depaul.edu> wrote:
Hah, apparently. Legacy installs are confusing, especially when they did things they shouldn't have done. There is another place in the config that has this and doesn't result in any noticeable errors:
authorized { eap { ok = return }
Read the documentation. This is allowed for *modules*.
*shrug* Time to go through the config and validate everything else that might be a little wonky.
Recent versions of 3.0 are much more picky about what they allow. And, they complain in great detail, with very useful error messages. i.e. if it doesn't complain, it's likely fine. Alan DeKok.
participants (2)
-
Alan DeKok -
John Kristoff