Hi,
> When you enable IPv6 for a service updating OS and Software is often
> required. Having minimum requirements for IPv6 the docs would help
depends on how old your OS/software is. given that I was running IPv6 services
on servers at the beginning of the last decade (IPv6 isnt somethign new...
On 2013-06-28 16:38, Heikki Vatiainen wrote:
> On 06/28/2013 03:17 PM, Mueller, Jason C wrote:
>
>> I am still using ipv6:::, since I have not yet convinced system
>> administrators to change the bindv6only attribute to 1.
>>
>> The example above (which a couple of others also suggested) works for
Heikki,
On Jun 28, 2013, at 1:58 PM, Heikki Vatiainen wrote:
> On 06/28/2013 07:56 PM, Mueller, Jason C wrote:
>
>> I have currently relented to specifying every individual IP address
>> that needs to listen for RADIUS across the set of systems running
>> Radiator (both v4 and v6), and I will j
Heikki,
On Jun 28, 2013, at 1:58 PM, Heikki Vatiainen wrote:
> On 06/28/2013 07:56 PM, Mueller, Jason C wrote:
>
>> I have currently relented to specifying every individual IP address
>> that needs to listen for RADIUS across the set of systems running
>> Radiator (both v4 and v6), and I will j
On 06/28/2013 08:41 PM, Johnson, Neil M wrote:
> Is there a recommended version of PERL to run Radiator 4.11 on? I'm
> running a fairly old version on my windows boxen (Active State 5.12)?
I think 5.16 is a good choice. I do not see anything wrong with 5.12
either but for new deployments I'd take
On 06/28/2013 07:56 PM, Mueller, Jason C wrote:
> I have currently relented to specifying every individual IP address
> that needs to listen for RADIUS across the set of systems running
> Radiator (both v4 and v6), and I will just live with the binding
> errors when Radiator starts. The reason is
Heikki,
Is there a recommended version of PERL to run Radiator 4.11 on? I'm
running a fairly old version on my windows boxen (Active State 5.12)?
Thanks.
-Neil
--
Neil Johnson
Network Engineer
The University of Iowa
Phone: 319 384-0938
Fax: 319 335-2951
Mobile: 319 540-2081
E-Mail: neil-john...
>The reason is that the Radiator config is managed in a single file that is
>pushed to multiple systems to ensure consistency of the config
We do the same thing... config created from database and then pushed. Avoids
possible human errors that could arise from editing config on several systems
Thanks for the information. I am still working on changing the system IPv6
default. I have currently relented to specifying every individual IP address
that needs to listen for RADIUS across the set of systems running Radiator
(both v4 and v6), and I will just live with the binding errors when R
On 06/28/2013 03:17 PM, Mueller, Jason C wrote:
> I am still using ipv6:::, since I have not yet convinced system
> administrators to change the bindv6only attribute to 1.
>
> The example above (which a couple of others also suggested) works for a
> single address (i.e., ipv6::::128.255.90.
Heikki,
> When BindAddress is set to ipv6::: and request comes in from an IPv4
> address 172.20.3.170 you'll get this in the logs:
>
> DEBUG: client_addr:
> <0><0><0><0><0><0><0><0><0><0><255><255><172><20><3><170>
>
> When BindAddress is commented out and defaults to IPv4 0.0.0.0 you'll
> get t
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
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 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
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 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
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.
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
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
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
Hello Jason -
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
5.5 Address binding
One of the main functions of Radiator is to listen for UDP packets and TCP
connections from other
21 matches
Mail list logo
