FR 2.0.3 gives duplicate NULL realm error

[John Horne]

On Tue, 2008-04-08 at 08:18 +0200, Alan DeKok wrote:
> John Horne wrote:
> > It seems that radiusd doesn't like the NULL realm after the DEFAULT. I
> > swapped these two around, and radiusd started up fine.
> 
>   ?  I can start up the server fine with those realms, in any order.
> 
Yes, with 2.0.2 I had the NULL realm in proxy.conf last. However, with
2.0.3 I have swapped these around a couple of times now, and it always
fails (duplicate realm error) if the NULL realm is last and the DEFAULT
realm is present. If I comment out the DEFAULT realm, although the NULL
realm is still last, then radiusd starts up. So it seems to be an
interaction between both the DEFAULT and NULL realms being present.

> >> I'm not sure why the 'radiusd -X' output gives as the very last line
> >> '} # realm NULL'. 
> >>
> > The code shows that it always does this (replacing 'NULL' for the
> > relevant realm name).
> 
>   Where in the code?
> 
>   That message is printed out *only* if it finds two realms with the
> same name.
> 
Sorry, I meant always does this if the duplicate realm error is
displayed.


John.
-- 
---------------------------------------------------------------
John Horne, University of Plymouth, UK  Tel: +44 (0)1752 233914
E-mail: John.Horne at plymouth.ac.uk       Fax: +44 (0)1752 233839