these forums have been incredibly, sometime simpossibly, slow these last two or three days.
Just mentioning it.
Incredibly Slow
I have been trying to figure out what the problem is. I was hoping it was just my connection from work. It's not the forums actually but it is something to do with my cable connection. I have been cleaning and moving equipment around so maybe I have a bad cable or a flaky switch. I'll try wiggling all the cables and power cycle the switches and modem and see what happens. It also seems to be more of a problem with my upload traffic and not my download traffic. All interfaces are clean, power cycled router, still bad. I'll do the cable wiggling in a few hours.
If you guys could perform a ping of around 20 or 30 packets and a traceroute and upload the results that would be cool. I suspect significant packet loss and I suspect it's my stinking ISP again. This has happened before and it took weeks for them to resolve it (bad modem then).
EDIT: I just did a ping out to Google which seemed fine at the normal ping package size but as soon as I started increasing the ping packet size (with the -s <size> switch) I started getting a lot of packet loss. The same is true when I ping my ISP's web server so something is definitely wrong with my network connection. I will be able to eliminate or implicate any of my equipment this evening.
If you guys could perform a ping of around 20 or 30 packets and a traceroute and upload the results that would be cool. I suspect significant packet loss and I suspect it's my stinking ISP again. This has happened before and it took weeks for them to resolve it (bad modem then).
EDIT: I just did a ping out to Google which seemed fine at the normal ping package size but as soon as I started increasing the ping packet size (with the -s <size> switch) I started getting a lot of packet loss. The same is true when I ping my ISP's web server so something is definitely wrong with my network connection. I will be able to eliminate or implicate any of my equipment this evening.
Code: Select all
yc@Icebox:~$ ping voidmain.is-a-geek.net
PING voidmain.is-a-geek.net (68.188.13.164) 56(84) bytes of data.
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=1 ttl=43 time=137 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=2 ttl=44 time=146 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=3 ttl=43 time=141 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=4 ttl=44 time=145 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=5 ttl=43 time=139 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=6 ttl=43 time=137 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=7 ttl=43 time=138 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=8 ttl=43 time=140 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=9 ttl=43 time=157 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=10 ttl=43 time=139 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=11 ttl=43 time=138 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=12 ttl=44 time=141 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=13 ttl=44 time=137 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=14 ttl=43 time=137 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=15 ttl=43 time=137 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=16 ttl=43 time=139 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=17 ttl=44 time=137 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=18 ttl=43 time=139 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=19 ttl=44 time=136 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=20 ttl=44 time=136 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=21 ttl=43 time=140 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=22 ttl=44 time=136 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=23 ttl=43 time=136 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=24 ttl=43 time=138 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=25 ttl=43 time=136 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=26 ttl=43 time=137 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=27 ttl=44 time=164 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=28 ttl=43 time=157 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=29 ttl=43 time=138 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=30 ttl=44 time=139 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=31 ttl=44 time=141 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=32 ttl=43 time=137 ms
Code: Select all
Icebox:~# traceroute voidmain.is-a-geek.net
traceroute to voidmain.is-a-geek.net (68.188.13.164), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.344 ms 5.321 ms 1.430 ms
2 10.70.128.1 (10.70.128.1) 34.661 ms 8.908 ms 10.982 ms
3 dD5E0FAE1.access.telenet.be (213.224.250.225) 9.692 ms 11.108 ms 9.262 ms
4 dD5E0FD41.access.telenet.be (213.224.253.65) 9.333 ms 9.172 ms 10.573 ms
5 dD5E0FD6A.access.telenet.be (213.224.253.106) 7.059 ms 9.874 ms 11.641 ms
6 Level3-Telenet-Dusseldorf (62.67.38.149) 16.340 ms 15.707 ms 16.546 ms
7 ae-0-53.bbr1.Dusseldorf1.Level3.net (4.68.119.65) 15.729 ms 47.667 ms ae-0-51.bbr1.Dusseldorf1.Level3.net (4.68.119.1) 15.930 ms
8 ae-0-0.bbr1.Washington1.Level3.net (64.159.0.229) 102.280 ms as-3-0.bbr2.Washington1.Level3.net (4.68.128.206) 101.439 ms ae-0-0.bbr1.Washington1.Level3.net (64.159.0.229) 100.506 ms
9 ae-23-54.car3.Washington1.Level3.net (4.68.121.112) 179.057 ms * *
10 qwest-level3-te.Washington.Level3.net (4.68.110.178) 104.609 ms 103.152 ms 107.568 ms
11 dcx-core-02.inet.qwest.net (205.171.251.37) 110.577 ms 104.221 ms 101.073 ms
12 cer-core-02.inet.qwest.net (67.14.8.22) 121.482 ms 123.969 ms 119.720 ms
13 cer-edge-01.inet.qwest.net (205.171.139.18) 121.895 ms 121.773 ms 120.152 ms
14 208.44.154.174 (208.44.154.174) 127.488 ms 129.156 ms 126.600 ms
15 24.217.2.253 (24.217.2.253) 132.679 ms 129.336 ms 128.344 ms
16 24.217.3.13 (24.217.3.13) 134.192 ms 129.998 ms 128.820 ms
17 24.217.2.146 (24.217.2.146) 128.366 ms 130.282 ms 127.676 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
i pinged you and it looks ok, (actually looking at it, 150ms compared with 40-50ms for other sites i tried to ping, well, could be worse...) but it's intermittent of course, sometimes i can't read the site at all. now of course, when i read your reply, i ping and because i can read it, i already know the connection is ok!
by the way, if this reply appears on your site then clearly the connection's managed to get through by now.
EDIT: by the way void main i really think you need to sort the thing that changes the abbrev for milliseconds to "M$", and while you're at it, the one that substitutes for microsoft is pretty silly too, but then it's your site after all!
traceroute now tells a slightly different story though...64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=11 ttl=41 time=149 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=12 ttl=41 time=148 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=13 ttl=41 time=149 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=14 ttl=41 time=151 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=15 ttl=41 time=149 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=16 ttl=41 time=150 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=17 ttl=41 time=149 ms
64 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=18 ttl=41 time=150 ms
--- voidmain.is-a-geek.net ping statistics ---
18 packets transmitted, 18 received, 0% packet loss, time 17149ms
rtt min/avg/max/mdev = 148.831/150.169/151.870/0.821 ms
i know you are planning to "wiggle" some wires (which reminded me of this btw!) but thought i would post some output anyway. why not, eh?traceroute to voidmain.is-a-geek.net (68.188.13.164), 30 hops max, 38 byte packe
ts
1 192.168.0.1 (192.168.0.1) 0.467 ms 0.434 ms 0.348 ms
2 192.168.1.1 (192.168.1.1) 4.393 ms 1.237 ms 1.100 ms
3 217.47.207.250 (217.47.207.250) 27.405 ms 27.682 ms 26.578 ms
4 217.47.207.161 (217.47.207.161) 25.639 ms 26.494 ms 28.797 ms
5 217.41.174.9 (217.41.174.9) 27.089 ms 26.989 ms 26.526 ms
6 217.41.174.66 (217.41.174.66) 38.432 ms 27.625 ms 27.795 ms
7 217.41.174.150 (217.41.174.150) 26.562 ms 26.053 ms 26.249 ms
8 217.41.218.54 (217.41.218.54) 27.610 ms 27.312 ms 26.988 ms
9 217.47.186.241 (217.47.186.241) 26.125 ms 25.843 ms 26.510 ms
10 core2-pos12-1.edinburgh.ukcore.bt.net (217.32.169.213) 26.290 ms 26.030 ms
27.027 ms
11 core2-pos15-2.birmingham.ukcore.bt.net (194.74.16.237) 33.754 ms 33.418 ms
33.129 ms
12 core2-pos5-0.ealing.ukcore.bt.net (62.6.204.214) 36.073 ms 36.093 ms 36.1
45 ms
13 transit2-pos6-0.ealing.ukcore.bt.net (194.72.17.198) 35.745 ms 35.548 ms
35.945 ms
14 t2c2-p1-0.uk-eal.eu.bt.net (166.49.168.37) 36.576 ms 36.196 ms 35.284 ms
15 t2c2-p4-0.us-ash.eu.bt.net (166.49.164.62) 111.455 ms 111.353 ms 110.220
ms
16 dcp-brdr-02.inet.qwest.net (205.171.1.37) 111.331 ms 110.173 ms 110.974 m
s
17 dcx-core-01.inet.qwest.net (205.171.251.33) 112.165 ms 119.906 ms 112.174
ms
18 * * *
19 cer-edge-01.inet.qwest.net (205.171.139.14) 132.463 ms 132.263 ms 131.474
ms
20 208.44.154.174 (208.44.154.174) 142.834 ms 141.853 ms 141.523 ms
21 24.217.2.253 (24.217.2.253) 140.440 ms 140.808 ms 141.030 ms
22 24.217.3.13 (24.217.3.13) 139.687 ms 139.666 ms 140.319 ms
23 24.217.2.146 (24.217.2.146) 141.225 ms 140.880 ms 140.504 ms
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
by the way, if this reply appears on your site then clearly the connection's managed to get through by now.
EDIT: by the way void main i really think you need to sort the thing that changes the abbrev for milliseconds to "M$", and while you're at it, the one that substitutes for microsoft is pretty silly too, but then it's your site after all!
Pretty much the same ...
Code: Select all
yc@Icebox:~$ ping -s 800 voidmain.is-a-geek.net
PING voidmain.is-a-geek.net (68.188.13.164) 800(828) bytes of data.
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=1 ttl=44 time=158 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=3 ttl=43 time=142 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=4 ttl=44 time=143 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=6 ttl=44 time=140 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=8 ttl=43 time=142 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=10 ttl=43 time=146 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=11 ttl=43 time=145 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=12 ttl=44 time=151 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=13 ttl=43 time=167 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=14 ttl=44 time=149 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=15 ttl=44 time=145 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=16 ttl=44 time=141 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=17 ttl=43 time=142 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=19 ttl=44 time=143 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=20 ttl=44 time=155 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=22 ttl=43 time=145 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=23 ttl=43 time=158 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=24 ttl=44 time=143 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=26 ttl=44 time=145 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=28 ttl=44 time=141 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=29 ttl=44 time=141 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=30 ttl=43 time=145 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=31 ttl=43 time=145 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=32 ttl=44 time=143 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=33 ttl=44 time=146 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=34 ttl=44 time=142 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=35 ttl=44 time=150 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=36 ttl=43 time=144 ms
Actually the results are quite different. You are getting around 30% packet loss with 800 byte packets. I suspect you'll see even higher packet loss the closer you get to 1500 bytes. That will cause any connection to be extremely crummy if not impossible. The ping is also just to my router/firewall so it has to be my modem or something on my ISP's end (or my firewall which I can eliminate as soon as I get home). I had the daughter reboot the modem today and that didn't help so it's either broke or the ISP has a faulty piece of equipment.
Uh, the results looked pretty similar to me but if you say I have around 30% packet loss I take your word for it, it's probably written somewhere where I don't know what to look for then.
I remember when I used to ping from winblows machines I had a result that actually told me how much lost packets I had and since I didn't see this anywhere now I assumed I didn't have any ost packets .....
I remember when I used to ping from winblows machines I had a result that actually told me how much lost packets I had and since I didn't see this anywhere now I assumed I didn't have any ost packets .....
When you break out of a ping with a ^C it *should* give you the statistics at the bottom, including how many packets were transmitted, how many were received and the amount of packet loss. All you do to figure out the packet loss is to look at your packet sequence numbers and count how may are missing vs how many were transmitted. If you'll notice on yours 36 packets were transmitted but many are missing.
Ah, I break out of running stuff with ^Z normally and that doesn't give me anything besides my regular prompt but with ^C I get this
Thanks for the tip!
Code: Select all
--- voidmain.is-a-geek.net ping statistics ---
25 packets transmitted, 19 received, 24% packet loss, time 24023ms
rtt min/avg/max/mdev = 141.770/148.835/201.321/13.264 ms
pretty bogging right enough. i didn't know you could ^Z out of things (actually i remember reading it years ago and thinking there's no need if i can ^C).bash-3.1$ ping -s 800 voidmain.is-a-geek.net
PING voidmain.is-a-geek.net (68.188.13.164) 800(828) bytes of data.
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=1 ttl=41 time=169 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=4 ttl=41 time=176 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=6 ttl=41 time=169 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=7 ttl=41 time=169 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=8 ttl=41 time=168 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=9 ttl=41 time=167 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=10 ttl=41 time=170 ms
808 bytes from 68-188-13-164.dhcp.stls.mo.charter.com (68.188.13.164): icmp_seq=11 ttl=41 time=169 ms
--- voidmain.is-a-geek.net ping statistics ---
11 packets transmitted, 8 received, 27% packet loss, time 10069ms
rtt min/avg/max/mdev = 167.796/170.103/176.042/2.403 ms
You can't ^Z out of things. What ^Z does is actually suspend a process. Do not use ^Z unless you really mean to use ^Z. Normally what you use that for is to suspend the process and then put it into the background to run. For example:
$ ping somewhere.com > /tmp/ping.log 2>&1
$ ^Z
$ bg %1
So every time you ^Z a process you will still see it in the process list in the suspended state consuming just as much memory as it was when you pressed ^Z. If you want suspended processes all over the place then go ahead and use ^Z. :)
$ ping somewhere.com > /tmp/ping.log 2>&1
$ ^Z
$ bg %1
So every time you ^Z a process you will still see it in the process list in the suspended state consuming just as much memory as it was when you pressed ^Z. If you want suspended processes all over the place then go ahead and use ^Z. :)
Ok, I've wiggled all the cables and reset the switches router and modem. I also was able to wget an 8MB kernel patch file from kernel.org in 27 seconds. It seems my downlink is fine, just the uplink seems to be the problem. By the way, the void site is snappy as can be from home. :) I guess I'll have to file a report with the ISP and see if they can get it fixed. Let me know if it's still slow.
what a surprise! i actuall ysuspected that you might not know about it being slow from the rest of the world which is why i posted here in the first place! in fact i was about to send an email to your linuxmail address but then your site picked up enough to start a new thread.By the way, the void site is snappy as can be from home.