|
Bugzilla – Full Text Bug Listing |
| Summary: | While ipv6 can be disabled for the browsers with difficulty yast2 always uses it causing dns problems for many users | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Forgotten User rWKKpJY5iO <forgotten_rWKKpJY5iO> |
| Component: | YaST2 | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | chacea, forgotten_--EoyBps8f, yzubkov |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | openSUSE 11.4 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User rWKKpJY5iO
2011-04-06 20:50:29 UTC
I forgot to mention that the ethx config option in yast did nothing either YAST still continues to try and use ipv6 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 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. 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 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. 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.) 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! 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. ;-) 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. 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 - Maybe, but you really need to tell that the "upstream" glibc developers. 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 Should this not be marked as upstream or duplicate of bug 684201? Which is back btw. Right. Actually a glibc bug. *** This bug has been marked as a duplicate of bug 684534 *** |