The big problem I have is how their Radius implementation is setup. You
must point ALL of your NASes to the R2000 and when it gets a request for
service it forwards the Radius request to a real Radius server.. and they
only have an entry for ONE Radius server..
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com]On Behalf Of Chris Clements
> Sent: Wednesday, August 16, 2000 9:42 AM
> To: firstname.lastname@example.org
> Subject: [RadiusNT] Fitering Solutions with RadiusNT
> We are evaluating a solution for filtering the content of
> our dial-up
> Internet customers. We a server from Logon.com that is called the
> R2000. This server sits on a mirrored port with the gateway router. It
> looks at the destination address of the packet. If the IP is that of a
> blocked address the user gets a page that says "Hey this is blocked etc."
> We utilize RadiusNT 2.5 in ODBC mode with MS SQL Server.
> We want our customers to be able to choose whether or not
> to enable this
> method of filtering. We would like this to filter based on
> USERNAME not an
> IP pool.
> I suspect I will need to define the attributes for blocking in the
> attributes table and then write them to the rad config table for each
> customer. Has anyone out there done this? What are some opinions?
> Chris Clements
> Network Administrator
> CP-Tel Network Services
> (318) 352-0006 Ext 600
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: