I currently use a
separate login for slipstream clients. This sucks, but it works. I’m looking
for a good solution allowing a single dialup connection and a single
slipstream connection at the same time. I have some ideas, but haven’t had
time to test any of them yet.
Idea #1: VOPRadius
should have a searching mechanism to match profiles based on service-type
and/or other attributs. I have my slipstream users logging in with a
service-type of “Slipstream” while dialup users log in with “Framed-User”. For
accounts with multiple profiles, VOPRadius should choose the one with the
matching service-type and/or X attribute.
Idea #2: Second
Radius Server. If the slipstream server auth’d to a different radius server,
it could maintain a port limit of 1 while the dialup connection would be
auth’d against VOPRadius (each server would allow 1 connection). For this I
would find a free radius product and possibly install it right on the
Slipstream Server itself.
Idea #3: Since I use
Rodopi, use the VOPRadius realm functionality to auth to a separate database
for uid’s matching x realm. Have the event script I use which adds dialup
uid’s to my authentication database recognize the slipstream plans and also
add the uid to database #2 (the slipstream database). Then just have clients
add “@slipstream” or something similar to their uid in the slipstream client.
I think it might even be possible to have the realm hard coded into the
slipstream client at build time so the user can just add their regular uid in
the slipstream client but authentication requests will be sent from uid +
@realm but I have to review this to be sure.
Brad
Johnson
Systems
Administrator
Local Link Network Operations
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Essary
Sent: Thursday, December 30, 2004 12:51
PM
To:
[email protected]
Subject:
[VOPRadius] Slip Stream
To those of you that are running slip
stream....
If you have you user port limit set to 1 how are you dealing
with the 2nd authentication request
that comes from the slip stream
authentication server ?
We have our port limit set to 1 and there seems
to be no clean way to solve this without
opening ourselves up to port abuse
in other ways. The method with the least liability seems
to be to put
all of the slip stream users into a profile that has port limit set to 2. One
for their
connection and one for the slip stream.
Any
ideas/solutions would be appreciated.
Larry
Essary
