[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Internet loads too slow



On Sun, Dec 29, 2013 at 11:11:41PM +0900, Man_Without_Clue wrote:
> Ok,
> 
> Here are what I have done though I really have lost track of things
> I've done as I just follow what I could find...

I see you haven't gotten a response to this. So, I'm going to have a
crack at it.

>    echo net.ipv6.conf.all.disable_ipv6=1 > /etc/sysctl.d/disableipv6.conf
> 

That's good enough, as long as you either ran

sysctl -p /etc/sysctl.d/disableipv6.conf

afterwords, or simply rebooted. The rest I consider to be
overkill. You still haven't explained why you're disabling ipv6 in the
first place. Do you have ipv6 connectivity which you suspect to be
buggy? If you only have ipv4 connectivity then an enabled ipv6 stack
is likely not the cause for your slow internet.

>    sed '/::/s/^/#/' /etc/hosts >/etc/dipv6-tmp;cp -a /etc/hosts
>    /etc/hosts-backup && mv /etc/dipv6-tmp /etc/hosts
> 
>    sed '/ipv6=yes/s/yes/no/' /etc/avahi/avahi-daemon.conf
>     >/etc/avahi/dipv6-tmp;cp -a /etc/avahi/avahi-daemon.conf
>    /etc/avahi/avahi-daemon.conf-backup && mv /etc/avahi/dipv6-tmp
>    /etc/avahi/avahi-daemon.conf
> 

Like I said above, overkill.

>  ping -c 5 google.com
> PING google.com (173.194.38.64) 56(84) bytes of data.
> 64 bytes from nrt19s17-in-f0.1e100.net (173.194.38.64): icmp_req=1
> ttl=54 time=17.2 ms
> 64 bytes from nrt19s17-in-f0.1e100.net (173.194.38.64): icmp_req=2
> ttl=54 time=17.1 ms
> 64 bytes from nrt19s17-in-f0.1e100.net (173.194.38.64): icmp_req=3
> ttl=54 time=16.9 ms
> 64 bytes from nrt19s17-in-f0.1e100.net (173.194.38.64): icmp_req=4
> ttl=54 time=21.1 ms
> 64 bytes from nrt19s17-in-f0.1e100.net (173.194.38.64): icmp_req=5
> ttl=54 time=17.2 ms
> 
> --- google.com ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 4003ms
> rtt min/avg/max/mdev = 16.955/17.942/21.102/1.583 ms
> 

That's not at all bad! It's better then what I get on a nearly 3 meg
down adsl connection from the gateway connected directly by wire to
the modem.

> 
> then,
> 
> 
> ping -c 5 101.119.11.99
> PING 101.119.11.99 (101.119.11.99) 56(84) bytes of data.
> 64 bytes from 101.119.11.99: icmp_req=1 ttl=48 time=138 ms
> 64 bytes from 101.119.11.99: icmp_req=2 ttl=48 time=130 ms
> 64 bytes from 101.119.11.99: icmp_req=3 ttl=48 time=132 ms
> 64 bytes from 101.119.11.99: icmp_req=4 ttl=48 time=133 ms
> 64 bytes from 101.119.11.99: icmp_req=5 ttl=48 time=135 ms
> 
> --- 101.119.11.99 ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 4005ms
> rtt min/avg/max/mdev = 130.803/134.260/138.205/2.539 ms
> 
> 

That's worse, but it's still better than what I get when pinging
that.

>  ifconfig $dev
> eth0      Link encap:Ethernet  HWaddr 00:1c:c0:19:ba:33
>           inet addr:192.168.1.15  Bcast:192.168.1.255 Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:325430 errors:0 dropped:23 overruns:0 frame:0
>           TX packets:239942 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:273528223 (260.8 MiB)  TX bytes:41728298 (39.7 MiB)
>           Interrupt:20 Memory:e0300000-e0320000
> 

You have 23 RX packets. That's probably nothing to worry about, unless
it keeps going up as you use your internet connection between
reboots. I don't see your nameservers and routing as being a problem either.

> From "curl" thing, I get very long response tagged with <html>....

I tried that too exactly as Scot posted it, but am told the -w flag
isn't recognized. This is on a wheezy system. I prefer wget myself, so
I suggest you try that instead

apt-get install wget (you should already have it installed anyway)

wget www.debian.org
--2013-12-30 20:45:04--  http://www.debian.org/
Resolving www.debian.org (www.debian.org)... 140.211.15.34,
128.31.0.51
Connecting to www.debian.org
(www.debian.org)|140.211.15.34|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14776 (14K) [text/html]
Saving to: `index.html'

100%[======================================>] 14,776      --.-K/s   in
0.1s

2013-12-30 20:45:06 (134 KB/s) - `index.html' saved [14776/14776]

>From what you posted so far, I'd say your internet connection is
fine. You still haven't answered some of Scot's questions, the answers
to which could shed light on your problem. I left what you haven't
provided answers to below.

> On 12/28/2013 11:16 PM, Scott Ferguson wrote:
> >*Important* *and*
> >your home network configuration, ISP plan, etc (do you really not have
> >IPV6?).
> >
> >What part of the internet loads slow?  e.g. DNS results, browser page,
> >slow internet etc.
> >
> >Lastly check dmesg and /var/log/syslog for pertinent errors, check top
> >and free for system resource restraints.
> >

Greg


-- 
web site: http://www.gregn..net
gpg public key: http://www.gregn..net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org


Reply to: