Hello Robert,
Thanks for reporting this problem.
We have posted a patch that should fix it.
We apologise for this problem
Cheers.
On Tue, 30 Sep 2003 01:59 am, Robert Blayzor wrote:
> I don't know if this effects other OS's, but on FreeBSD, when sending a SIG
> HUP to Radiator the monitor port s
Hello Rainer -
Here is the comment block from "Radius/Client.pm":
# In order to detect duplicate arrivals, we keep an array
# of arrivals ($self->{RecentIdentifiers})indexed by
# the IP address of the host that sent the request,
# the UDP port number (some hosts like Lucent TNT have multiple ID s
Hi!
I've seen that radiator detects duplicate records depending only on the
identifier and the client IP:
"If more than 1 Radius request from this Client with the same Radius
Identifier are
received within DupInterval seconds, the 2nd and subsequent are ignored."
Shouldn't be the Identifier, the
I don't know if this effects other OS's, but on FreeBSD, when sending a SIG
HUP to Radiator the monitor port stops working...
Mon Sep 29 11:55:17 2003: NOTICE: SIGHUP received: restarting
Mon Sep 29 11:55:17 2003: ERR: Could not bind Monitor socket: Address
already in use
Mon Sep 29 11:55:17 2003:
Oh, my! And I thought it was a typo. I deleted it on purpose! Later, when it
didn't function I didn't even remember about it. It's working fine now.
Thank you for your help, Hugh.
cheers
cl.
- Original Message -
From: "Hugh Irvine" <[EMAIL PROTECTED]>
To: "Claudio Lapidus" <[EMAIL PROTEC
Hello Claudio -
Please look at my example again:
sub
{
my $p = ${$_[0]}; # original request packet
my $rp = ${$_[1]}; # reply packet to NAS
my $handled = $_[2]; # flag to indicate ACCEPT, REJECT or IGNORE
# Only deal with authentication requests
my $code = $p->code();
r
