Hello Michael -
If your DSL users are going to be authenticated from a different realm, then what you describe will work fine.
Otherwise you could use Handlers, or you could use Identifiers in your Client clauses and use the Client-Identifier as the PoolHint for the AuthBy DYNADDRESS.
This topic has been discussed on the mailing list, so check the archives.
www.open.com.au/archives/radiator
regards
Hugh
On Thursday, Jun 26, 2003, at 13:50 Australia/Melbourne, Michael Bellears wrote:
Client of ours is running Radmin-1.7, Radiator 3.5 for dialup clients (Modem+ISDN).
They want to now also Authenticate for DSL users - NAS will be a Cisco 7200.
I have added a new Client (Via Radmin), with a NAS Type of CiscoVPDN.
Would I need to add a new realm to the config with <AuthBy RADMIN> and also containing an <AuthBy DYNADDRESS> to allocate a different pool(To the modem dialup users) of dynamic adddresses?
Has anyone setup something similar to the above that would like to share
there experiences?
Thanks in advance.
Regards, MB
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?
-- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence.
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
