Gary T. Giesen wrote:
I've compiled freeradius with the --with-udpfromto directive.
...
However, if I specify multiple IPs to bind to (rather than just one or
all), it reverts to the the behaviour of responding to all requests
with a source IP of the first bind directive listed. For example:
Built latest git and still the exact same results.
GG
On Tue, May 3, 2011 at 8:23 AM, Alan DeKok al...@deployingradius.com wrote:
Gary T. Giesen wrote:
I've compiled freeradius with the --with-udpfromto directive.
...
However, if I specify multiple IPs to bind to (rather than just one or
My apologies, it does seem to be working correctly now... I found part
of the problem was that I hadn't specified a source IP address for
proxying, but direct clients were broken as well too so I'm going to
drop back to the old version and see if I still have the same problem
GG
On Tue, May 3,
Gary T. Giesen gie...@snickers.org wrote:
In this configuration, freeradius will always respond from
192.168.1.250, even if the initial request was sent to 1.2.3.4. This
is obviously breaking things for me, as I'd rather not have freeradius
listen on every interface on the server (and
Tanjil Ahmed tan...@tanjil.net wrote:
why radius is not bind auto MAC from user in first time use?like mikrotik
user manager have this option...
...dear user, why do people keep hijacking mailing list threads and use
the *Reply-To* button rather than *Compose* in their email clients?
is
Dear All
why radius is not bind auto MAC from user in first time use?like mikrotik
user manager have this option...
is there any way?
Thanks in Advance
On Tue, May 3, 2011 at 3:20 AM, Gary T. Giesen gie...@snickers.org wrote:
I've compiled freeradius with the --with-udpfromto directive.
6 matches
Mail list logo
