Slow internet problem seems to be related to dns Suse 11.4 i586 KDE

I have just installed 11.4 from scratch. All seems ok but the internet service is really slow. Firefox often shows — looking up … for a very long time. As this looked much like an ipv6 problem I have used yast’s /etc/sysconfig editor to add ipv6.disable=1 to the end of the 3 bootloader _APPENDS. I have also disabled it’s use in KDE after finding the appropriate place with the editors search facility. I restarted the system but have found that this hasn’t helped at all. Things are much the same.

I use an asdl2/2+ router over ethernet. This looks after log in to my isp and obtains the dns server address etc.

One curious aspect is that once a page has displayed, this forum for instance, further pages load fairly quickly for a while. Others with adds etc all over the place display the same symptom. The data itself seems to download fairly quickly. Graphics performance seems fine too.

My wife’s windoze works as expected by the way so the router set up looks to be ok

I’m more or less a complete kernal novice by the way and much prefer to stay away from it.

:open_mouth: Help

John

there is also an anti-IPv6 switch in Firefox…try any or all of these
which should speed it up (btw, i copied the following from another post
and take neither credit nor responsibility for any–and see my sig caveat)

place about:config in the address bar and hit enter

You should get a really long list of things

In the search bar put
‘network.dns.disableIPv6’

My default value was set to false, go ahead and set it to true. Right
click and Toggle.

Clear out the search bar where ‘network.dns.disableIPv6’ was, and put
in ‘network.http.pipelining’

You should have three listings

Right click on ‘network.http.pipelining’ and Toggle so “true” shows for
the value.

Next, right click on ‘network.http.pipelining.maxrequests’ and Modify,
a box will pop up, replace the default 4 with 8.

Close the about:config

also, maybe it is a DNS problem, did you put the right name server in
your setup? Check your DNS servers in your /etc/resolv.conf file


CAVEAT: http://is.gd/bpoMD [NNTP via openSUSE 11.3 + KDE4.5.5 +
Thunderbird3.1.8] Can you believe it? This guy Ralph wins $181 million
in the lottery last Wednesday, and then finds the love of his life just
2 days later. Talk about LUCK!

Thanks. That fixed it completely. On the dns server my router gets these from the isp so I wouldn’t have a clue what to enter. They change from time to time as well.

Having this problem is a little disgusting really. Way back when suse was still a .de company an update installed and activated ipv6. I was lucky my internet still worked after a fashion - not so for many people. I notice that if I happened to be using a straight modem there seems to be an option for disabling ipv6 but no long term user will be using one. Does anybody these days?

Despite de activating ipv6 in KDE Konq still has the problem. I thought that the route to disabling it looked very much like kde 3.??? so I suppose it’s just garbage that suse has left lying around. Does anyone know of a fix for konq? Also it seems to have a fixation as installed about working through a proxy. I’ve changed that to use the net directly as only one of the proxy settings actually works. The install left that one set.

John

Gets worse Yast2 seems to be having the same problem and is refusing to download the repositories - can’t connect to server. Anybody and clues.

I have found another kde ipv6 over ride but it’s correctly set.

John

I’ve found another ipv6 over ride which seemed to have fixed yast2 for some. Network card config has 2 settings. IPV6 and IPV4 or IPV4 only. lol! I got really excited as yast seemed to update. It loaded the repository update. Then started to hang on connection time outs also stating that some rpm’s are unavailable. :frowning:

Konqueror is still the same.

Help. I’ve searched this forum and info seems to be scattered in many threads which doesn’t help at all.

John

Since its been some time without a reply and you seem to have ruled out all the usual suspects, I’ll venture a (wild) guess.

I had the same problem - first few connections ok, subsequent site accesses timing out. It turned out that I had a VM set to the same IP address as the host, in bridged mode. When both would access the network one timed out.

So, perhaps you have another machine (real or virtual) trying to use the same IP in your network?

Also keep in mind the words of our wireless networking guru, lwfinger: If it’s not working, there’s at least two things going wrong at the same time. (any quote error is solely mine, thanks lwfinger :)).

