that is nearly as clear and to the point as 'ipv6_enable'.
do
do Another reason I lean to not using xxx_enable is that an rc.d knob
do cannot control enabling/disabling the IPv6 functionality actually.
do It was true even when we were using the network_ipv6 script.
do
do But that's equally true
actully too lazy to see why it had really been added.
See my answer to Hiroki. Since there was no clear consensus to keep
ipv6_enable I agree to allow it to stay deprecated.
I wouldn't want to have a link-local address on my non-loopback
interfaces working unless I asked for them. That's why we had
*do* like a single rc.conf knob (ipv6_enable) for
the top level IPv6 functionality - even if it doesn't do a 100% job.
Thanks for your response. Do you think the compromise that I suggested
in my response to Kevin, enabling SLAAC for the interface if DHCP is in
use for IPv4 is reasonable?
I
is a bad idea.
On the other hand, I *do* like a single rc.conf knob (ipv6_enable) for
the top level IPv6 functionality - even if it doesn't do a 100% job.
Thanks for your response. Do you think the compromise that I suggested
in my response to Kevin, enabling SLAAC for the interface if DHCP
no reason not to use them to enable or disable functionality
whether
do ob it involves a script in rc.d or not. The idea is to have a clear,
do ob obvious way to enable or disable functionality. I see nothing in
Hiroki's
do ob proposal that is nearly as clear and to the point as 'ipv6_enable'.
do
ipv6_enable just for the purpose. ipv6_enable=NO never
means disabling IPv6 functionality in the kernel, and it will
cause people tend to think IPv6 is disabled completely.
If we want to disable ifconfig_IF_AF lines in a handy manner,
implementing ifconfig_DEFAULT_AF is more
or disable functionality
whether
do ob it involves a script in rc.d or not. The idea is to have a clear,
do ob obvious way to enable or disable functionality. I see nothing in
Hiroki's
do ob proposal that is nearly as clear and to the point as 'ipv6_enable'.
do
do Another reason I lean
that completely
unnecessary for the common case (RA).
However, I disagree with using the
name ipv6_enable just for the purpose. ipv6_enable=NO never
means disabling IPv6 functionality in the kernel, and it will
cause people tend to think IPv6 is disabled completely.
Throughout
no reason not to use them to enable or disable functionality
whether
do ob it involves a script in rc.d or not. The idea is to have a clear,
do ob obvious way to enable or disable functionality. I see nothing in
Hiroki's
do ob proposal that is nearly as clear and to the point as 'ipv6_enable'.
do
, functional solution. Making
ipv6_enable=NO really turn off IPv6 looks like the ideal answer, but I
think it's up to Hiroki to determine if it is feasible. I did my last
kernel programming on VMS about 25 years ago and it was in assembly and
BLISS, not C.
I am just a bit uncomfortable
John Hay j...@meraka.org.za wrote
in 20100405083056.ga8...@zibbi.meraka.csir.co.za:
jh These questions actually start more questions for me. :-) Maybe we should
jh also think from the user perspective and list a few use cases and what a
jh user need to put in rc.conf to make that work?
jh
jh
if ipv6_enable
was NO on boot. You had to change the sysctl (manually) and then down
up the interface(s) leading to serivce interruption even for IPv4.
There is a PR about it if you want to check.
In the past there was no way to express enable it on my wired interface
but not on my wireless or enable
,
ob obvious way to enable or disable functionality. I see nothing in Hiroki's
ob proposal that is nearly as clear and to the point as 'ipv6_enable'.
Another reason I lean to not using xxx_enable is that an rc.d knob
cannot control enabling/disabling the IPv6 functionality actually.
It was true
a single rc.conf knob (ipv6_enable) for
the top level IPv6 functionality - even if it doesn't do a 100% job.
Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
the various opinions regarding having RA on by default, and
have reconsidered my position. Therefore I'd like to offer a compromise.
What I'm after is that modulo the need to toggle ipv6_enable if a user
has an interface configured with IPv4 that the same interface should
just work with IPv6. Given
in rc.d or not. The idea is to have a clear,
ob obvious way to enable or disable functionality. I see nothing in Hiroki's
ob proposal that is nearly as clear and to the point as 'ipv6_enable'.
Another reason I lean to not using xxx_enable is that an rc.d knob
cannot control enabling
is a bad idea.
On the other hand, I *do* like a single rc.conf knob (ipv6_enable) for
the top level IPv6 functionality - even if it doesn't do a 100% job.
Thanks for your response. Do you think the compromise that I suggested
in my response to Kevin, enabling SLAAC for the interface if DHCP
not to use them to enable or disable functionality whether
ob it involves a script in rc.d or not. The idea is to have a clear,
ob obvious way to enable or disable functionality. I see nothing in
Hiroki's
ob proposal that is nearly as clear and to the point as 'ipv6_enable'.
Another
what I agree and disagree again:
a. I agree that it is useful to have a knob for disabling all of
ifconfig_IF_ipv6 handling. However, I disagree with using the
name ipv6_enable just for the purpose. ipv6_enable=NO never
means disabling IPv6 functionality in the kernel
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hrs@ has been doing some great work on bringing IPv6 support up to par
with IPv4, and deserves a lot of credit for that work. Included in those
changes were changes to the traditional semantics of how ipv6_enable
works. That variable
Doug Barton do...@freebsd.org wrote
in 4bb70e1e.3090...@freebsd.org:
do 1. There should be an ipv6_enable knob to easily turn IPv6 configuration
do on and off when INET6 is in the kernel. I think the value of this kind
do of knob is obvious, but I'd be happy to elaborate if that is necessary
be configured.
On 04/03/10 04:51, Hiroki Sato wrote:
Doug Barton do...@freebsd.org wrote
in 4bb70e1e.3090...@freebsd.org:
do 1. There should be an ipv6_enable knob to easily turn IPv6 configuration
do on and off when INET6 is in the kernel. I think the value of this kind
do of knob is obvious
desk in Berkeley.
I agree with one of Doug's points and one of Hiroki's.
On 04/03/10 04:51, Hiroki Sato wrote:
Doug Barton do...@freebsd.org wrote
in 4bb70e1e.3090...@freebsd.org:
do 1. There should be an ipv6_enable knob to easily turn IPv6 configuration
do on and off when INET6
23 matches
Mail list logo
