I just tried this with @isp3 configured to go to 10.0.0.1 and
@isp3.com configured to go to 127.0.0.2. RadiusNT correctly
forwarded the requests:
> radrecv: Request from host 7f000001 code=1, id=89, length=62
> NAS-Identifier = 127.0.0.1
> NAS-Port = 0
> User-Name = "daler@isp3"
> rad_authenticate_ODBC()
> Sending proxy request to: isp3:10.0.0.1:blah:73
> radrecv: Request from host 7f000001 code=1, id=147, length=66
> NAS-Identifier = 127.0.0.1
> NAS-Port = 0
> User-Name = "daler@isp3.com"
> rad_authenticate_ODBC()
> Sending proxy request to: isp3.my.com:127.0.0.2:blah:77
Are you using MS Access or SQL Server? You didn't include that part.
With SQL Server, the stored procedure RadCheckDomain is used to find
whethere there are any domains in the database. If this stored proc
was modified to have a "like %" clause added, I could see this
happening. The one from the docs doesn't have it, though. :(
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com