* This is the VOP Radius mailing list * I control this via radius profiles. I have several account types, and some triggers that force certain rate groups to have certain account types. It is all automated, so local native number users can only connect to our RASes, and users with accounts that have access to our outside networks, are not restricted by NAS. You can email me off list if you are looking for a similar setup using VopRadius and Platypus. The advantage to this, is I don't need to do anything special with the usernames for the accounts. Everything is the same setup for any account type.
Benjamin Tompkins > * This is the VOP Radius mailing list * > So, kind of a long story. > > We presently have dial-ups that authenticate to platypus. They are all in > our local area. > > We want to add dial-ups that will be passed thru to us for authentication > from globalpops.com. > > We want to continue using platypus for authentication for all networks. > > One of their dial-up numbers is local to us, but also allows us to reach > another city further north which is not local to us. > > I do not want my existing local customers to be able to use the local > dial-up number of theirs because it will incur an additional cost. > > One scenario I think will work would be to have all the outside dial-ups use > a [EMAIL PROTECTED] as their actual user name. That would be the actual > username put into platypus. > > Any other suggestions? > > -------------------------------------------------- > Gene DuCharme SysAdmin > Inland Northwest Internet 509-935-8923 > 401 S. Park St. > Chewelah, Wa. 99109 > http://www.inwi.net > > ****E-mail certified Virus Free by ModusMail**** > ************ http://www.vircom.com *********** > -------------------------------------------------- > > > ** > To leave this list, send an email to [EMAIL PROTECTED] > and put the word "LEAVE" in the BODY of the email. ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email.
