On 8 Nov 96 at 7:33, MegaZone wrote:
> Once upon a time Tony Graham shaped the electrons to say...
> >bobo Password = "f/5ed", Expiration = "Dec 24 1998"
> > User-Service-Type = Dialback-Framed-User,
> > Framed-Protocol = PPP,
> > Framed-Netmask = 255.255.255.0,
> > Framed-Routing = Broadcast-Listen,
> > Framed-Filter-Id = "std.ppp",
> > Framed-MTU = 1500,
> > Framed-Compression = Van-Jacobsen-TCP-IP,
> > Dialback-No = "5555"
>
> Dialback-No is NOT used for Framed Dialback Users. Framed Dialback users
> MUST have a dedicated location table entry.
>
And, as you should know, a severe drawback in using PortMasters in a
typical dialback environment. We have customers who exclusively use
dialback for security and easy accounting.
Now, you have the possibility to you RADIUS for authentication. But
all dialback locations have to be defined in the several Portmasters.
This is shit:
(1) no central database
(2) new users require new locations in each PM
(3) number of location limited to free FLASH space - no warning, just
a big crash if FLASH is full
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").
Does the following work:
(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?
best regards,
Frank
-- Frank M. Heinzius MMS Communication GmbH frimp@mms.de Eiffestrasse 598 http://www.mms.de 20537 Hamburg, Germany Phone: +49 40 211105-0 Fax: +49 40 210 32 210