Dear all,
For your reference, the Radiator 3-2 manual contains a small error regarding
the AddAddressQuery in section 6.53.8.
Below you find the correct text and the correct default SQL-query:
snip
AddAddressQuery
This optional parameter allows you to define a custom SQL query to add an
I don't think there is a way to tell inside of Radiator. You can run
multiple instances of Radiator with each one bound to a different address
using the BindAddress config parameter. This will also give you the
advantage of being able to handle more traffic since you will have multiple
threads
Anyone here have any experience doing the radius accounting with
Comindico DialIP Ports? (Australia)
I am not sure how to deal with their double accounting radius records.
If they had the same session ID this would not be a problem... but they
come from 2 sources with different id's maybe a
Title: Message
So..
if they are on a looong time, you can simply take the last accounting record for
that session id?
Hmmm.. I am trying to work out how the best deal with
customers who are on for LONG periods of times... weeks - perhaps months in the
DSL world.
Daily
usage
If you don't like this behavior, you can specify your handlers like this:
Handler Realm=bogus-service, Request-Type=Access-Request
...
...
AddToRequest Attribute-Name = Attribut-Value
/Handler
Handler Realm=bogus-service, Request-Type=Accounting-Request
...
== From: [EMAIL PROTECTED]
If you don't like this behavior, you can specify your handlers like this:
Handler Realm=bogus-service, Request-Type=Access-Request
...
...
AddToRequest Attribute-Name = Attribut-Value
/Handler
Handler Realm=bogus-service,
The only downside to doing it this way is that it still adds the
attributes to access-reject reply packets, which inherantly does not
cause problems, except when dealing with larger networks, such as UUNet
which request that the only attributes passes back are Proxy-State and
Reply-Message...
Hi. Is it possible to quickly disable persistent connections for SQL
logging? Persistent connections do not work well with our SQL Server,
since they time out. Short failure backoff times do not help either
since I think any DB connection failure trips the RADIUS authentication code
on the
== From: [EMAIL PROTECTED]
The only downside to doing it this way is that it still adds the
attributes to access-reject reply packets, which inherantly does not
cause problems, except when dealing with larger networks, such as UUNet
which request that the only attributes passes back are
Unisphere ERX Vendor 4874 Attribute 24
Hi All,
This attribute number (24) does not appear in the latest dictionary file.
Does anyone know what it should be - we only just started receiveing them
after an ERX upgrade.
Regards,
Brian Morris
NetSpeed.
===
Archive at
Hi Skeeve,
What you may notice, is these packets also contain the attribute Tunnel-Id
These attributes will match the two packets, perhaps you could use that in
order to collect the two packets correctly.
I have to battle that one myself in a few days, I have suggested to
COMindico engineers
Thanks to Chris Patterson at TransACT for this...
VENDORATTR 4874 Unisphere-Pppoe-Description 24 string
Regards, Brian.
- Original Message -
From: Brian Morris [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 27, 2002 9:16 AM
Subject: (RADIATOR) Unisphere ERX Vendor
Brian,
This is the MAC address of the device requesting a pppoe connection.
VENDORATTR 4874 Unisphere-Pppoe-Description 24 string
Cheers
Chris.
-Original Message-
From: Brian Morris [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 27 August 2002 9:17 AM
To: [EMAIL PROTECTED]
Subject:
Hello Wim, Hello Miko -
Thanks Wim - I was going to write the same thing as you did.
The reason that AddToReply does what it does is because there are people
who do want to add attributes to both rejects and to accounting replies.
The manual is incorrect and has been fixed for the next
Hello Dan -
Can you please tell me what database you are using and what platform?
thanks
Hugh
On Tuesday, August 27, 2002, at 04:34 AM, Dan Melomedman wrote:
Hi. Is it possible to quickly disable persistent connections for SQL
logging? Persistent connections do not work well with our SQL
Hugh Irvine wrote:
Hello Dan -
Can you please tell me what database you are using and what platform?
thanks
Hugh
I thought SQL Server implied MS SQL Server :). This is FreeBSD. Anyway,
we need connect-log-disconnect behavior instead of the current
implementation.
===
Archive at
Hello Dan -
I must confess that this is the first time I have ever heard this
request. All other previous requests in this area have been for
long-held connections to the SQL server.
I have copied this mail to Mike for further comments.
regards
Hugh
On Tuesday, August 27, 2002, at 12:31
Hello Dan,
On Tue, 27 Aug 2002 14:49, Hugh Irvine wrote:
Hello Dan -
I must confess that this is the first time I have ever heard this
request. All other previous requests in this area have been for
long-held connections to the SQL server.
I have copied this mail to Mike for further
18 matches
Mail list logo
