Hi Mike and Hugh,
Thank you very much for the new feature. Most of the time, it works
well. However, we just come into a situation when the old IP was
reallocated and the PING test just failed to tell.
I think the solution is simple. Before writing a new session record,
remove any existing on
Hello,
We had a problem with
Dynamic address allocator configuration. Our part of configuration file is
below:
--
# Accounting for Intranet
User
AuthByPolicy ContinueWhileAccept
#Authenticate only,
accounting on another table DBSourc
Hola Hugh -
Thanks for your help.
whr
- Original Message -
From: "Hugh Irvine" <[EMAIL PROTECTED]>
To: "William Hernandez" <[EMAIL PROTECTED]>; "Radiator"
<[EMAIL PROTECTED]>
Sent: Tuesday, June 13, 2000 7:32 PM
Subject: Re: (RADIATOR) Password Log File Format
Hello William -
>From
Hi Hugh,
Here is the output from DSL Terminatior:
RADIF: radius type Acct ID = 100
RADIF: _radiusAcctRequest: type 0 id 100, user name <0:>
RADIF: _radiusAcctReq: socket 8 len 49 IP 160.79.128.15 port 1026=>1813, ID=100
RADIF: _radCallback: buf=81543660 from 160.79.128.15 1813
RADIF: _radProcAcc
I might have better luck on a Unix newsgroup, but I'll proceed anyway...
Regarding the SocketQueueLength global, does this pertain to the same
setting as the kern.ipc.somaxconn MIB variable? On my system, I get:
# sysctl kern.ipc.somaxconn
kern.ipc.somaxconn: 128
According to "m
Help!
We have recently changed to Platypus ISP Billing software and Radiator to
handle Authentication and Accounting.
We are running Radiator in Emerald mode so we have the RadiusNT options in
Platypus.
Everything works fine except the settings in the RadiusNT - Acct Attributes
tab. Radiator is
Hello Benjamin -
On Thu, 15 Jun 2000, Benjamin Wakefield wrote:
>
> Help!
>
> We have recently changed to Platypus ISP Billing software and Radiator to
> handle Authentication and Accounting.
>
> We are running Radiator in Emerald mode so we have the RadiusNT options in
> Platypus.
>
> Every
Hello Clement -
On Wed, 14 Jun 2000, Clement wrote:
> Hi Mike and Hugh,
>
> Thank you very much for the new feature. Most of the time, it works
> well. However, we just come into a situation when the old IP was
> reallocated and the PING test just failed to tell.
>
> I think the solution is
Hello Dave -
On Thu, 15 Jun 2000, Dave Kitabjian wrote:
> I might have better luck on a Unix newsgroup, but I'll proceed anyway...
>
> Regarding the SocketQueueLength global, does this pertain to the same
> setting as the kern.ipc.somaxconn MIB variable? On my system, I get:
>
> # sysctl
Hello Garry -
On Thu, 15 Jun 2000, Garry Shtern wrote:
> Hi Hugh,
>
> Here is the output from DSL Terminatior:
>
> RADIF: radius type Acct ID = 100
> RADIF: _radiusAcctRequest: type 0 id 100, user name <0:>
> RADIF: _radiusAcctReq: socket 8 len 49 IP 160.79.128.15 port 1026=>1813, ID=100
> RAD
Hello Le Anh Tuan -
On Wed, 14 Jun 2000, Le Anh Tuan wrote:
>
> Hello,
> We had a problem with Dynamic address allocator configuration. Our part of
> configuration file is below:
> --
> # Accounting for Intranet User
>
>AuthByPolicy ContinueWhile
--- Forwarded mail from [EMAIL PROTECTED]
Date: Thu, 15 Jun 2000 02:10:22 +1000 (EST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: BOUNCE [EMAIL PROTECTED]:Non-member submission from [David
Lloyd <[EMAIL PROTECTED]>]
>From mikem Thu Jun 15 02:10:16 2000
Received: by oscar.open.co
On Jun 15, 8:33am, Hugh Irvine wrote:
> Subject: Re: (RADIATOR) Sim. use control by Ping
>
> Hello Clement -
>
> On Wed, 14 Jun 2000, Clement wrote:
> > Hi Mike and Hugh,
> >
> > Thank you very much for the new feature. Most of the time, it works
> > well. However, we just come into a situation
Hi all,
I am back again... I am trying to set up a setup on a
Cobalt RaQ3 with shadowed passwords, I don't even know if this can be
done. Anyhow If I do a radpwtst it works fine with no problems, but as
soon as I dial-up via PPP using PAP authentication radius locks up and
starts queuing
That makes pretty good sense. As the one who added the
DeleteIPQuery code and made this suggestion earlier, the mod offered by
Mike allows you to modify the delete query without changing any internal
code. No?
--
Aaron H
Hey Hugh,
You were absolutly right! Thank you so much. As soon as I added the
shared secret to the Accounting, it worked like a charm. I didn't know
that on Ascends you have to set a secret for accounting like you do for
authentication. Good lesson for me, I guess :)
Again, thanks a lot...
Looks excellent to me. Where can I get this feature?
Mike McCauley wrote:
> ...
> The DeleteQuery gets run just before adding a new session. I wonder if the
> right thing is to alter the DeleteQuery so it deletes the IP address too:
>
> DeleteQuery delete from RADONLINE where (NASIDENTIFIER
Hello Clement -
You would configure the DeleteQuery in your clause.
See section 6.6.4 in the Radiator 2.16.1 reference manual.
regards
Hugh
On Thu, 15 Jun 2000, Clement wrote:
> Looks excellent to me. Where can I get this feature?
>
> Mike McCauley wrote:
> > ...
> > The DeleteQuery gets
Hello Le Anh Tuan -
On Thu, 15 Jun 2000, Le Anh Tuan wrote:
> Dear Mr Hugh,
> Thanks you so much for your help. But I have another question:
>- How can AuthBy DYNADDRESS dectect when NAS reboot to reset it's address
> pool (for example when Account-Request=Accounting-On) ?
> - In that case
19 matches
Mail list logo
