Why is my Internet so slow?

Unhyper · 09-17-2011, 12:35 AM

I am using a fresh install of Mint x64, and it is working out great but for one thing: browsing the Internet is noticeably slower than it was on Windows. Typing in any URL results in an intolerable wait. I just typed in cnn.com in the address bar and it took 11 seconds for the CNN homepage to appear.

I am using mobile broadband connection and Firefox 6.0.2.

jdkaye · 09-17-2011, 01:10 AM

I tried your test (the only reason I would ever look at CNN). It took about 2 seconds to load. I'm using Debian Wheezy Amd64 and Iceweasel 6.0.2 (same as FFx) and connected to my router via wifi. I confess to total ignorance of mobile broadbands but I don't think it's a FFx nor a Mint issue. You may want to disable any FFx plugins or extensions and see if that makes a difference.
ciao,
jdk

etech3 · 09-17-2011, 01:18 AM

You may want to check your dns settings. I never use the carriers dns. I use a different dns like google (8.8.8.8). Check your resolv.conf settings. I always have at least three in there.

es0teric · 09-17-2011, 01:21 AM

Depending on how familiar you are with networking, it may be useful to install Wireshark to see what's going on at the packet level during that wait time. Wireshark basically starts "recording" network traffic when you press a button. If you're already familiar with networking and TCP/IP stuff, then it will shed some light on it. If you're not but would like to be, then it's a great way to learn.

markush · 09-17-2011, 02:28 AM

Hello Unhyper,

if you're not familiar with checking your DNS-settings, please post the output of

Code:

cat /etc/resolv.conf

To check if DNS can be the problem, please use the

Code:

ping -Uc4 anyadress

command and for "anyadress" use the URL of a website where you've never been before. Afterwards ping the same adress by it's IP-adress (it will be shown in the output of the command with "anyadress". I'll give you an example what I mean: first I ping the adress

Code:

markus@samsung:~$ ping -Uc4 www.google.ca
PING www.l.google.com (209.85.148.99) 56(84) bytes of data.
64 bytes from fra07s07-in-f99.1e100.net (209.85.148.99): icmp_req=1 ttl=53 time=38.4 ms
64 bytes from fra07s07-in-f99.1e100.net (209.85.148.99): icmp_req=2 ttl=54 time=35.9 ms
64 bytes from fra07s07-in-f99.1e100.net (209.85.148.99): icmp_req=3 ttl=54 time=37.0 ms
64 bytes from fra07s07-in-f99.1e100.net (209.85.148.99): icmp_req=4 ttl=54 time=36.2 ms

--- www.l.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms

afterwards I take the adress which is shown (209.85.148.99) and ping again

Code:

markus@samsung:~$ ping -Uc4 209.85.148.99
PING 209.85.148.99 (209.85.148.99) 56(84) bytes of data.
64 bytes from 209.85.148.99: icmp_req=1 ttl=54 time=35.1 ms
64 bytes from 209.85.148.99: icmp_req=2 ttl=53 time=33.7 ms
64 bytes from 209.85.148.99: icmp_req=3 ttl=53 time=29.1 ms
64 bytes from 209.85.148.99: icmp_req=4 ttl=53 time=47.1 ms

--- 209.85.148.99 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 29.138/36.302/47.149/6.648 ms

If there's something wrong with the DNS-settings, you'll see a difference in the pingtime between pinging the name or the IP.

Note that this will only give a first hint. You may also post the IP-settings of your Windows-machine, on the Windowsmachine open a terminal (cmd) and post the output of

Code:

ipconfig /all

Markus

jsaravana87 · 09-17-2011, 05:14 AM

first check ur dns vi /etc/resolv.conf,nslookup ,dig command check whether u have conf ipaddress setting wright

repo · 09-17-2011, 05:16 AM

Try to disable ipv6 in firefox
http://thedaneshproject.com/posts/di...-in-firefox-3/

Kind regards

anon02 · 09-17-2011, 05:32 AM

Not sure how helpful this will be compared to other answers, but when I upgraded my asus eee pc 901 with Ubuntu 11.04 I had the same issue. My fix was to look in :

'lsmod | grep -e rt'

Which posted all drivers used for the WiFi chipset. Depending on which chipset your computer uses it may have conflicting drivers. In my case this fixed it.