On Sun, Nov 28, 1999 at 10:44:22PM -0500, Roy Hooper wrote:
> At present, I have two situations I want to rememedy:
>
> 1. I'm getting a number of "noise" accounting packets sent by one of our
> vendors to check our server is working. These packets tend to pollute the
> session database, but can be easily ignored if I can prevent them from
> making it to the session database by UserID.
If they're using something that's always the same, then create a Handler
that matches and ignores these packets (although you may want to log
them to make sure they're doing their job etc).
>
> 2. I've got a number of accounting packets coming in from one NAS in order
> to track 1-800 service. 50% of this same NAS includes accounting packets I
> do not want in the radwho database, and am presently not logging to file
> because I don't want to see them, except when debugging. The rest of the
> packets I am very interested in tracking, and am presentlying doing this by
> realm for this NAS -- packets w/o a realm are ignored for logging to file
> for accounting, the rest are kept.
>
If you can distinguish them easily based on Radius attributes then another
Handle to collect the discardables would be the solution.
[EMAIL PROTECTED]
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
