Hi Rainer,
As stated in the changelog for 3.6, Radiator no longer indexes on UDP
port. This is illustrated by the following code from Client.pm :
# its not a dup, save the id for later dup checking
$self-{RecentIdentifiers}-{$p-{RecvFromAddress}}-{$code .
$p-identifier} = $p-{RecvTime};
Seems
One possibility is that a reply from the server you proxy to arrives
outside the timeout set in Radiator, i.e. a late packet. When the
timeout period expires Radiator removes the packet from the queue and
generates a new packet (or if it is the last try stops sending).
Because there now is no
Hello,
I was wondering whether it's possible to do some kind of conditional
logging, with the AcctLogFileName. For example, would it be
possible to
say, that radiator should only log the accounting line (defined in
AcctLogFileFormat), if Acct-Status-Type (or any other attribute) has a
See 6.15 and 6.27, i.e. something like this :
AuthBy RADIUS
Hosteric.open.com.au
Secret 666obaFGkmRNs666
Identifier radiusproxy1
/AuthBy
handler Called-Station-Id="value"
AuthBy radiusproxy1
/Handler
Regards
Arjan
-Original Message-
In earlier versions you should use an AuthByPolicy ContinueWhileIgnore.
If a SQL-database fails Radiator cannot get a reply and ignores the request
instead of rejecting it.
Arjan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Hugh Irvine
Sent: Friday,
--
From: Mike McCauley[SMTP:[EMAIL PROTECTED]]
Sent: Friday, February 23, 2001 2:06 PM
To: [EMAIL PROTECTED]
Subject:(RADIATOR) Restricting DefaultSimultaneousUse to a particular client
Hi.
I'm currently using Radiator in an environment where people
are dialling in
