Security I can see. But how does it help accounting?
>Now, you have the possibility to you RADIUS for authentication. But
>all dialback locations have to be defined in the several Portmasters.
The PM wasn't designed to be a dialback server in wide use. Most comm
servers have limitations in this area - this is the PMs limitation.
Dialback is a capability that wasn't expected to be used to the extent
some users do. So you run into a design wall at the moment.
>I already asked for dynamic, RADIUS-based locations for Portmasters.
>It should also be possible to use DEFAULT locations and passing the
>phone number as a user parameter (Dialback-Framed-Location =
>"babelfish", Dialback-Number = "42").
I proposed something else as an internal RFE - a Location entry server.
Using the same technology developed to serve filters for ChoiceNet, you
could have the PM ask a Location server for centrally managed location
table entries.
But we don't have a lot of demand for this kind of thing.
>(1) Define a normal login Dialback user in RADIUS with the supplied
>phone number
>(2) Define an additional PPP user for the above login (or use RADIUS
>2.0 prefix/suffix).
>(3) If the user logs in with account (1), the PortMasters dials back.
>After the connect, the PM asks for user/password again. Now enter the
>login (2).
>What do you think?
Hmm, it *sounds* logical. All I can say is try it.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 6920 Koll Center Parkway #220, Pleasanton, CA 94566