[VOP RADIUS] tracking and suspending proxied users

[Customer Support]

Title: Message

Hello Vasia,   To do this you can use the VOP Radius API/Hook "VPRHook.dll". The package can be downloaded from the following URL:   http://www.vircom.com/downloads/vopradius/softwares/VPRHook.ZIP   This is a very complicated project because you must know how to program using C++ and as well you must have very good knowledge of the Radius protocol. As far as I know no one has ever implemented a project like this so it is experimental. The overhead will increase substantially once VPRHook begins to perform time banking for pass through authentication requests. So if you are running close to the machine's resource limit, then you will likely have to upgrade your hardware.   If you want Vircom to research this as a feature request (or any feature request for that matter), then you should contact our Product Manager: Daniel Roy ([EMAIL PROTECTED]).   Thank-you   Andrew O'Halloran Technical Support Department Vircom Inc. http://www.vircom.com Email: [EMAIL PROTECTED] Phone: (514) 990-2532 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Vasia Sent: Friday, July 05, 2002 4:46 PM To: [EMAIL PROTECTED] Subject: [VOP RADIUS] tracking and suspending proxied users Vircom engineers, Have a few realm we proxy to. I need to shut off users if they go over a set hour limit. Presently your program doesn't have that feature.   Have figured out how to make it work. Just need the source code to have someone look at it to see if we can do it. If you can't release the source code Here is what I came up with. enduser dials the NAS --------------->Qwest -------------> my radius -----------> downstream radius (Access request) Downstream radius ------------------> my radius --------->Qwest ----------> NAS (Access granted)   I want to set up the access granted from downstream proxy to query my radius before sending the granted back. When i set up the client via the ROAMER option it will trigger an event to cause the request to check that table first. In the client configuration i would also input the time this realm is allowed. also just like the error logs roll over to a different file daily I would have it set up to roll over to a new table that would start the process over for the new month. On a new month it would look for the name that rolled over from previuos month and deduct from the reset time. If name is not there it would add the name.   At the same time this is being built I would modify the license to be monthly and it would check this table. This way if a customer just buys 200 licenses for the month it will stop him at 200 unique users for the month. the first 200 users can authenticate any new users will not be able to.   Looking forward to resolving this soon.   thanks Vasia