[Bug 539869] New: openSUSE 11.2 M7: CONFIG_IPV6=y (only) on x86_64

http://bugzilla.novell.com/show_bug.cgi?id=539869 Summary: openSUSE 11.2 M7: CONFIG_IPV6=y (only) on x86_64 Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 7 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: AxelKoellhofer@web.de QAContact: qa@suse.de Found By: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; de) Presto/2.2.15 Version/10.00 On Milestone 7 IPv6 is compiled directly into the kernel on x86_64: grep -i ipv6 /boot/config-2.6.31-rc9-7-default CONFIG_IPV6=y CONFIG_IPV6_PRIVACY=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y # CONFIG_IPV6_OPTIMISTIC_DAD is not set CONFIG_IPV6_MIP6=m CONFIG_IPV6_SIT=m CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_IPV6_SUBTREES=y # CONFIG_IPV6_MROUTE is not set CONFIG_IP_VS_IPV6=y # IPv6: Netfilter Configuration CONFIG_NF_CONNTRACK_IPV6=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m or for the "desktop" kernel: grep -i ipv6 /boot/config-2.6.31-rc9-7-desktop CONFIG_IPV6=y CONFIG_IPV6_PRIVACY=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y # CONFIG_IPV6_OPTIMISTIC_DAD is not set CONFIG_IPV6_MIP6=m CONFIG_IPV6_SIT=m CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_IPV6_SUBTREES=y # CONFIG_IPV6_MROUTE is not set CONFIG_IP_VS_IPV6=y # IPv6: Netfilter Configuration CONFIG_NF_CONNTRACK_IPV6=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m However, on i586 ipv6 is configured as a module: grep ipv6 -i /boot/config-2.6.31-rc9-7-default CONFIG_IPV6=m CONFIG_IPV6_PRIVACY=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y # CONFIG_IPV6_OPTIMISTIC_DAD is not set CONFIG_IPV6_MIP6=m CONFIG_IPV6_SIT=m CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y CONFIG_IPV6_SUBTREES=y # CONFIG_IPV6_MROUTE is not set CONFIG_IP_VS_IPV6=y # IPv6: Netfilter Configuration CONFIG_NF_CONNTRACK_IPV6=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m Now there is a potential problem arising (especially for less experienced users). First of all, only few users use IPv6 (at least exclusively) in their LAN (and then ones who do are most certainly more experienced ones), but still a lot of users have old harcware (i.e. an old router) not capable of IPv6 and if they ask for help in one of the many internet fora, the easy answer (and very often the one solving the problem) was "go to YaST, disable IPv6 with that nice little checkbox you will find in the global networking options and reboot your machine". AFAIK this disables IPv6 by setting install ipv6 /bin/true in /etc/modprobe.d/ipv6 (or on 11.2 /etc/modprobe.d/50-ipv6.conf) With ipv6 dircetly compiled into the kernel, this will not work any longer and one would have to try explaining an unexperienced user how to disable ipv6 via sysctl (I think at least it is possible via sysctl, but TBH I never did this before, so it's just a guess). Now while x86_64 capable hardware is getting more and more popular, IPv6 is still not very wide spread and still causes more problems than it gives any benefits to the "average" user. IMHO it would be more prudent to always configure IPv6 as a module at least giving the users a simple way in disabling it if they run into trouble related to IPv6. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 User AxelKoellhofer@web.de added comment http://bugzilla.novell.com/show_bug.cgi?id=539869#c1 --- Comment #1 from Axel Köllhofer <AxelKoellhofer@web.de> 2009-09-20 10:30:00 MDT --- (In reply to comment #0)
With ipv6 dircetly compiled into the kernel, this will not work any longer and one would have to try explaining an unexperienced user how to disable ipv6 via sysctl (I think at least it is possible via sysctl, but TBH I never did this before, so it's just a guess).
To answer that question myself (and save me from some self made embarassement). The "sledgehammer"-workaround would be to add ipv6.disable=1 as a boot parameter. Still this had to be added to the entries in /boot/grub/menu.lst for the running kernel (to take effect after rebooting) and to the APPEND options in /etc/sysconfig/bootloader to have it as a persistent option which will stay there even after kernel updates. Certainly easier than changing/adding some the settings via /etc/sysctl.conf but still not very convincing compared to the easy fix via YaST when ipv6 is compiled as a module. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 User mcarrion@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=539869#c2 Mario Carrion <mcarrion@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mcarrion@novell.com --- Comment #2 from Mario Carrion <mcarrion@novell.com> 2009-10-13 13:44:40 MDT --- FYI. M8 was compiled the same way. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 User rlutzinger@comcast.net added comment http://bugzilla.novell.com/show_bug.cgi?id=539869#c3 Randy Lutzinger <rlutzinger@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rlutzinger@comcast.net --- Comment #3 from Randy Lutzinger <rlutzinger@comcast.net> 2009-10-15 12:34:33 MDT --- Just updated to 11.2 RC1 and the problem is still there.
From "config-2.6.31.3-1-desktop":
CONFIG_IPV6=y This causes my internet speed on Firefox to be extremely slow. I was able to default FF to disable IPV6, but I also run Chromium from time to time and as far as I know there's no way to disable IPV6 there. It's also causing slowdowns in Kontact when I'm fetching feeds. Hope this will be fixed before the final release. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 User maddler@maddler.net added comment http://bugzilla.novell.com/show_bug.cgi?id=539869#c4 Gianlorenzo Cipparrone <maddler@maddler.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maddler@maddler.net --- Comment #4 from Gianlorenzo Cipparrone <maddler@maddler.net> 2009-10-27 15:08:03 MDT --- Hello all, looks like we've got same "issue" on i686 as well. Linux cruciferous 2.6.31.3-1-desktop #1 SMP PREEMPT 2009-10-08 00:27:25 +0200 i686 athlon i386 GNU/Linux Consider that in many cases residential routers will assign an IPV6 address even if the ISP isn't actually handling IPV6 routing. Same situation form many access points. Entry level users and newbies could find themselves in a situation where networking is not working at all and no way to easily fix that. Also, there is an option in yast which is supposed to stop/disable IPV6. Having it working despite user configuration will make users confused. Regards -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 User jeffm@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=539869#c5 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |ASSIGNED AssignedTo|kernel-maintainers@forge.pr |jeffm@novell.com |ovo.novell.com | --- Comment #5 from Jeff Mahoney <jeffm@novell.com> 2009-11-12 09:11:28 MST --- Wait, so there is an option in yast to disable ipv6 and it isn't working? That's a different issue entirely. The inconsistency between flavors certainly should be addressed, but that should be ok in an update. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 --- Comment #6 from Axel Köllhofer <AxelKoellhofer@web.de> 2009-11-15 12:02:21 UTC --- Well, as stated in my opening comment, if one uses YaST to deactivate IPv6, this is done by creating a file /etc/modprobe.d/50-ipv6.conf with the following content: install ipv6 /bin/true If IPv6 is not compiled as a module, this will not have any effect and one would have to use the boot parameter "ipv6.disable=1" to deactivate ipv6. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 --- Comment #7 from Axel Köllhofer <AxelKoellhofer@web.de> 2009-11-15 14:27:37 UTC --- after having a thought or two about this issue (and presuming that CONFIG_IPV6=y was set for the same of speeding up the boot process) it looks to me as there are three potentiel ways to solve this issu. a) "Back to the roots" Setting CONFIG_IPV6=m on all flavors and keeping the way YaST handles disabling IPv6 via blacklisting the module. If CONFIG_IPV6=y was set for speeding up the boot process (amongst others, i.e. ext3 has been compiled into the kernel also since 11.2), this might be undesired. b) Making disabling IPv6 via YaST "dumb but effective" When disabling/enabling IPv6 via YaST, the YaST-mdule will disable/enable the module ipv6 via /etc/modprobe.d/50-ipv6.conf and the boot parameter "ipv6.disable=1" will be appended/removed from the respective lines in /boot/grub/menu.lst and /etc/sysconfig/bootloader. The only drawback will be a warning very early on boot if the system is booting a kernel-flavor with CONFIG_IPV6=m set, informing the user of an unknown parameter which will be ignored. c) Enabling YaST to make an "intelligent" choice: When disabling/enabling IPv6 via YaST, the YaST-module will search all /boot/config-*version*-*flavor* files for CONFIG_IPV6 and modify menu.lst/etc/sysconfig/bootloader only for those flavors with CONFIG_IPV6=y, while setting "install ipv6 /bin/true" if at least one of the installed flavors has CONFIG_IPV6=m set. However, this would have to be repeated automatically if the user installs another kernel-flavor. Personally, I would vote for b) at least as a short term solution, but these are just a few thoughts by someone from the "outside". -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 http://bugzilla.novell.com/show_bug.cgi?id=539869#c8 Diego Ercolani <diego.ercolani@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |diego.ercolani@gmail.com --- Comment #8 from Diego Ercolani <diego.ercolani@gmail.com> 2009-12-17 09:08:27 UTC --- My 2¢: There is an entry in proc filesystem: /proc/sys/net/ipv6/conf/all/disable_ipv6 if you send a echo "1" > /proc/sys/net/ipv6/conf/all/disable_ipv6 you can disable runtime the support to IPV6 and reeneable with: echo "0" > /proc/sys/net/ipv6/conf/all/disable_ipv6 so it seems that all the sysconfig structure in OpenSuSE 11.2 to enable/disable the IPV6 support should be revised. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 http://bugzilla.novell.com/show_bug.cgi?id=539869#c9 Diego Ercolani <diego.ercolani@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 7 |Final --- Comment #9 from Diego Ercolani <diego.ercolani@gmail.com> 2009-12-17 09:09:19 UTC --- My 2¢: There is an entry in proc filesystem: /proc/sys/net/ipv6/conf/all/disable_ipv6 if you send a echo "1" > /proc/sys/net/ipv6/conf/all/disable_ipv6 you can disable runtime the support to IPV6 and reeneable with: echo "0" > /proc/sys/net/ipv6/conf/all/disable_ipv6 so it seems that all the sysconfig structure in OpenSuSE 11.2 to enable/disable the IPV6 support should be revised. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=539869 http://bugzilla.novell.com/show_bug.cgi?id=539869#c10 Thomas Richard <thomas9999@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas9999@gmail.com --- Comment #10 from Thomas Richard <thomas9999@gmail.com> 2009-12-21 16:52:53 UTC --- For your interest, this also affects Ubuntu and Fedora: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/417757 https://bugzilla.redhat.com/show_bug.cgi?id=505105 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=539869 https://bugzilla.novell.com/show_bug.cgi?id=539869#c11 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #11 from Jeff Mahoney <jeffm@novell.com> 2010-12-01 14:23:31 UTC --- Closing as WONTFIX. There are a few reasons why we have CONFIG_IPV6=y. Interface bonding has hooks into the ipv6 code that make it dependent on it. If bonding gets loaded, ipv6 gets loaded. If you disable ipv6, then bonding can't be loaded at all. Another effect is that the tunables for disabling it must be used /before/ the network interfaces are activated or it will use router autoconfiguration as the interfaces are brought up. Getting the timing right is complicated and error prone, so it just works better to build it in and use the sysctl to disable it before the network is brought up. For more of the discussion, visit the opensuse-kernel archive: http://lists.opensuse.org/opensuse-kernel/2010-11/msg00071.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com