I’ve posted it as bug basically because everything else is working when switched to ipv4 but yast just wont have it so as it’s purely dns I’m certain it’s ipv6.

I use ethernet cable to an adsl2/2+ router. Been there for some time and wireless doesn’t appeal.

John

Try setting your DNS addresses directly in Yast>Network Device, instead of pointing to the router, if it isn’t already so.

This is an area that confuses me brunomcl. My isp provides the dns addresses when I connect. As I’m connected all/most of the time this has very occasionally caused problems that rebooting the router fixed. A complaint to the isp fixed that aspect as well.

Firefox,Opera,Konqueror are all ok now and I assume correctly using the dns via the adsl router. YAST just gets through occasionally when it does the rpm’s etc come very quickly. YAST spends so much time trying to connect to the servers I haven’t managed a complete update yet. I can view and download the files with any of the browsers. To many files though to use as a fix.

One aspect of this is that I have been here before. Some time ago 9.x suse or very early opensuse 10.x was updated to ipv6 and it was also activated. My system just about worked providing that I didn’t mind pages taking very long times to load. Could be up to a min or more. Some peoples web just wouldn’t work at all. I just can’t understand why it has installed like this.

John

On 04/11/2011 11:36 AM, ajohnw wrote:
>
> This is an area that confuses me brunomcl. My isp provides the dns
> addresses when I connect. As I’m connected all/most of the time this has
> very occasionally caused problems that rebooting the router fixed. A
> complaint to the isp fixed that aspect as well.
>
> Firefox,Opera,Konqueror are all ok now and I assume correctly using the
> dns via the adsl router. YAST just gets through occasionally when it
> does the rpm’s etc come very quickly. YAST spends so much time trying to
> connect to the servers I haven’t managed a complete update yet. I can
> view and download the files with any of the browsers. To many files
> though to use as a fix.
>
> One aspect of this is that I have been here before. Some time ago 9.x
> suse or very early opensuse 10.x was updated to ipv6 and it was also
> activated. My system just about worked providing that I didn’t mind
> pages taking very long times to load. Could be up to a min or more. Some
> peoples web just wouldn’t work at all. I just can’t understand why it
> has installed like this.

If you hane an IPv6 problem, then the fault is with something upstream in your
setup. With Linux in general, and openSUSE in particular, IPv6 works. There are
no holdups and no extra delays. When a DNS server is misconfigured, says it
handles IPv6, but does not, then the name lookup will time out every time. That
leads to very slow browsing.

Not sure if opensuse 11.4’s requests are somehow “poisoning” my router, but a complete shutdown and restart of the router bought me about 45 minutes of normal internet access.

Duel boothing Windows 7 and confirming this is an opensuse 11.4 issue.

Same Here … one more thing i test a virtualbox machine in my suse host with xp and firefox its ok

I’ve filed a bug and it continues to gain comments. I’m currently using googles public dns service as mentioned in other threads. Not good really as I’m in the uk.

I had a look around for more info on ipv6 roll out and found a very recent .gov paper. Basically it reckons that roll out from now is about 2years away. Basic reason is that isp’s can manage without it so there are few ipv6 dns services or even ipv6 servers about world wide. I assume isp’s will just use a subnet approach until they have no other choice. On that basis there is no need for them to change at all in some respects. It seems there are cost considerations as far as they are concerned as well. This probably relates to bandwidth as well as implementation costs. While a few % or less change in traffic sounds small it can represent a lot of users.

As to fixes I would have hoped that the ipv6 standard includes some mechanism to see if it is available just as mail servers can be interrogated to see what they support. This way and change over could be transparent as far as the user is concerned.

>:) All leaves me wondering if we are about to have more problems with commodity dealers - buying up all the ip addresses they can and then holding on to them until the price goes up. Companies values might even rocket on the basis of the ip space they own. The mind boggles. Then comes a crash when if ever ipv6 really rolls out.

Fixed your slow internet connect on openSUSE by doing the following:

open up the resolv.conf and change the nameserver to 8.8.8.8 in the bottom as shown bellow:

make sure you make a copy of your original reslov.conf file just in case.

