Re: (RADIATOR) Leading spaces

2003-09-10 Thread Steve Roderick
From the manual: 6.4.19 RewriteUsername # Remove any spaces from a usernameRewriteUsername s/\s+//g If you just want to get rid of leading spaces then try this: RewriteUsername s/^\s+(.*)$/$1/ Steve - Original Message - From: Herman verschooten To: [EMAIL

Re: (RADIATOR) AuthByPolicy Question: ContinueUntilAccept

2003-01-20 Thread Steve Roderick
Couldn't you do some groups. AuthBy INTERNAL Identifier AlwaysReject DefaultResult REJECT /AuthBy AuthBy INTERNAL Identifier AlwaysIgnore DefaultResult IGNORE /AuthBy AuthBy GROUP AuthByPolicy ContinueWhileIgnore AuthBy GROUP AuthByPolicy ContinueUntilAccept AuthBy

Re: (RADIATOR) Port limit accuracy

2003-01-02 Thread Steve Roderick
Marius, I recommend doing your configuration as David described below. I would add a couple of thoughts though. If you have a NAS that sets up SNMP table entries for sessions before they are fully logged in, tears them down before the radius stop has been sent, or generally does a bad job

Re: (RADIATOR) blocking caller IDs

2002-12-24 Thread Steve Roderick
Try this: AuthBy REJECT Identifier RejectAll /AuthBy Handler Calling-Station-Id=8675309 AuthBy RejectAll /Handler Of course you want to substitute the phone number that you want to reject, or even put in a pattern such as Calling-Station-Id=/202456/ (no calls from the White House :-)

Re: (RADIATOR) Connection for all

2002-11-13 Thread Steve Roderick
You should be able to have a fall through handler that authenticates the user but returns a different IP address and possibly a filter attribute. So, if the first authentication (is account active) failed then it would fall through to the next one (special IP assignment). Something like:

Re: (RADIATOR) AuthbyRADIUS with DYNADDRESS

2002-01-07 Thread Steve Roderick
At 03:17 PM 1/7/2002 -0800, Matt Scifo wrote: The attached debug file (replyhook_example.log) shows that as soon as AuthbyRADIUS sends the Access-Request to the proxy server, an Access-Accept is sent back to our nas containing no attributes, even with the ReplyHook. The nas then authenticates

Re: (RADIATOR) AuthbyRADIUS with DYNADDRESS

2002-01-07 Thread Steve Roderick
At 03:17 PM 1/7/2002 -0800, Matt Scifo wrote: Our setup includes well over a 100 handlers which are used based on called-station-id and/or realm. There is an SQL based module that would eliminate these 100 handlers. Look for AuthSQLRadius. Steve --- Stephen Roderick Universal Telecom, Inc.

Re: (RADIATOR) AuthBy SQLRADIUS and Rewrite

2001-10-28 Thread Steve Roderick
At 09:44 AM 10/29/2001 +1000, you wrote: I think we will wait to see if anyone else has ideas for further enhancements and then we will incorporate all of them in Radiator 2.19.1. Actually I have a HostColumnDefs piece of code which may work well with the new AuthSQLRADIUS.pm. I will see if I

RE: (RADIATOR) Performance with RADIATOR

2001-03-19 Thread Steve Roderick
At 08:18 PM 3/19/2001 +0100, [EMAIL PROTECTED] wrote: We have gotten over 500 requests per second from Radiator when hitting it with multiple clients. We can do over 200 from a single client. Are you including accounting in your requests or are you purely looking at auths? We send complete

(RADIATOR) Reply:Profile pseudo attribute

2001-02-27 Thread Steve Roderick
Is there something special about this or can I use any name that I wish as long as I strip it before sending it back to the NAS? I want to: 1. Lookup a customer ID in a PreProcessingHook 2. Store the customer ID in a reply attribute 3. Process the request with a custom AuthBy module 4. Strip