Carlos E. R. wrote:
The Thursday 2005-01-27 at 15:49 -0700, Robert A. Rawlinson wrote:
I just recently installed Suse 9.1 on an older pc. I have most everything working now but I have a problem when the browsers (Mozilla 1.7 & Konquarer) try to convert an address to the ip address. It acts like something has to time out and then it goes ok until it has to resolve another address. I set up the gateway and it does eventually get the ip address. Does anyone have any idea where to start looking? Bob Rawlinson
Known thing. Disable ipv6. Look at the SuSE database (SDB) for instructions.
I believe this is supposed to be resolved in Mozilla 1.7.5 (maybe as early as 1.7.3), but alas the problem also exists with other software, notably lukemftp and whois. When IPv6 is enabled, a hostname search first tries to find an IPv6 address. The problem occurs, I believe, only when the hostname actually does have an IPv6 address. With lukemftp, an immediate attempt is made to connect to that version 6 address (presumably it would therefore work if IPv6 was properly configured, which I never did). Mozilla, Konqueror and whois seem to be different matters; all of them seem unable somehow to handle hosts which have an IPv6 address. Maybe it is the same thing as lukemftp, maybe it is something else, I do not know. As you have noted, however, disabling IPv6 is the easiest solution -- certainly far easier than configuring IPv6 tunnelling :-) This brings up the immediate question: why is IPv6 automatically enabled when SuSE 9.x is installed, but configuration is something which must be done only after the installation is complete? I do not recall seeing anything anywhere in YaST where IPv6 can be configured in any way. Given the complexity of doing things like IPv6 tunnelling, I would think the default should be to have IPv6 disabled at installation time.