http://bugzilla.novell.com/show_bug.cgi?id=616765
http://bugzilla.novell.com/show_bug.cgi?id=616765#c16
--- Comment #16 from Marius Tomaschewski
Is that still true? I thought that particular issue (the IPv6-goes-away and firefox-crashes bug) was fixed.
IN any case, I'd much rather see "you may have to restart some networking applications if you are disabling IPv6" instead of "reboot your computer".
Short: The problem is, that "some networking applications" is an insufficient action description and may be also technically not sufficient. Generally, it should be possible to handle it completely manually... it should be not even strictly required to restart the network when the disable_ipv6 way is effective (as on 11.3), the kernel will then remove all ipv6 addresses itself... But on older systems/kernels, ipv6 may be a module and yast2 disables the ipv6 module loading. It is not possible to unload the module -- only a reboot works here. It is not easy even for advanced user with disable_ipv6, because there are several side effects / corner cases. There are not only GUI applications like firefox, but also several services, possibly inclusive of X11, that may have bound ipv6 ports or even handle ipv4 connections through the ipv6 socket and at least side effects have to be taken into account. Last but not least: the above dependencies for the applications may be also true for things running inside of the kernel. It may include also another type of problems: see bug 559170. Another issue is: disabling ipv6 usually introduces more problems than it solves and just delays the correct solutions. It was never required for me to disable ipv6 -- except for tests. Anyway: fixed for me, fix will be picked up in the next 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.