We are pleased to announce the release of Radiator version 3.7.1
This version contains an important fix for a typo that was introduced
in version 3.7 as well as support for EAP Generic Token Card
As usual, the new version is available free of charge to current
licensees from
Hello Terry,
On Fri, 26 Sep 2003 03:44 pm, Terry Simons wrote:
Howdy,
After upgrading to Radiator 3.7 I'm getting the following error:
Reply-Message = EAP TTLS inner authentication redespatched to a
Handler
Things worked just fine in 3.6... :)
I took a look in eap_ttls.cfg, but it
Hello,
On Fri, 26 Sep 2003 02:03 pm, Tech wrote:
I to have had the same problem but this only started after I had
downloaded the last patches for 3.6. I was running 3.6 with the patches
that were aval around May of this year with no problems.
This was due to a typo that was introduced in
Hello!
We had some problems in the past regarding our main database server
(Oracle). The problem is, when the database slows down (it is still
accepting connections but runs very slow) Radiator starts slowing down
too and my NAS boxes eventually timeout. So all my users start getting
rejected.
Just want to make sure I'm not totally out in left field on how to
accomplish this, I thought I'd ask. We just recently setup MySQL
Replication.. and I'd like to make our Radiator software use the master
and slaves for authentication (just using DNS round robin atm).. but
since only the
hi,
i am trying to think of a method where i can avoid
connect to db
do something...
disconnect from db
each time one of my hook gets processing in a radius operation for each
postauth request. (so if it handles 100k packets it means that
Igor-
It sounds like you are using the Oracle database for storing accounting data
only. If that is the case how about runnning an instance of Radiator on each
box for authentication and another instance of Radiator for accounting? That
way authentication should not be affected by database
On Pet, 2003-09-26 at 13:59, Frank Danielson wrote:
Igor-
It sounds like you are using the Oracle database for storing accounting data
only. If that is the case how about runnning an instance of Radiator on each
box for authentication and another instance of Radiator for accounting? That
You can use an existing database handle from an AuthBy SQL or SessSQL in
your hook. This not only reduces the overhead of disconnecting and
reconnecting to the db each time but also lets you leverage the work that
Radiator does behing the scenes to manage the db connection. Here is an
excerpt
The only catch is that AuthBy SQL will open a connection to the database
when it starts up and keep that connection up unless there is a problem with
it so your round robin DNS will not do much. AuthBY SQL supports declaring a
database to use as a backup which may be a better scheme for
10 matches
Mail list logo
