[Bug 685627] New: While ipv6 can be disabled for the browsers with difficulty yast2 always uses it causing dns problems for many users
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c0 Summary: While ipv6 can be disabled for the browsers with difficulty yast2 always uses it causing dns problems for many users Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i586 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: a.johnw@yahoo.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 The usual way of disabling ipv6 was to use kernal load appends. This doesn't seem to do anything any more. The kde flag also does not stop konqueror from using it. Firefox has to be stopped from it's own configuration facility. Despite the kernel load appends and a change to sysctl.conf which does prevent Konqueror from using it YAST2 continues to use ipv6. This causes dns problems on many isp's when updates etc are run and they take for ever as a result - 18hrs and it didn't complete. This made worse by the fact that yast2 assumes the server is busy and extends the retry delay times. While all of this is going on both firefox and konqueror working on ipv4 can access and download the update files with ease. There are too many to use this as an update fix. Reproducible: Always Steps to Reproduce: 1.Clean 11.4 install from downloaded dvd 2. Try updating via a network that has problems with dns via ipv6 - many do 3.Read the forums and see how often this crops up, google brings up 500,000 hits many asking for fixes on a number of suse releases. Actual Results: DNS problems prevent a full update from occurring in anything like a reasonable time. Expected Results: There should be a method within yast of disabling ipv6 on all web traffic even from itself. Users can't be expected to find the existing methods which do not bear any relationship to previous ones so info on the web is misleading. Yast seems to be applying patches as they are loaded. I assume that nothing really happens until it has all of the updates it needs otherwise this might lead to a broken system. As YAST stands if an update is provided I could not be sure of being able to install it with yast as it can take hours to even check for repository updates. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c1 --- Comment #1 from john woodhouse <a.johnw@yahoo.com> 2011-04-07 09:25:15 UTC --- I forgot to mention that the ethx config option in yast did nothing either YAST still continues to try and use ipv6 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c2 --- Comment #2 from john woodhouse <a.johnw@yahoo.com> 2011-04-07 09:33:51 UTC --- Additionally I chose not to use the net wizard on install. My router was plugged and active when I carried out the install. Previous releases prior to 11 have looked after this aspect during installation. Long term it may be possible to determine if ipv6 dns is fully functional automatically in situations like this. I also note attention to modems and signing in to isp's. Few people use them these days so the router invariably looks after that aspect. This especially applies to longer term users due to past difficulties associated with logging in to typical isp's from linux. John -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c3 Yaroslav Zubkov <yzubkov@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yzubkov@gmail.com --- Comment #3 from Yaroslav Zubkov <yzubkov@gmail.com> 2011-04-23 16:57:34 UTC --- I agree that this is a pretty severe issue with Yast. In the meantime you can fix this issue by either using Google public DNS (add two nameserver entries to /etc/resolv.conf), or better yet switch to Fedora or Ububtu. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c5 --- Comment #5 from Michael Schröder <mls@novell.com> 2011-05-13 11:53:55 UTC --- Fedora won't help you as this is not a YaST but a glibc problem. See bug #684201 and bug #684534. Also see https://bugzilla.redhat.com/show_bug.cgi?id=459756 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c6 --- Comment #6 from Yaroslav Zubkov <yzubkov@gmail.com> 2011-05-13 17:34:56 UTC --- Fedora does help, I am running FC14 and I have glibc-2.13-1 and that does not prevent package manager to connect to internet and get updates. I understand that using Fedora is not fixing an issue, but it is the best way to avoid it. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c7 --- Comment #7 from Michael Schröder <mls@novell.com> 2011-05-16 09:47:17 UTC --- Maybe yum doesn't use libcurl to download data, but you'll still have delays in many other programs. (That is, if they don't have a patch for this in their glibc. Maybe they do.) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c8 --- Comment #8 from Yaroslav Zubkov <yzubkov@gmail.com> 2011-05-19 02:30:20 UTC --- Just wanted to clarify my previous comment. When originally installed, Fedora 14 ships with GLIBC-2.12.90-17(i686). Package manager/yum work as expected. If you decide not to update your system, you will be fine. But if you do update (a reasonable assumption), they push GLIBC-2.13.1 on you and next time you run an update it curses at you with "Errors were encountered while downloading packages.". Funny how you can try to run from IPv6 but you can't hide. I demand my IPv4 back! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c9 --- Comment #9 from john woodhouse <a.johnw@yahoo.com> 2011-05-24 16:54:43 UTC --- I may as well add that for one reason or another I was poking about on windoze vista the other day. Guess what it can choose to use ipv6 or ipv4 according to performance and of course this is post install. This looks to be done on the fly so it can switch at any time. Opensuse may have been the first to release ipv6 functionality many moons ago but it clearly isn't really ipv6 ready on this basis. Suse.de released and ungraded all users to ipv6. The result was that many users had no web access at all. Mine worked but oh so very very slowly. At the time they mentioned tunneling and it looks like my isp does support it but it's a lot slower these days. There is a very recent .gov.uk paper pointing out that there are so few ipv6 servers about that full roll out will probably take at least a further 2 years. It also points out that as far as many isp's are concerned there is no need to change to ipv6 as they can manage more users in other ways. I assume this means that they will use sub net techniques just as a single ip can service many pc's on the users end of the line. So putting it bluntly an install fix is just a patch really as at some point it will roll out and probably while ipv4 is still in use. Windoze looks to be able to cope now. Lixux can't. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c10 --- Comment #10 from john woodhouse <a.johnw@yahoo.com> 2011-05-24 17:02:49 UTC --- ;-) I should have said few ipv6 servers about world wide in case anyone is thinking this is a uk thing. While google has opened up an ipv6 service to the public isn't this a wonderful way of them gathering usage info - just as some routers can have there auto dns detection pirated. They are doing it legally. Not that I care but it is a probable side effect. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c11 --- Comment #11 from john woodhouse <a.johnw@yahoo.com> 2011-05-27 10:01:06 UTC --- One further note. Nosing around on windoze vista recently I noticed that it appears to be able to use either ipv4 or ipv6 on the fly and will choose according to performance. Now that really is ipv6 ready. John - -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c12 --- Comment #12 from Michael Schröder <mls@novell.com> 2011-05-27 10:13:06 UTC --- Maybe, but you really need to tell that the "upstream" glibc developers. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c13 --- Comment #13 from john woodhouse <a.johnw@yahoo.com> 2011-06-06 14:33:49 UTC --- As a check of comments elsewhere that yast does contain a global ipv6 disable which I have used I reset my routers dns to the isp provided defaults. One update via yast worked but 2 following ones failed to connect to the server in time. I reset the dns to google and it works again. Problem though as I'm in the uk all web access is has a longish pregnant pause before the web page comes up. When I have time I will take a closer look at vista to try and determine if what appears to be their does actually work. Even if it doesn't it does show intent and at this point in time given the very low number of ipv6 servers about it doesn't really matter if it doesn't work. John -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c14 --- Comment #14 from Sven Burmeister <sven.burmeister@gmx.net> 2011-11-21 16:34:27 UTC --- Should this not be marked as upstream or duplicate of bug 684201? Which is back btw. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=685627 https://bugzilla.novell.com/show_bug.cgi?id=685627#c15 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #15 from Michael Andres <ma@suse.com> 2012-03-28 08:36:50 CEST --- Right. Actually a glibc bug. *** This bug has been marked as a duplicate of bug 684534 *** http://bugzilla.novell.com/show_bug.cgi?id=684534 -- 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