Hi guys
I've just fixed a problem where requests coming in to our Radiator
instance via IPv6 were not recognized.
I did not configure the BindAddress paramater, which defaults to
0.0.0.0. So, this was the error.
After reading up on the docs, I could not find a way to have it listen
to all IPv6.
Hi,
> Could it be the same as other apps, '::' ?
>
>
> I have now configured the hard coded addresses as a work aroudn.
goodies/ipv6.cfg
BindAddress ipv6:::
(this is basically saying, use ipv6: and bind to :: - like other daemons do)
please note that you must use ipv6: as the prefix to ho
On 09/06/2011 12:48, Alan Buxey wrote:
> Hi,
>
>> Could it be the same as other apps, '::' ?
>>
>>
>> I have now configured the hard coded addresses as a work aroudn.
>
> goodies/ipv6.cfg
>
> BindAddress ipv6:::
>
> (this is basically saying, use ipv6: and bind to :: - like other daemons
>
Hi,
> So this should make it listen for all IPv4 and IPv6:
>
> BindAddress 0.0.0.0,ipv6:::
on Solaris thats certainly true
> I heard that this might caused problems with Linux kernels?
BindAddress 0.0.0.0
BindAddress ipv6:::
that works on the few Linux boxes that I've tested
alan
_
On 06/09/2011 01:56 PM, Dyonisius Visser wrote:
> On 09/06/2011 12:48, Alan Buxey wrote:
>> Hi,
>>
>>> Could it be the same as other apps, '::' ?
>>>
>>>
>>> I have now configured the hard coded addresses as a work aroudn.
>>
>> goodies/ipv6.cfg
>>
>> BindAddress ipv6:::
>>
>> (this is basically sa
Hi,
> > BindAddress 0.0.0.0,ipv6:::
its horribly broken on Linux isnt it? on Solaris this works fine in this
incantation.
alan
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
On 06/08/2011 01:28 PM, Alex Sharaz wrote:
> I'm running a hardware load balanced Radiator setup with multiple
> Radiator back end servers. With the exception of a handful of
> variables,each back end server runs an identical config file. Accounting
> records are processed through the use of 3 , o
On 06/09/2011 03:03 PM, Alan Buxey wrote:
>>> BindAddress 0.0.0.0,ipv6:::
>
> its horribly broken on Linux isnt it? on Solaris this works fine in this
> incantation.
Heh, I guess it can be said its broken, or this is just one posibility
to do it.
For those who are interested, see for example
Well, I installed a second instance on a dual stack host, and I tested
various combinations:
BindAddress 192.87.30.31,ipv6:2001:610:148:dead::31
I.e. hardcoded addresses - this works, both IPv4 and IPv6 clients work
BindAddress ipv6:::
IPv4 blocked (NOTICE: Request from unknown client 19
hi,
I can confirm exactly the same behaviour on Linux boxes here. hardcoded
is the only way to have both working. Solaris can have both on single line
and it works. a nice patch for 4.8 to arrive? :-)
alan
___
radiator mailing list
radiator@open.com.a
On 06/09/2011 05:37 PM, Dyonisius Visser wrote:
> Well, I installed a second instance on a dual stack host, and I tested
> various combinations:
Thanks for the summary.
> BindAddress 192.87.30.31,ipv6:2001:610:148:dead::31
> I.e. hardcoded addresses - this works, both IPv4 and IPv6 clients wo
Greetings,
I have a requirement to re-write certain cisco-avpairs as they are pulled
from LDAP and returned to the LNS.
Using a PostAuthHook i'm achieving this, kind of. My problem is it looks
like its working but it isnt.
In this example I don't need to modify the particular avpair so it works
Hi Matt,
Do you get any warnings about an attribute not being in the dictionary?
I think you should be adding it like this:
$rad->add_attr('cisco-avpair', "$pairName=$pairValue");
Cheers,
Kiernan
From: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] On
Behalf Of Matt
Sent:
Hi Kiernan,
As it happens I was getting warnings.. I refer to the warning in the past
tenths as your correction to my use of add_attr of course fixed it :)
Thanks for the quick reply !
Matt
Hi Matt,
Do you get any warnings about an attribute not being in the dictionary?
I think you should
14 matches
Mail list logo
