Re: Huntgroups/preprocess issue 1.1.6
Alan DeKok wrote: Craig Huckabee wrote: That is sort of the question - what is there to port ? I don't see any documentation saying the format of the huntgroups file changed from 1.1.2 to 1.1.6. It didn't, but the parser got more careful. It used to accept (and ignore) things that the server didn't support. It now complains about them. I've narrowed it down even more - only seems to choke on NAS-Port. NAS-Port-ID or any other attribute I've tried works fine. --Craig - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Huntgroups/preprocess issue 1.1.6
The build goes without a hitch, but when running the new version and using the existing configuration files I get the following (relevant output from 'radiusd -X'): the problem IMHO is in using the existing configuration: I had similar issues until I ported mine to the new configuration files, half an hour of work. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Huntgroups/preprocess issue 1.1.6
inverse wrote: The build goes without a hitch, but when running the new version and using the existing configuration files I get the following (relevant output from 'radiusd -X'): the problem IMHO is in using the existing configuration: I had similar issues until I ported mine to the new configuration files, half an hour of work. That is sort of the question - what is there to port ? I don't see any documentation saying the format of the huntgroups file changed from 1.1.2 to 1.1.6. I can understand having to port config files when making a major version leap (e.g. 0.9.3 = 1.1.x), but for a minor version change ? --Craig - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Huntgroups/preprocess issue 1.1.6
Craig Huckabee wrote: That is sort of the question - what is there to port ? I don't see any documentation saying the format of the huntgroups file changed from 1.1.2 to 1.1.6. It didn't, but the parser got more careful. It used to accept (and ignore) things that the server didn't support. It now complains about them. I can understand having to port config files when making a major version leap (e.g. 0.9.3 = 1.1.x), but for a minor version change ? Your previous configuration didn't do what you expected. It's not porting, it's bug fixing, because the error messages just got better. 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/users.html
