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:e030-e032 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-mana...@eu.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of
Re: Internet loads too slow
On 30/12/13 01:11, Man_Without_Clue wrote: Ok, Here are what I have done though I really have lost track of things You might find it easier to follow if you used interleaved posting:- https://wiki.debian.org/DebianMailingLists#Posting_Rules.2C_Guidelines.2C_and_Tips http://en.wikipedia.org/wiki/Posting_style#Interleaved_style and plain text format:- https://wiki.debian.org/DebianMailingLists#HowTo_send_plain_text_emails_to_the_list I find it less difficult to follow threads that way. It's worth learning IMO :) I've done as I just follow what I could find... snipped #netstat -tunlp |grep p6 |wc -l This returns 0. Thanks. Just wanted to check you hadn't been following borked instructions that slowed your network. I agree with Greg Nowak, except in embedded and other resource limited situations the IPv6 stack isn't going to slow your network. On the other hand you might get a slower network if IPv6 is delivered and you're not using it (you didn't say). Now, I did following as you suggested, ping -c 5 google.com snipped Those times aren't terrible. Though speed and service satisfaction are different things. You'd have to give some information about what your ISP has told you to expect before the service can be measured. also, cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.1.254 ## 192.168.1.254 is the IP for the router. Unless your router is doing DNS caching it's just a continuous relay for another DNS. You'd have to check your router (modem/hub?) settings to see what that DNS is - by default that's normally set to your ISP's DNS. Generally their DNS is going to be the fastest (though not necessarily the most up-to-date). Choice of DNS server can make a significant difference to what's perceived as internet speed*1. *1 Generally, a user's perception of internet speed (click) means action time (graphic result) - response time and can be a struggle to correlate throughput time to that. Those on-line speed tests give a poor indication of throughput time anyway. Loading a web page:- ;ask DNS for IP address (check cache first if one exists, then try DNS Nameserver entries in order) ;ask ISP for route to IP address ;ask server at IP address for page ;read page ;ask DNS for IP addresses for page components ;ask IP address for page components ;rinse and repeat as needed ;if not served ISP pre-cached, if Vodaphone may route page and components through squasher to compress pictures and code ;add in browser extension, malware detection and firewall processes, etags and other factors ;render results to screen So a fast, low-latency internet connection can still appear slow due to poor page design, bad firewall and anti-malware systems, buggy extensions, video settings and hardware, DE settings and constraints (swappiness), and DNS settings. You don't say what it is that isn't as fast as you'd like and that's important because it may be something that only QOS can fix (i.e. VOIP). For your browser disable any unused extensions. Do install NoScript, FlashBlock and AdBlock if you use Iceweasel. Disable any networking desktop widgets/eyecandy. Disable any network applications. Install namebench:- # apt-get install namebench man namebench Optimise your DNS settings using namebench (it's got a simple to use GUI and good documentation). Then selectively re-enable any applications you use that use the network (weather widgets, rss readers, bittorrents, VOIP etc), testing each time with ping, curl and tcptraceroute to see what effects they have on your network. Note that your ISP's network latency and bandwidth may change considerably throughout the day. Ping won't test the speed of the route taken by pages. tcptraceroute will. # apt-get install tcptraceroute Test your internet connection. Ping, curl (or wget), and tcptraceroute will give you some useful metrics, but they won't tell you if your ISP is throttling certain types of traffic. And online internet speed tests are useless because they only test total time to tranfer. For detailed analysis and measurement of your internet connection use:- http://mlab-live.appspot.com/tools/ndt http://code.google.com/p/ndt/source/checkout Let us know the results ;) If you find problems try the transparency and last mile tests elsewhere on the site. If you want to do longer term monitoring look at installing nubot. route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default 192.168.1.254 0.0.0.0 UG0 00 eth0 localnet* 255.255.255.0 U 0 00 eth0 All good 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 You've
Re: Internet loads too slow
On 31/12/13 15:08, Gregory Nowak wrote: On Sun, Dec 29, 2013 at 11:11:41PM +0900, Man_Without_Clue wrote: snipped I tried that too exactly as Scot posted it, but am told the -w flag isn't recognized. This is on a wheezy system. Likewise. Though I have backports enabled. curl 7.26.0-1+wheezy i386 man curl -w, --write-out format Defines what to display on stdout after a completed and successful operation. The format name and to tell curl to read the format from stdin you write @-. The variables present in the output format will be substituted by the value or text that curl thinks fit, as described below.. I prefer wget myself, Different dog, same leg action ;) snipped Kind regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52c25eda.2000...@gmail.com
Re: Internet loads too slow
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... Comment them with a '#' sign: Code: Select all #udp6 tpi_clts v inet6 udp - - I did this. echo net.ipv6.conf.all.disable_ipv6=1 /etc/sysctl.d/disableipv6.conf 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 and I did this. #netstat -tunlp |grep p6 |wc -l This returns 0. Now, I did following as you suggested, 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 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 also, cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.1.254 ## 192.168.1.254 is the IP for the router. route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.1.254 0.0.0.0 UG0 00 eth0 localnet* 255.255.255.0 U 0 00 eth0 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:e030-e032 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:400 (400.0 B) TX bytes:400 (400.0 B) ip a 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1c:c0:19:ba:33 brd ff:ff:ff:ff:ff:ff inet 192.168.1.15/24 brd 192.168.1.255 scope global eth0 I could get up to here... From curl thing, I get very long response tagged with html I am lost A.K. On 12/28/2013 11:16 PM, Scott Ferguson wrote: On 29/12/13 00:26, Man_Without_Clue wrote: Hi all, I have asked this question everywhere, but still haven't gotten clear and solid solutions yet, so I thought I would send this to this list. Perhaps because there are an unknown number of causes for the problem and because you've provided no information about your network. :) As title says, internet loads too slow on Debian Wheezy amd 64. I have searched web and have done several methods to turn ipv6 off including Iceweasel, but still websites load slow. Any additional advise ? See below. *Important* please tell us what you have done to disable IPV6 *and* your home network configuration, ISP plan, etc (do you really not have IPV6?). Thanks in advance. A.K. What part of the internet loads slow? e.g. DNS results, browser page, slow internet etc. Check the DNS by pinging a domain name then it's IP address and posting your results e.g.:- $ ping -c 5 google.com PING google.com (101.119.11.99) 56(84) bytes of data. 64 bytes from google.com (101.119.11.99): icmp_req=1 ttl=60 time=77.5 ms 64 bytes from google.com (101.119.11.99): icmp_req=2 ttl=60 time=67.5 ms 64 bytes from google.com (101.119.11.99): icmp_req=3 ttl=60 time=68.0 ms 64 bytes from google.com (101.119.11.99): icmp_req=4
Internet loads too slow
Hi all, I have asked this question everywhere, but still haven't gotten clear and solid solutions yet, so I thought I would send this to this list. As title says, internet loads too slow on Debian Wheezy amd 64. I have searched web and have done several methods to turn ipv6 off including Iceweasel, but still websites load slow. Any additional advise ? Thanks in advance. A.K. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52bed197.9040...@gmail.com
Re: Internet loads too slow
On 28 December 2013 13:26, Man_Without_Clue love.cha...@gmail.com wrote: Hi all, I have asked this question everywhere, but still haven't gotten clear and solid solutions yet, so I thought I would send this to this list. As title says, internet loads too slow on Debian Wheezy amd 64. I have searched web and have done several methods to turn ipv6 off including Iceweasel, but still websites load slow. Any additional advise ? Thanks in advance. A.K. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52bed197.9040...@gmail.com Compared to? Which browser are you using? Try Chromium. -- *rob*
Re: Internet loads too slow
On 29/12/13 00:26, Man_Without_Clue wrote:
Hi all,
I have asked this question everywhere, but still haven't gotten clear
and solid solutions yet, so I thought I would send this to this list.
Perhaps because there are an unknown number of causes for the problem
and because you've provided no information about your network. :)
As title says, internet loads too slow on Debian Wheezy amd 64.
I have searched web and have done several methods to turn ipv6 off
including Iceweasel, but still websites load slow.
Any additional advise ?
See below.
*Important* please tell us what you have done to disable IPV6 *and*
your home network configuration, ISP plan, etc (do you really not have
IPV6?).
Thanks in advance.
A.K.
What part of the internet loads slow? e.g. DNS results, browser page,
slow internet etc.
Check the DNS by pinging a domain name then it's IP address and posting
your results e.g.:-
$ ping -c 5 google.com
PING google.com (101.119.11.99) 56(84) bytes of data.
64 bytes from google.com (101.119.11.99): icmp_req=1 ttl=60 time=77.5 ms
64 bytes from google.com (101.119.11.99): icmp_req=2 ttl=60 time=67.5 ms
64 bytes from google.com (101.119.11.99): icmp_req=3 ttl=60 time=68.0 ms
64 bytes from google.com (101.119.11.99): icmp_req=4 ttl=60 time=86.6 ms
64 bytes from google.com (101.119.11.99): icmp_req=5 ttl=60 time=63.2 ms
--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 63.284/72.615/86.673/8.442 ms
scott@vbserver:~/Downloads/kernel$ 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=60 time=66.6 ms
64 bytes from 101.119.11.99: icmp_req=2 ttl=60 time=65.1 ms
64 bytes from 101.119.11.99: icmp_req=3 ttl=60 time=65.8 ms
64 bytes from 101.119.11.99: icmp_req=4 ttl=60 time=83.2 ms
64 bytes from 101.119.11.99: icmp_req=5 ttl=60 time=75.1 ms
--- 101.119.11.99 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 65.100/71.195/83.222/7.028 ms
NOTE: my system uses a wireless broadband connection so slow responses
are normal for this network.
Show us your nameserver settings by posting the output of:-
$ cat /etc/resolv.conf
Show us the routing by posting the output of:-
# route
See if you are dropping packets by substituting $dev with your internet
connection device:-
# ifconfig $dev
e.g eth1 is my internet connection and it's dropped no packets
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:20:ed:8f:ab:fd
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:89090 errors:0 dropped:0 overruns:0 frame:0
TX packets:188186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14993111 (14.2 MiB) TX bytes:248603032 (237.0 MiB)
Interrupt:22 Base address:0xe000
Show us your NICs by posting the output of:-
$ ip a
Test your download speed with curl (# apt-get install curl if you
don't have it). This will is to distiguish between network speed and
browser speed e.g.:-
$ curl http://www.debian.org -w
%{time_connect}:%{time_starttransfer}:%{time_total}:%{size_download}
NOTE: I get 0.930:1.787:2.016:13655
Lastly check dmesg and /var/log/syslog for pertinent errors, check top
and free for system resource restraints.
Kind regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52bedd35.2070...@gmail.com