/etc/resolv.conf file autogenerated by netconfig!

Before you change this file manually, consider to define the

static DNS configuration using the following variables in the

/etc/sysconfig/network/config file:

NETCONFIG_DNS_STATIC_SEARCHLIST

NETCONFIG_DNS_STATIC_SERVERS

NETCONFIG_DNS_FORWARDER

or disable DNS configuration updates via netconfig by setting:

NETCONFIG_DNS_POLICY=’’

See also the netconfig(8) manual page and other documentation.

Note: Manual change of this file disables netconfig too, but

may get lost when this file contains comments or empty lines

only, the netconfig settings are same with settings in this

file and in case of a “netconfig update -f” call.

Please remove (at least) this line when you modify the file!

nameserver 8.8.8.8

Worked like a charm. Glad the info can be found(eventually). It’s a shame that it should be necessary to go to these lengths to make something work the way it should, however.

OTOH how do I fix Thunderbird? This is the first time I’ve ever seen “Looking up”… my mail server.

Found it, but it still pretty lame.

On 08/27/2011 05:46 AM, TucsonBill wrote:
>
> Found it, but it still pretty lame.

just to set the record straight: the ‘lame’ you experience is because
your ISP has not yet correctly set up their name servers to support the
new IPv6 standards…

that, coupled with the fact that openSUSE (and Linux in general) has
been 100% IPv6 ready for years it (rightly) trys to resolve name service
using IPv6…but, since your ISPs stuff is broken you have to wait for
the request to time out, and then it reverts to the old IPv4 protocol
and that zings through…

so, the step you took (to include 8.8.8.8) in your resolve file
removed your ISPs broken DNS servers from the loop and you now go
direct to Google’s DNS servers which are correctly set up and your 100%
capable openSUSE can zing along as it should, without having to WAIT for
your broken ISP name server to timeout…

by the way, my ISP is similarly broken and i’ve solved the slow down
problem (for now) by just turning off the IPv6 service in openSUSE…


DD
openSUSE®, the “German Engineered Automobile” of operating systems!

DenverD, Peace. I did not say or intend to imply that I think Opens SUSE linux is lame. I’m also culpable for not making it clear what I was responding to. Your post about the Firefox configuration edits is what solved this for me. (In Firefox). I appreciate it and that’s the post I responded to. The frustration is manifold. After much searching and finding this solution, I had to launch another expedition to find out where to find this configuration editor for Thunderbird. What I think is lame is the need to do this for each application and the easter egg hunt required to find out how to do it. I would say it’s probably beyond the average user. OTOH the average user wouldn’t be using Linux. Compounding the frustration is the fact that I have Windows 7 running in a VM on this machine, and it has no problem at all handling this using the same interface. Thanks again for the help. I’m a happier camper now.

On 08/27/2011 10:36 PM, TucsonBill wrote:
>
> DenverD, Peace. I did not say or intend to imply that I think Opens
> SUSE linux is lame.

i also often write (peacefully) for the next person to come in the
thread (via google maybe)…who might think “Hey, this guy who seems to
know what he is talking about says openSUSE is lame, so i guess it
is…i’ll go somewhere else!”

> OTOH the average user wouldn’t be using Linux.

i consider myself an average computer user…
i will admit that i did learn a long time ago to use something more
practical that virus bait…

> Compounding the frustration is the fact that I have Windows 7 running
> in a VM on this machine, and it has no problem at all handling this
> using the same interface.

i am NOT sure, but i think that is because Win7 is born with IPv6
disabled, or maybe it is asking first using IPv4 and if it gets and
answer it goes on…what happens if you use your Win7 in VM to go to

http://ipv6.google.com/

or

http://test-ipv6.com/

or

http://help.yahoo.com/l/us/yahoo/ipv6/ (and press the “Start IPv6 test”
button)

i’d be interested to know if those test say Win7 is using IPv6 (and,
your ISP’s dns) “with no problem at all”…

> Thanks again for the help. I’m a happier camper now.

happy for you too!


DD
openSUSE®, the “German Engineered Automobile” of operating systems!