I remember what the problem with an add-on plan was. For what ever
reason it would allow dial-up access as well. I had to have these two
attributes as a minimum for slipstream authentication to work.
Attribute on that plan is:
Slipstream-Auth - true
Service-Type - Framed-User
I thought without "Framed-Protocol=PPP" it would prevent that.
Gary Carr wrote:
We have slipstream setup 2 ways.
First is that it is included in our Unlimited plus and up plans and the
second is a addon on our regular dialup plan. In the second situation
we add a second plan to the customers account and give it a username of
ss-usersname and the same password. The radius profile for the
Slipstream plan has to attributes, profile = "" and
Service-Type = Framed-User so the user can be authenticated in
VopRadius.
Gary
We
are stripping it. I was able to authenticate properly when I have
slipstream=true on the dialup profile. What I was trying to do is use a
different list of username/passwords than the default Rodopi list.
Problem is that VOP doesn't know to look at the other list. What I have
decided to do is, rather than having a separate plan I'll have two
dialup plans, one with slipstream the other without.
Also, Gary, I found that in the Radius Attribute editor in Rodopi you
can add:
Slipstream-Auth=true (or false)
This means you don't have to use the profile file in VOP for the
slipstream-auth line. I haven't test without the dictionary
modification, but being that it is working I'm not going to mess around
with it for the moment.
Paul
Gary Carr wrote:
Have you setup a realm in your vopradius for the @domail.com or are you
stripping it.
Gary
Well, back at it again this week. Before I start. Rodopi 5.1sp2 and
VOPRadius 2.
Still unable to authenticate. I made a new plan with (and new supporting
features for the plan, i.e., slipstream username and password) but when
the user - [EMAIL PROTECTED] - logs in VOPRadius erros with the error:
--snip--
(Reject :02672) 11/10/2003 10:45:40 Invalid Attempt: [203.63.154.1:1234]
test1 - Invalid UserID/Password! [or ODBC Error][987654321/123456789]
--snip--
If I add the clause slipstream=true to our dail-up attributre,
everything works, but I can't tell which user can or can't use the
service. So how do I tell Rodopi or VOPRadius where to look for this
username and password. Also, I've never seen "[987654321/123456789]" on
the end of this error before. Anyone know what it means?
Paul
---------------------
To Leave the Rodopi mail list send a message to [EMAIL PROTECTED]
with the word LEAVE as the message body.
Please also visit the Rodopi FAQ at http://www.rodopi-faq.com
---------------------
---------------------
To Leave the Rodopi mail list send a message to [EMAIL PROTECTED]
with the word LEAVE as the message body.
Please also visit the Rodopi FAQ at http://www.rodopi-faq.com
---------------------
|
