Hi Tim -
Yes, well that is the same conclusion that Mike and I came to as well.
I think the best and simplest approach is to run multiple instances - one on
each IP address, as you have described before.
regards
Hugh
On Wed, 1 May 2002 13:19, Timothy G. Wells wrote:
> Thanks!
>
> But I fou
h SMTP id g3UGFuo26554;
Tue, 30 Apr 2002 12:15:56 -0400
Message-Id: <[EMAIL PROTECTED]>
To: "Timothy G. Wells" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Subject: ADDL INFO Re: (RADIATOR) Bound IP
Date: Tue, 30 Apr 2002 16:15:56 GMT
X-Mailer: Endymion M
Thanks!
But I found an unfortunate issue with this. If I remove the BindAddress
and let Radiator listen on all IP's then the answer comes back as
0.0.0.0. If I leave the BindAddress then it does say the correct IP but
that doesn't help me in my attempt to prevent having multiple instances
running
Hello Tim -
You have access to both the source and destination:
$p->{RecvFrom};
and
$p->{RecvSocket};
Have a look at "Radius/Radius.pm", sub newRecvFrom.
regards
Hugh
On Tue, 30 Apr 2002 22:45, Timothy G. Wells wrote:
> Greetings,
>
> From within a hook, how would
Hi Tim,
You should use the BindAddress parameter in your radius config file to define this
(note that the AuthBy RADIUS has its own binding, as its a client).
/Ingvar
> -Original Message-
> From: Timothy G. Wells [mailto:[EMAIL PROTECTED]]
> Sent: den 30 april 2002 14:45
> To
