On 14/06/2011 15:21, Heikki Vatiainen wrote:
Linux also has this special file to control the system wide behaviour:
/proc/sys/net/ipv6/bindv6only
If I do this to enable the option:
echo 1 |sudo tee /proc/sys/net/ipv6/bindv6only
the same configuration works:
BindAddress ipv6:::,
Does this mean that we can't bind to IPv4 and IPv6 separately on Linux
to not get v6 mapped v4 addresses?
Am 2011-06-09 19:50, schrieb Heikki Vatiainen:
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:
On 06/14/2011 11:45 AM, Alexander Hartmaier wrote:
Does this mean that we can't bind to IPv4 and IPv6 separately on Linux
to not get v6 mapped v4 addresses?
I think the mapped addresses are only seen when a wildcard IPv6 bind is
done. If you bind to a non-wildcard IPv4 or IPv6 address, you
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
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
do)
So this
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 saying, use ipv6: and bind to
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/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
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
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 work
Hi Jeremy,
Yes from memory, only one BindAddress can currently be used, but I can see
that multiple qaddresses might be usefule, and prob not too hard to
implement. I will look when I am back on Nov 4.
Cheers.
On Tue, 29 Oct 2002 13:31, Hugh Irvine wrote:
Hello Jeremy -
I have copied this
Hugh crew,
From reading the docs, and my own testing, it looks like the BindAddress
parameter can only accept a single IP. As a result,
it looks like you're limited to either having radiator respond on all IPs,
or just on one. If this is not the case, someone please feel free to
correct me.
Title: BindAddress
Hello,
We are using Radiator 2.18.2 on RH6.2.
The BindAddress parameter works only on radius authentication but not accounting request.
We use tcpdump to check where has the packet gone, it said udp port radacct unreachable.
I have no idea how to solve it, can anyone give
Hello Harrison -
Could you please send me a copy of your Radiator configuration file (no
secrets) together with a complete trace 4. I would also like to see the
command line that you have used to start Radiator and the command line you
have used for radpwtst.
thanks
Hugh
On Monday 20
Hello Andy -
This is almost always an OS issue - it decides what interface to use,
not Radiator.
regards
Hugh
At 12:49 +0200 15/5/01, Andy De Petter wrote:
Hi,
I have a question, concerning the BindAddress to multiple
interfaces, on the same machine. When I don't bind Radiator to a
Hi,
I have a question, concerning the BindAddress to multiple interfaces, on
the same machine. When I don't bind Radiator to a specific interface,
it listens (by default) on -all- interfaces.
Now, when I have RADIUS requests coming in from NAS, on a virtual
interface, Radiator will always
Hello,
It seems that the BindAddress attribute, for SNMPAgent isn't working
properly on my site. I'm running Radiator 2.17.1, and I have this in my
configuration file, for my authentication radiator server:
SNMPAgent
Community public
BindAddress 192.168.1.97
Is it possible to bind to more than one IP address per installation?
--
-Jason J. Horton [EMAIL PROTECTED]
Fat Man in a Little Coat
Intercom Online Inc.
212.376.7440 | http://www.intercom.com
===
Archive at http://www.starport.net/~radiator/
Announcements on
Hello Jason -
On Fri, 04 Aug 2000, Jason J. Horton wrote:
Is it possible to bind to more than one IP address per installation?
No - but it is possible to run multiple copies of Radiator, each on a different
IP address and/or port number.
hth
Hugh
--
Radiator: the most portable, flexible
22 matches
Mail list logo
