problem with proxy and 2.0pre2

[A.L.M.Buxey at lboro.ac.uk]

Hi,

>   It may not be working right.
> 
>   See src/main/realms.c, function home_server_ldb().  It SHOULD look for
> DEFAULT.  But it isn't well tested.

aha. thanks for the feedback.  i also see another issue. if i have a few
servers defined in a pool, then i am given the 'already exists' error
and the server wont start eg

test_config {
        server0 = radius1.our.tld
        server1 = radius2.our.tld
        secret0 = monkey_heaven
        secret1 = iguana_depot
}


server_pool testing {
                home_server = test0
                home_server = test1
}

home_server test0 {
                hostname = ${test_config.server0}
                secret = ${test_config.secret0}
                port = 1812
                type = auth+acct
                nostrip
}

home_server test1 {
                hostname = ${test_config.server1}
                secret = ${test_config.secret1}
                port = 1812
                type = auth+acct
                nostrip
}


the server complains that test0 already exists when loading in test1

i also note another pseudo-issue. the example proxy.conf supplied
comes with the last few lines....

#
#  This realm is for requests which don't have an explicit realm
#  prefix or suffix.  User names like "bob" will match this one.
#
#realm NULL {
#       type            = radius
#       authhost        = radius.company.com:1600
#       accthost        = radius.company.com:1601
#       secret          = testing123
#}

#
#  This realm is for ALL OTHER requests.
#
#realm DEFAULT {
#       type            = radius
#       authhost        = radius.company.com:1600
#       accthost        = radius.company.com:1601
#       secret          = testing123
#}


however, 'type = radius' is now defunt - and the server doesnt like it
at all. acct+auth is the correct and only alternative, yes?

alan