Comment 15 for bug 663395

Revision history for this message
Orlando (holwerda-inc) wrote :

Hello everyone, my name is Orlando, and I am a new user of Ubuntu. I do not know very much about computers but believe that I have solved my slow browsing speed and web related loading issues after persistent research.

I approached this problem with a very simple method that I always use, called the scientific method, which consistently works for virtually every aspect of scientific knowledge; and in this case, computer science.

Step 1: Identify The Problem

Clean and full install of Ubuntu 10.10 results in slow internet connection speed, and slow loading time, including browsing glitches, random dns search reroutes; as well as pages loading quickly while images lag, flash glitches and lack of functionality in video streaming.

Step 2: Research Possible Solutions

Most forums were addressing and pointing to issues which pertain to disabling ipv6, however some forums also included posts that stated ipv6 was not the only issue, but dns, internet configuration, application malfunction, and firefox bugs.

Step 3: Hypothesis

To rule out any peripheral problems, my hypothesis is that one should make sure that their ubuntu 10.10 installation cd is in good working order by opening up the files in the cd and checking to see that everything is there. One should reinstall ubuntu 10.10, just to be further meticulous. One should have their internet service provider run a signal test to your modem to make sure your signal is normal. One should reset their modem, and reboot their computer to make sure everything is reset. One should thoroughly manage and install updates and synaptic packages to the newly, fully installed ubuntu 10.10, as well as install adobe flash, and reboot their computer to ensure that ubuntu 10.10 has all the resources at its disposal, and fully loaded before attempting to troubleshoot the browsing issue.

Once the everything is set up, one should do a quick surf of the internet to confirm that the browsing problem is still their and that problem solving should go continue.

Now, after reviewing most of the online posts and notes, I realized that the disabling of ipv6 was noted in most posts, for "resolved". My hypothesis, therefore, is that ipv6 should definitely be disabled. However, because dns issues were also reported, my hypothesis is that a dns test should be run before trying to disable ipv6. Once dns is found to be working properly, one should follow up by disabling ipv6. Although rebooting after disabling ipv6 might have worked for some, many reported that it only worked temporarily, or not at all, therefore my hypothesis is that firefox should be reconfigured to authenticate the disabling of ipv6 as well.

Step 4: Experiment

First, I ran a dns test in accordance with notes provided by CARROARMATO0

"To test DNS, you can use nslookup. It's a commandline tool for querying dns servers.

1) Open up a commandline and type in "nslookup" and pressing enter (a prompt should appear waiting for input)
2) type in url's like google.com, facebook.com or ubuntu.com, etc... etc... followed by and enter
3) You should be getting responses in about under 1 second for each query
4) exit with "exit"

If you get near instant responses, that means that DNS (over ipv4) is ok.

Should you get very long response times, you're probably experiencing a different kind of issue than explained in the bug report.
If this is the case, try changing Dns servers, for example OpenDNS.

You can switch DNS server(s) by manually editing your connection in Network Manager, and selecting IPv4 "Automatic, only addresses".
You should be able to edit the "DNS server" field.

In there you can enter the following IP's: 208.67.222.222, 208.67.220.220
and repeat the testing process with nslookup

Again if that fails, than I believe you are experiencing a different kind of problem."

My test proved that I did not have a dns problem, therefore, I began to proceed to disable the ipv6 in accordance with notes provided by, again, CARROARMATO0:

"After doing some research, I finally found out that IPv6 is causing the huge delay in resolving url's.

IPv6 is enabled by default and apparently is the first IP protocol used for which to resolv url's.

Most people aren't using IPv6 yet, so attempting to resolv over IPv6 will result in a huge delay untill the system stops trying and falling back to IPv4.

This is the reason why the connections after waiting long enough will succeed.

Also, ping uses ipv4, that's why it works (ping6 being the ipv6 counterpart).

Now,

**************** WORKAROUND ****************
Disable IPv6 entirely

In a terminal, do this: cat /proc/sys/net/ipv6/conf/all/disable_ipv6
0 means IPv6 is enabled, we want it to become 1 (disabled) and make the change permanent.

Open up the following file like this: sudo gedit /etc/sysctl.conf
And add the following lines:

#Disable IPv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

Now reboot the system, and connectivity should be snappy as expected."

This however, did not entirely solve the problem, the internet browsing speed resumed to slow as noted.

This is because carroarmato0 failed to follow up by reconfiguring firefox to employ the changes made in the terminal.

Therefore, my last step in the experiment conclusively lead to a fix in the issue, and it was fully resolved. Here are the final steps that were left out, which lead to the fix.

Go to: the firefox browser and type in: about:config

in the menue, scroll to:

network.dns.disableIPv6 and change the value from false, to true (by double clicking it)

scroll to:

network.http.pipelining and change the value from false, to true (by double clicking it)

scroll to:

network.http.pipelinning.maxrequests and change the value to 8 or 10 (by double clicking it, and entering the new value)

scroll to:

network.http.proxy.pipelining and change the value from false, to true (by double clicking it)

After you do this, get out of firefox, and then reboot your system. Now the problem is fixed

Step 5. Test

Surf the web.

Step 6: Findings

I found my browsing to be back to normal and up to speed. This is definitely a fix. My findings are that ipv6 must be disabled, followed by reconfiguring firefox.