Browsers take a long time to resolve ip address
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
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
This usually indicates that the primary dns server was unreachable and timed out then the secondary was contacted. Do pings take a long time to resolve also? Can you ping/telnet to the primary name server for this box? Jeff
Jeffrey Laramie wrote:
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
This usually indicates that the primary dns server was unreachable and timed out then the secondary was contacted. Do pings take a long time to resolve also? Can you ping/telnet to the primary name server for this box?
Jeff
Yes ping works and it does not have any delay. However the gateway is a router box and i put that in as the gateway. Then the router has the ip of the 'real' dns server and gateway. Would that make any difference? Bob Rawlinson
On Friday 28 January 2005 10:59, Robert A. Rawlinson wrote:
Jeffrey Laramie wrote:
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
This usually indicates that the primary dns server was unreachable and timed out then the secondary was contacted. Do pings take a long time to resolve also? Can you ping/telnet to the primary name server for this box?
Jeff
Yes ping works and it does not have any delay. However the gateway is a router box and i put that in as the gateway. Then the router has the ip of the 'real' dns server and gateway. Would that make any difference? Bob Rawlinson
You've had a couple other answers that indicate ipv6 might need to be disabled. Try that. Also, in your configuration does the router box provide dns for a lan? Are other boxes in the lan having problems resolving names or is it just this one? Jeff
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. -- Cheers, Carlos Robinson
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.
The Friday 2005-01-28 at 09:45 -0600, Darryl Gregorash wrote:
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.
I believe 9.2 has a setting in yast to dissable ipv6, but 9.1 doesn't. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Friday 2005-01-28 at 09:45 -0600, Darryl Gregorash wrote:
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.
I believe 9.2 has a setting in yast to dissable ipv6, but 9.1 doesn't.
I hope this also disables the place in SuSEfirewall2 where ip6_tables is loaded anyway, even if the ipv6 module isn't loaded (that's in 9.0, I don't know 9.1 because I have never installed it). Perhaps the powers that be might consider backporting this feature to 9.0 and 9.1, and issuing an update for all appropriate packages. This whole issue begs the question: will the next version of SuSE also have an option to disable ipv4, for those who only have an ipv6 presence? With both versions enabled, hopefully YaST will also offer options for configuring ipv6-to-ipv4 tunnelling. That stuff isn't all that exotic, but it still baffles me, because I don't have the patience to work through the documentation.
The Saturday 2005-01-29 at 12:53 -0600, Darryl Gregorash wrote:
I believe 9.2 has a setting in yast to dissable ipv6, but 9.1 doesn't.
I hope this also disables the place in SuSEfirewall2 where ip6_tables is loaded anyway, even if the ipv6 module isn't loaded (that's in 9.0, I don't know 9.1 because I have never installed it).
Perhaps. I suppose so, but I don't know, I don't have 9.2 yet.
Perhaps the powers that be might consider backporting this feature to 9.0 and 9.1, and issuing an update for all appropriate packages.
You can wait sitting down. X'-) (Spanish saying, meaning don't expect it)
This whole issue begs the question: will the next version of SuSE also have an option to disable ipv4, for those who only have an ipv6 presence?
I doubt it, at least, not yet. ipv6 is still experimental, work in progress, and I don't think every linux program would work. -- Cheers, Carlos Robinson
At 12:15 PM 30/01/2005, Carlos E. R. wrote:
The Saturday 2005-01-29 at 12:53 -0600, Darryl Gregorash wrote:
\cut
This whole issue begs the question: will the next version of SuSE also
have an
option to disable ipv4, for those who only have an ipv6 presence?
I doubt it, at least, not yet. ipv6 is still experimental, work in progress, and I don't think every linux program would work.
--
Sorry but, IPV6 is very much up, alive, and well. A number of the international pipes are running it as their main protocol. That doesn't sound like experimental to me. scsijon
The Monday 2005-01-31 at 13:36 +1100, scsijon wrote:
Sorry but, IPV6 is very much up, alive, and well. A number of the international pipes are running it as their main protocol. That doesn't sound like experimental to me.
Any of them use Linux? My understanding was that it is experimental in Linux. I'd be happy to know that this is not so. -- Cheers, Carlos Robinson
On Fri, 28 Jan 2005 02:58:10 +0100 (CET), Carlos E. R. <robin1.listas@tiscali.es> 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.
-- Cheers, Carlos Robinson
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Ok, same problem here (9.1). I found the article in SDB, and I made the changes in /etc/modprobe.conf. Now, as I do not want to reboot, is just restarting the network will do the trick. I tried rmmod ipv6, but it says it's in use. Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Sunny wrote:
Now, as I do not want to reboot, is just restarting the network will do the trick. I tried rmmod ipv6, but it says it's in use.
There are a few modules that depend on ipv6, two being installed by the SuSEfirewall2 script. 'lsmod | grep ipv6' to find them all. ipv6 will be the last one to be removed.
On Fri, 28 Jan 2005 13:30:32 -0600, Darryl Gregorash <raven@accesscomm.ca> wrote:
Sunny wrote:
Now, as I do not want to reboot, is just restarting the network will do the trick. I tried rmmod ipv6, but it says it's in use.
There are a few modules that depend on ipv6, two being installed by the SuSEfirewall2 script. 'lsmod | grep ipv6' to find them all. ipv6 will be the last one to be removed.
Only ipv6 module is loaded. sunny@linux:~> lsmod | grep ipv6 ipv6 236800 122 sunny@linux:~> su Password: linux:/ # rmmod ipv6 ERROR: Module ipv6 is in use Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Sunny wrote:
There are a few modules that depend on ipv6, two being installed by the SuSEfirewall2 script. 'lsmod | grep ipv6' to find them all. ipv6 will be the last one to be removed.
Only ipv6 module is loaded.
sunny@linux:~> lsmod | grep ipv6 ipv6 236800 122 sunny@linux:~> su Password: linux:/ # rmmod ipv6 ERROR: Module ipv6 is in use
Mea culpa; the ip6tables modules are named just that, ip6tables_*. You could try an extended regexp search (-E option in grep), or just run lsmod and sort through the list. Module dependencies are listed in the fourth column.
On Fri, 28 Jan 2005 13:57:08 -0600, Darryl Gregorash <raven@accesscomm.ca> wrote:
Mea culpa; the ip6tables modules are named just that, ip6tables_*. You could try an extended regexp search (-E option in grep), or just run lsmod and sort through the list. Module dependencies are listed in the fourth column.
linux:/ # lsmod | grep -i ip ipv6 236800 134 linux:/ # This is the only one I can suspect. God, I hate to reboot. Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Sunny wrote:
On Fri, 28 Jan 2005 13:57:08 -0600, Darryl Gregorash <raven@accesscomm.ca> wrote:
Mea culpa; the ip6tables modules are named just that, ip6tables_*. You could try an extended regexp search (-E option in grep), or just run lsmod and sort through the list. Module dependencies are listed in the fourth column.
linux:/ # lsmod | grep -i ip ipv6 236800 134 linux:/ #
This is the only one I can suspect. God, I hate to reboot.
Sunny
No firewall on that system? There should be about 9 modules named ip* just from iptables alone, nevermind NAT and connection tracking, and nevermind ip6tables. If ipv6 is enabled, then the system should automatically configure a default ipv6 address for your network devices, and I think that should result in a few more modules being loaded. In any event, "lsmod | grep ip" should yield far more than just ipv6. BTW, I discovered just today that, at least in 9.0, SuSEfirewall2 will load a couple of ip6tables modules even if ipv6 is not loaded. It used modprobe to do so, and there is no complaint from the system. If I try to load the same module using insmod, I get "unresolved symbol" errors. Very strange. I'm a bit curious about the output you're posting here; when I run lsmod, I get things like iptable_nat 15374 1 [ip_nat_ftp] This shows that this module depends on ip_nat_ftp, so the latter cannot be removed until iptable_nat (and any other modules depending on it) is removed.
On Fri, 28 Jan 2005 15:10:59 -0600, Darryl Gregorash <raven@accesscomm.ca> wrote:
Sunny wrote:
On Fri, 28 Jan 2005 13:57:08 -0600, Darryl Gregorash <raven@accesscomm.ca> wrote:
Mea culpa; the ip6tables modules are named just that, ip6tables_*. You could try an extended regexp search (-E option in grep), or just run lsmod and sort through the list. Module dependencies are listed in the fourth column.
linux:/ # lsmod | grep -i ip ipv6 236800 134 linux:/ #
This is the only one I can suspect. God, I hate to reboot.
Sunny
No firewall on that system? There should be about 9 modules named ip* just from iptables alone, nevermind NAT and connection tracking, and nevermind ip6tables. If ipv6 is enabled, then the system should automatically configure a default ipv6 address for your network devices, and I think that should result in a few more modules being loaded. In any event, "lsmod | grep ip" should yield far more than just ipv6.
BTW, I discovered just today that, at least in 9.0, SuSEfirewall2 will load a couple of ip6tables modules even if ipv6 is not loaded. It used modprobe to do so, and there is no complaint from the system. If I try to load the same module using insmod, I get "unresolved symbol" errors. Very strange.
I'm a bit curious about the output you're posting here; when I run lsmod, I get things like
iptable_nat 15374 1 [ip_nat_ftp]
This shows that this module depends on ip_nat_ftp, so the latter cannot be removed until iptable_nat (and any other modules depending on it) is removed.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
This is my home desktop. It is by itself behind 2 other firewalls (the cable router, and one debian box), so the SuSEFirewall is not activated. And I can't believe there is no way to disable this ipv6 stuff without rebooting. I'm so tired to reboot winbozes all the day at work :) Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Sunny wrote:
On Fri, 28 Jan 2005 02:58:10 +0100 (CET), Carlos E. R. <robin1.listas@tiscali.es> 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.
-- Cheers, Carlos Robinson
Ok, same problem here (9.1). I found the article in SDB, and I made the changes in /etc/modprobe.conf.
Now, as I do not want to reboot, is just restarting the network will do the trick. I tried rmmod ipv6, but it says it's in use.
Sunny
I also found the article. I applied it and I rebooted. It didn't change it. I hope you have more luck. I am still trying to find a solution. Thanks for the suggestions folks. Bob Rawlinson
Robert A. Rawlinson wrote:
I also found the article. I applied it and I rebooted. It didn't change it. I hope you have more luck. I am still trying to find a solution. Thanks for the suggestions folks.
If you have enabled any of the IPv6 variables (such as IPV6_PRIVACY) in YaST, then the ipv6 module will be automatically loaded at boot time, regardless of what is set in modules.conf. You should probably fire up YaST and make sure all such variables are set to "no".
The Friday 2005-01-28 at 13:59 -0700, Robert A. Rawlinson wrote:
I also found the article. I applied it and I rebooted. It didn't change it. I hope you have more luck.
In '/etc/modprobe.conf.local' I have: install ipv6 /bin/true Notice that, contrary to intuition, "true" disables it. It has a good technical explanation, but of course, the result is not intuitive :-) Also, in '/etc/hosts' I disabled all addresses referring to ipv6, just in case: # special IPv6 addresses #::1 localhost ipv6-localhost ipv6-loopback #fe00::0 ipv6-localnet And there are two other settings in '/etc/sysconfig/SuSEfirewall2': FW_IPv6="" FW_IPv6_REJECT_OUTGOING="yes" And I don't remember anything else I did, except rebooting. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
And there are two other settings in '/etc/sysconfig/SuSEfirewall2':
FW_IPv6="" FW_IPv6_REJECT_OUTGOING="yes"
These must also be for 9.2 only; they aren't present in 9.0. Do you think I should forward all this thread to feedback@suse.com and ask them to packport it to 9.0 and 9.1? :-)
The Saturday 2005-01-29 at 13:02 -0600, Darryl Gregorash wrote:
And there are two other settings in '/etc/sysconfig/SuSEfirewall2':
FW_IPv6="" FW_IPv6_REJECT_OUTGOING="yes"
These must also be for 9.2 only; they aren't present in 9.0.
My 9.1 has them.
Do you think I should forward all this thread to feedback@suse.com and ask them to packport it to 9.0 and 9.1? :-)
This is already documented by them. As to backport those variables, it wouldn't work, I think. And it would be adding new features, and they don't do that. They keep the same version of packages, with security patches, not improvements (with vary few exceptions). -- Cheers, Carlos Robinson
Darryl Gregorash wrote:
Carlos E. R. wrote:
And there are two other settings in '/etc/sysconfig/SuSEfirewall2':
FW_IPv6="" FW_IPv6_REJECT_OUTGOING="yes"
These must also be for 9.2 only; they aren't present in 9.0.
Do you think I should forward all this thread to feedback@suse.com and ask them to packport it to 9.0 and 9.1? :-)
I found this on the suse web site. *SUSE Linux 9.1* (in connection with Kernel 2.6.x) includes the file /etc/modprobe.conf instead of /etc/modules.conf. If you want to disable IPv6 on a permanent basis in SUSE Linux 9.1, change the file /etc/modprobe.conf as follows: Change alias net-pf-10 ipv6 to alias net-pf-10 ipv6 install ipv6 /bin/true Bob Rawlinson
Robert A. Rawlinson wrote:
Darryl Gregorash wrote:
Carlos E. R. wrote:
And there are two other settings in '/etc/sysconfig/SuSEfirewall2':
FW_IPv6="" FW_IPv6_REJECT_OUTGOING="yes"
These must also be for 9.2 only; they aren't present in 9.0.
Do you think I should forward all this thread to feedback@suse.com and ask them to packport it to 9.0 and 9.1? :-)
I found this on the suse web site.
*SUSE Linux 9.1* (in connection with Kernel 2.6.x) includes the file /etc/modprobe.conf instead of /etc/modules.conf.
If you want to disable IPv6 on a permanent basis in SUSE Linux 9.1, change the file /etc/modprobe.conf as follows:
Change
alias net-pf-10 ipv6
to
alias net-pf-10 ipv6 install ipv6 /bin/true
Bob Rawlinson
I have a Suse 9.1 with the 2.4 kernal but I updated it to the 2.6 kernal. So I had both files mentioned. So I made the change in both files and rebooted. I still get the ipv6 and I still have the problem. Bob Rawlinson
Robert A. Rawlinson wrote:
Change
alias net-pf-10 ipv6
to
alias net-pf-10 ipv6 install ipv6 /bin/true
Bob Rawlinson
I have a Suse 9.1 with the 2.4 kernal but I updated it to the 2.6 kernal. So I had both files mentioned. So I made the change in both files and rebooted. I still get the ipv6 and I still have the problem. Bob Rawlinson
All I can suggest, again, is that you check /etc/sysconfig/sysctl to see if things like IPV6_PRIVACY are set to "yes". If any of them are (there are 2 in 9.0) then the ipv6 module will be loaded anyway, in /etc/init.d/boot.ipconfig, no matter what it says in your modules.conf or whatever it may be called.
Darryl Gregorash wrote:
Robert A. Rawlinson wrote:
Change
alias net-pf-10 ipv6
to
alias net-pf-10 ipv6 install ipv6 /bin/true
Bob Rawlinson
I have a Suse 9.1 with the 2.4 kernal but I updated it to the 2.6 kernal. So I had both files mentioned. So I made the change in both files and rebooted. I still get the ipv6 and I still have the problem. Bob Rawlinson
All I can suggest, again, is that you check /etc/sysconfig/sysctl to see if things like IPV6_PRIVACY are set to "yes". If any of them are (there are 2 in 9.0) then the ipv6 module will be loaded anyway, in /etc/init.d/boot.ipconfig, no matter what it says in your modules.conf or whatever it may be called.
I have checked and all those are correct. Still ipv6 IS running. I looked in /etc/sysconfig/sysctl and /etc/init.d/boot.ipconfig and I could see no where it should start ipv6. The system I have in Ohio did not have this problem. Only the system I have with me in Tucson Az. I think the DSL line back home handled the ipv6 but the WiFi I have here will not. Bob Rawlinson
Robert A. Rawlinson wrote:
Darryl Gregorash wrote:
Robert A. Rawlinson wrote:
Change
alias net-pf-10 ipv6
to
alias net-pf-10 ipv6 install ipv6 /bin/true
Bob Rawlinson
I have a Suse 9.1 with the 2.4 kernal but I updated it to the 2.6 kernal. So I had both files mentioned. So I made the change in both files and rebooted. I still get the ipv6 and I still have the problem. Bob Rawlinson
All I can suggest, again, is that you check /etc/sysconfig/sysctl to see if things like IPV6_PRIVACY are set to "yes". If any of them are (there are 2 in 9.0) then the ipv6 module will be loaded anyway, in /etc/init.d/boot.ipconfig, no matter what it says in your modules.conf or whatever it may be called.
I have checked and all those are correct. Still ipv6 IS running. I looked in /etc/sysconfig/sysctl and /etc/init.d/boot.ipconfig and I could see no where it should start ipv6. The system I have in Ohio did not have this problem. Only the system I have with me in Tucson Az. I think the DSL line back home handled the ipv6 but the WiFi I have here will not.
You have nothing in /etc/init.d/boot.ipconfig that looks like this? # Enable IPv6 forwarding ? # LOAD_IPV6="no" case $IPV6_FORWARD in yes) LOAD_IPV6="yes" ;; esac case $IPV6_PRIVACY in yes) LOAD_IPV6="yes" ;; esac test "$LOAD_IPV6" = "yes" && /sbin/modprobe ipv6 >/dev/null 2>&1 # If not, then I believe similar code must be elsewhere in one of the /etc/init.d/boot* files. Try grep "modprobe ipv6" /etc/init.d/boot* and if nothing turns up, also grep for "insmod ipv6". Those 2 variables, IPV6_FORWARD and IPV6_PRIVACY, are in /etc/sysconfig/sysctl in 9.0, but they may have been moved in 9.1. Grep recursively for "IPV6_" in /etc/sysconfig/* They may of course, be renamed, so look at the script that turns up when you grep for "modprobe". Please don't think I am being condescending or arrogant or anything here, Bob. I don't want to think how many wrong turns I took until I stumbled onto this (plus the part in SuSEfirewall2 where ip6_tables is loaded, no matter what you do with ipv6 :-) ) I never encountered this myself; as soon as I turned it off in modules.conf, ipv6 stopped being loaded. But that is only what always gets loaded when the kernel is loaded, and other places abound where a module can optionally get loaded. The above is one such instance, and I am positive you must have the same, or a similar, instance on your system. In fact, I think it might have been your first description of this problem that got me looking into all this. It *has* to be there, or failing that, copy modules.conf (or whatever it's called with 2.6) to *.old, edit out ALL the ipv6 references, and boot with that. If ipv6 still gets loaded, then we haven't looked far enough to find where :-)
participants (6)
-
Carlos E. R. -
Darryl Gregorash -
Jeffrey Laramie -
Robert A. Rawlinson -
scsijon -
Sunny