Hugh,
> According to section 5.5 in the Radiator 4.11 reference manual
> ("doc/ref.pdf") you need to specify both ipv6 and ipv4 like this:
>
>
> BindAddress ipv6:::, 0.0.0.0
That syntax doesn't work on my system. The issue is not with the binding
statement. I am able to receive both IPv4 an
Christian,
>>> According to section 5.5 in the Radiator 4.11 reference manual
>>> ("doc/ref.pdf") you need to specify both ipv6 and ipv4 like this:
>>>
>>>
>>> BindAddress ipv6:::, 0.0.0.0
>>
>> That syntax doesn't work on my system. The issue is not with the binding
>> statement. I am able
Well we rolled back to an image of the system made the day before the
change and it started working.
AndŠ we managed to break it again uninstalling Symantec and installing
Microsoft's Anti-virus like we did before.
I agree that something is hosing the network stackŠ.
Definitely not a RADIATOR pr
What would be interesting is whether a clean install of Windows and just the
installation of the Microsoft SEP kills it
alan
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
Well, according to our server support folks, they performed this same procedure
on our other 8 RADIUS servers and didn't have any issues.
They were using SCCM (Microsoft's System Center Configuration Manager) to
automate the uninstall and re-install of the software rather than a manual
process.
For the sake of testing out whether making the BindAddress look as you
suggested might help, I went ahead and did as you suggested. My Bind Address
now looks like this:
BindAddress ipv6:::, 0.0.0.0
I was thinking that there just might be a chance that Radiator would need the
"0.0.0.0" value to
Hi,
> Quick summary again, when using ipv6::: and bindv6only set to 0:
> * Both IPv4 and IPv6 traffic gets to Radiator
> * IPv6 works with everything I have tried
> * IPv4 clients will not match on the proper client stanza, only the DEFAULT
> client stanza
I have the following:
BindAddress 0.0.
On 6/27/2013 3:01 PM, Mueller, Jason C wrote:
Quick summary again, when using ipv6::: and bindv6only set to 0:
* Both IPv4 and IPv6 traffic gets to Radiator
* IPv6 works with everything I have tried
* IPv4 clients will not match on the proper client stanza, only the DEFAULT
client stanza
Perha
Alan,
> Hi,
>
>> Quick summary again, when using ipv6::: and bindv6only set to 0:
>> * Both IPv4 and IPv6 traffic gets to Radiator
>> * IPv6 works with everything I have tried
>> * IPv4 clients will not match on the proper client stanza, only the DEFAULT
>> client stanza
>
> I have the followin
On 06/28/2013 12:01 AM, Christopher Bongaarts wrote:
> On 6/27/2013 3:01 PM, Mueller, Jason C wrote:
>> Quick summary again, when using ipv6::: and bindv6only set to 0:
>> * Both IPv4 and IPv6 traffic gets to Radiator
>> * IPv6 works with everything I have tried
>> * IPv4 clients will not match on
Clients are defined by their IP address (apart from RADSEC clients which come
through the RADSEC clause). The server runs other services on v4 and v6 too.
alan!
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radia
On Thu, 27 Jun 2013, Mueller, Jason C wrote:
> It seems to me that this is an issue where Radiator does not match on
> IPv4 client stanzas when specifying a bind of "ipv6:::", which is a
> legitimate binding statement that results in IPv4 traffic also working.
>
> To summarize again, with my cur
12 matches
Mail list logo
