Hello Ray -
On Sat, 27 Nov 1999, Ray Carpenter wrote:
Hi all,
I wanted to strip our domain name from the username so I added the following
in the config file:
RewriteUsername s/^([^@]+).*/$1/
This works fine for authentication. Is there a way to do this for
accounting records and
Hello Robert -
On Sat, 27 Nov 1999, Robert Page wrote:
%_I have just installed Radiator on NT with Platypus. Everything is working
fine except for users with IP Address, etc., attributes assigned. They are
unable to use their connections. using the same information with our old
RADIUS
On Sat, 27 Nov 1999, Todd Knaus wrote:
Dear Fellow Radiator Users,
I am in the process of getting Radiator (running on RedHat 6.1 Unix) to
authenticate off of our Platypus server (running on an NT 4.0 box). I
followed the instructions on open.com.au under the FAQ #13 and have
downloaded
Hmmm...
You appear to be right, it appears sane today. There are no stragglers.
I would like to find a way, however, to not list certain NAS, Clients, or
Usernames in the session database.
At present, I have two situations I want to rememedy:
1. I'm getting a number of "noise" accounting
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
Hi Roy (and Tom) -
On Mon, 29 Nov 1999, Roy Hooper wrote:
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).
I'm already doing this (here's my
Hi Roy -
On Mon, 29 Nov 1999, Roy Hooper wrote:
Thanks! That worked well.
Good.
Is there any way to just discard instead of using two (or 3) session
databases?
No, not really, as you need the first one as a place-holder in any case. Its
always the first one that is used by default
Note however that you can specify an internal session database,
just like the
others, and as it runs entirely in memory it will be fast and won't leave
anything lying around.
Ahh, yes, this is what I was trying to figure out.
Actually, I have just been looking at the code, and it says that
