On Wed, Apr 07, 2010 at 09:23:39PM +1000, Andrew Byrne wrote: > > I'd like to introduce a patch to the base-files Makefile that will run a sed > on the sysctl.conf file to remove the comment if IPv6 routing is required.
IPv6 is a bit more complicated than IPv4. I would assume for now that people routing routers would know particularities of it, whereas a wireless bridge for IPv6 is still easy enough. > > Checking the status of CONFIG_PACKAGE_kmod_ipv6 or CONFIG_IPV6 probably > isn't going to be sufficient, as not every device running OpenWrt is a > router, and with IPv6, enabling forwarding can prevent the device from using > autoconfiguration. IPv4 doesn't have this problem, so enabling forwarding > by default doesn't cause any issues. Wireless bridges do not need IPv6 forwarding. There is also an autoconf setting for ipv6 on interfaces. Teh defauilt depends on forwarding. IMHO having an IPv6 with one interface on autoconfig, the others not is somewhat rare, esp. in the absences of NAT (IMHO a good thing). Besides, I would not consider the autoconf disabled as a problem, more as a feature (from the policy point of view, it is standard conform and documented, so it can only be a feature ;-) > > Maybe there should be another option such as CONFIG_IPV6_ROUTER. This would > be used initially to ensure the sysctl.conf file is correct, but could also > be used in the future where other decisions need to be made on the basis of > whether or not the device will be routing IPv6. > > Of course this only affects manually compiled images, and anyone using > prebuilt images would still need to make this change manually (possibly via > a LuCI IPv6 config page when I finally get around to writing one!). > > I'm interested in your feedback. The presence of radvd or quagga or just any routing daemon would be a hint for a IPv6 router. However, I personally do not like software policy induced side effect on interface settings. By experience I never belong to that majority said to benefit from it. If you really want, make it fine grained. For example: - define the "upstream" interface and choose autoconf or manual - create a default radvd config, with the option of not touching anything. - define the other interfaces, optionally as autoconf from the local radvd. Bye, Joerg
signature.asc
Description: Digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
