<div dir="ltr">Thanks, Michael! I am going to chew on this for a while. :-)</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 28, 2016 at 7:06 PM, Michael Paoli <span dir="ltr"><<a href="mailto:Michael.Paoli@cal.berkeley.edu" target="_blank">Michael.Paoli@cal.berkeley.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You might want to start with closest hop router.<br>
It's likely default. Can find that with the ip command.<br>
If that command isn't on (your mere mortal user) PATH,<br>
it's typically in /sbin or /usr/sbin, so could use absolute<br>
(starts with /) path to the program instead (e.g. prepend ip<br>
with /sbin/ or /usr/sbin/). So e.g. I find from my example<br>
host:<br>
$ ip r s<br>
default via 198.144.194.233 dev br0<br>
<a href="http://192.168.55.0/24" rel="noreferrer" target="_blank">192.168.55.0/24</a> dev br0 proto kernel scope link src 192.168.55.1<br>
<a href="http://192.168.122.0/24" rel="noreferrer" target="_blank">192.168.122.0/24</a> dev virbr0 proto kernel scope link src 192.168.122.1<br>
<a href="http://198.144.194.232/29" rel="noreferrer" target="_blank">198.144.194.232/29</a> dev br0 proto kernel scope link src 198.144.194.235<br>
$<br>
So, most notable there, would be the IP that shows in the<br>
default route:<br>
198.144.194.233<br>
Interestingly/oddly that command didn't show my IPv6 bits, but that<br>
may not matter for your setup. Anyway, giving option to just show<br>
the IPv6, I have:<br>
$ ip -6 r s<br>
2001:470:66:76f::1 dev he-ipv6 metric 1024<br>
2001:470:66:76f::/64 dev he-ipv6 proto kernel metric 256<br>
fe80::/64 dev br0 proto kernel metric 256<br>
fe80::/64 dev he-ipv6 proto kernel metric 256<br>
fe80::/64 dev vnet0 proto kernel metric 256<br>
default via 2001:470:66:76f::1 dev he-ipv6 metric 1024<br>
$<br>
... so in that case, for the IPv6 portion, default router IP:<br>
2001:470:66:76f::1<br>
<br>
Anyway, should be able to ping your default router IP(s),<br>
ping(1) for IPv4, ping6 for IPv6, e.g.:<br>
$ ping -n -c 5 198.144.194.233<br>
PING 198.144.194.233 (198.144.194.233) 56(84) bytes of data.<br>
64 bytes from <a href="http://198.144.194.233" rel="noreferrer" target="_blank">198.144.194.233</a>: icmp_seq=1 ttl=255 time=29.3 ms<br>
64 bytes from <a href="http://198.144.194.233" rel="noreferrer" target="_blank">198.144.194.233</a>: icmp_seq=2 ttl=255 time=10.6 ms<br>
64 bytes from <a href="http://198.144.194.233" rel="noreferrer" target="_blank">198.144.194.233</a>: icmp_seq=3 ttl=255 time=11.2 ms<br>
64 bytes from <a href="http://198.144.194.233" rel="noreferrer" target="_blank">198.144.194.233</a>: icmp_seq=4 ttl=255 time=11.3 ms<br>
64 bytes from <a href="http://198.144.194.233" rel="noreferrer" target="_blank">198.144.194.233</a>: icmp_seq=5 ttl=255 time=12.1 ms<br>
<br>
--- 198.144.194.233 ping statistics ---<br>
5 packets transmitted, 5 received, 0% packet loss, time 4003ms<br>
rtt min/avg/max/mdev = 10.676/14.960/29.305/7.188 ms<br>
$<br>
and for IPv6:<br>
$ ping6 -n -c 5 2001:470:66:76f::1<br>
PING 2001:470:66:76f::1(2001:470:66:76f::1) 56 data bytes<br>
64 bytes from 2001:470:66:76f::1: icmp_seq=1 ttl=64 time=15.0 ms<br>
64 bytes from 2001:470:66:76f::1: icmp_seq=2 ttl=64 time=15.4 ms<br>
64 bytes from 2001:470:66:76f::1: icmp_seq=3 ttl=64 time=15.0 ms<br>
64 bytes from 2001:470:66:76f::1: icmp_seq=4 ttl=64 time=15.1 ms<br>
64 bytes from 2001:470:66:76f::1: icmp_seq=5 ttl=64 time=14.2 ms<br>
<br>
--- 2001:470:66:76f::1 ping statistics ---<br>
5 packets transmitted, 5 received, 0% packet loss, time 4005ms<br>
rtt min/avg/max/mdev = 14.216/14.971/15.440/0.426 ms<br>
$<br>
<br>
You may also be able to isolate issues with traceroute, e.g. using<br>
TCP with traceroute (need to be superuser ("root") to do this, so<br>
sudo or as root, so, e.g.:<br>
$ dig -t A <a href="http://www.google.com" rel="noreferrer" target="_blank">www.google.com</a>. +short<br>
172.217.1.228<br>
$ sudo traceroute -n -T -p 443 172.217.1.228<br>
traceroute to 172.217.1.228 (172.217.1.228), 30 hops max, 60 byte packets<br>
1 198.144.194.233 10.857 ms 12.343 ms 14.765 ms<br>
2 216.131.94.209 16.936 ms 19.052 ms *<br>
3 * * 173.205.60.193 21.125 ms<br>
4 89.149.180.42 30.564 ms * 141.136.106.206 33.101 ms<br>
5 199.229.230.134 37.055 ms 37.975 ms 41.609 ms<br>
6 216.239.49.168 42.531 ms 34.588 ms 39.405 ms<br>
7 64.233.174.91 46.842 ms 49.246 ms 209.85.246.38 53.627 ms<br>
8 64.233.174.204 65.770 ms 58.009 ms 57.582 ms<br>
9 209.85.248.124 55.769 ms 64.233.174.191 56.836 ms 55.163 ms<br>
10 * * *<br>
11 172.217.1.228 43.975 ms 42.202 ms 37.240 ms<br>
$<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
From: "Christian Einfeldt" <<a href="mailto:einfeldt@gmail.com" target="_blank">einfeldt@gmail.com</a>><br>
Subject: Re: [Tech] Need help with the Internet at the Mentone ("slow" ... latency? and/or connectivity?)<br>
Date: Tue, 28 Jun 2016 11:01:07 -0700<br>
</blockquote><div class="HOEnZb"><div class="h5">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Mike,<br>
<br>
How do I get the IP address for the switch? Googling doesn't seem to be<br>
helping me here, I just be asking the wrong question?<br>
<br>
The speedtest does work on that machine from home using the same machine<br>
and the same ethernet cable. Thanks!<br>
<br>
On Tue, Jun 28, 2016 at 8:05 AM, Michael Rojas <<br>
<a href="mailto:ledworldwide.solutions@gmail.com" target="_blank">ledworldwide.solutions@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Christian,<br>
<br>
It looks like you are experiencing heavy packet loss from the lobby. My<br>
next step would be to ping a switch or server on the local network from the<br>
lobby to try and narrow down where the problem lies (bad switch/router<br>
config, bad cable ...?)<br>
<br>
Why the speed test didn't work from the basement is a mystery though. Is<br>
the speedtest working from another location (from home)?<br>
<br>
-Mike Rojas-<br>
<br>
<br>
<br>
On Fri, Jun 24, 2016 at 11:46 PM, Christian Einfeldt <<a href="mailto:einfeldt@gmail.com" target="_blank">einfeldt@gmail.com</a>><br>
wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, Thanks for your thoughts, Michael.<br>
<br>
On Fri, Jun 24, 2016 at 1:44 PM, Michael Paoli <<br>
<a href="mailto:Michael.Paoli@cal.berkeley.edu" target="_blank">Michael.Paoli@cal.berkeley.edu</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sounds like you've got latency issue, not necessarily bandwidth<br>
issue(s). The very long times on ping to Google would<br>
reflect latency issues. It's not uncommon for ISPs to support<br>
large buffering - this gives 'em a slight edge in most typical<br>
bandwidth tests ... and the cost of latency - as/when the<br>
bandwidth is quite saturated, buffers fill, and hence latency<br>
can be quite to even exceedingly high. This can then trigger various<br>
errors, such as DNS timeouts - which might well be why your<br>
"speed tests" failed - but can't really tell from the limited output<br>
that check provided (the CLI tool may have options for more details,<br>
and/or one may use additional diagnostics to check what's happening<br>
when the speed test is attempted - which may then make clear why the<br>
test is failing). Shared usage of bandwidth can be an issue, e.g.<br>
multiple computers, etc., and single "pipe" of some fixed limited<br>
bandwidth to Internet. If one machine is hogging it all, or even<br>
multiple are together trying to use all the bandwidth, that will<br>
make it "slow" for them, and anything else attempting to share that<br>
bandwidth.<br>
<br>
Anyway, realized and understand that bandwidth (speed), and latency<br>
(how long does the trip take) are not the same thing. Either may<br>
be perceived as "slow", depending upon the nature of the usage.<br>
<br>
If, as you mention, you're having problems even doing the updates,<br>
it's likely either issues with latency causing issues with DNS,<br>
and/or more general connectivity issues (which may also be caused<br>
by latency issues). "Slow" - as in low bandwidth, will not<br>
in-and-of-itself break "speed"tests or getting updates on-line ...<br>
were it only a bandwidth issue, things would just take longer ...<br>
possibly *much* longer.<br>
<br>
From: "Christian Einfeldt" <<a href="mailto:einfeldt@gmail.com" target="_blank">einfeldt@gmail.com</a>><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Subject: [Tech] Need help with the Internet at the Mentone<br>
Date: Fri, 24 Jun 2016 11:50:55 -0700<br>
<br>
</blockquote>
<br>
Hi,<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Here are my questions:<br>
<br>
1. Why did my speed tests fail in this situation?<br>
2. Are the ping speeds normal for this situation?<br>
3. What diagnostic tests can I run to isolate the slowness on this<br>
system?<br>
<br>
As most people on this list know, Partimus is volunteering for a low<br>
income<br>
housing shelter in here in SF. I have put in some quality legacy<br>
Lubuntu<br>
machines in the lobby for the residents to use. These machines all have<br>
Intel Core 2 duo chips with 2 GB of RAM and are running Lubuntu 14.04.<br>
I<br>
use a similar machine at home, and have no problems with it. This<br>
email is<br>
being written on such a machine at one of the other two homeless<br>
shelters.<br>
The residents routinely use these machines to watch YouTube video and<br>
use<br>
LibreOffice, etc., all without issue. The machines are proven good.<br>
<br>
This is the third shelter to which we have given machines. They don't<br>
have<br>
a budget for either the equipment or the tech support for these<br>
machines.<br>
<br>
Two of the three shelters have good speed on the Internet that goes to<br>
the<br>
machines. (The shelters provide the Internet service).<br>
<br>
However, the third shelter, called the Mentone, has slow Internet<br>
speeds in<br>
the lobby. I am not able to even do anything as basic as run sudo<br>
apt-get<br>
update, as the machine chokes on downloading the updates.<br>
<br>
The wiring is put in place by a company I will call the Maintenance<br>
Group<br>
(MG). I have called both the MG and the ISP. Both of them claim that<br>
they<br>
have no problems. The ISP says that they are providing the usual 2<br>
Mbit /<br>
second that we expect here in the US for a configuration like this.<br>
The MG<br>
says that they have run a test on the wiring from the server to the<br>
lobby,<br>
and are not seeing any problems.<br>
<br>
The ISP is a good company that does not hate GNU-Linux.<br>
<br>
The ISP asked me to give them a speed test directly from the switch,<br>
which<br>
is located in the basement. So I ran speed tests in the basement and in<br>
the lobby, and was unable to get the speed test to work. Speed test has<br>
worked on this machine before. Here are the two results:<br>
<br>
Lobby, where the Lubuntu machine is to be located:<br>
<br>
cje@cje-ultralap440:~$ speedtest-cli<br>
<br>
Retrieving <a href="http://speedtest.net" rel="noreferrer" target="_blank">speedtest.net</a> configuration...<br>
<br>
Could not retrieve <a href="http://speedtest.net" rel="noreferrer" target="_blank">speedtest.net</a> configuration: timed out<br>
<br>
cje@cje-ultralap440:~$ ifconfig<br>
<br>
eth0 Link encap:Ethernet HWaddr 20:1a:06:04:64:42<br>
inet addr:172.16.2.121<br>
<br>
basement, directly from the switch:<br>
<br>
cje@cje-ultralap440:~$ speedtest-cli<br>
<br>
Retrieving <a href="http://speedtest.net" rel="noreferrer" target="_blank">speedtest.net</a> configuration...<br>
<br>
Could not retrieve <a href="http://speedtest.net" rel="noreferrer" target="_blank">speedtest.net</a> configuration: timed out<br>
<br>
cje@cje-ultralap440:~$<br>
<br>
*My first question: *I am not sure why this speed test failed. Does<br>
anyone know?<br>
<br>
Since I couldn't run speedtest, I pinged google instead. Here are the<br>
results from the lobby:<br>
<br>
cje@cje-ultralap440:~$ ping <a href="http://www.google.com" rel="noreferrer" target="_blank">www.google.com</a><br>
<br>
PING <a href="http://www.google.com" rel="noreferrer" target="_blank">www.google.com</a> (216.58.192.4) 56(84) bytes of data.<br>
<br>
64 bytes from <a href="http://nuq04s29-in-f4.1e100.net" rel="noreferrer" target="_blank">nuq04s29-in-f4.1e100.net</a> (216.58.192.4): icmp_seq=1<br>
ttl=52<br>
time=8.24 ms<br>
<br>
64 bytes from <a href="http://nuq04s29-in-f4.1e100.net" rel="noreferrer" target="_blank">nuq04s29-in-f4.1e100.net</a> (216.58.192.4): icmp_seq=2<br>
ttl=52<br>
time=7.31 ms<br>
<snip><br>
<br>
--- <a href="http://www.google.com" rel="noreferrer" target="_blank">www.google.com</a> ping statistics ---<br>
<br>
16 packets transmitted, 12 received, 25% packet loss, time 15037ms<br>
<br>
rtt min/avg/max/mdev = 6.962/7.497/8.198/0.366 ms<br>
<br>
Here is the test from the basement:<br>
<br>
cje@cje-ultralap440:~$ ping <a href="http://www.google.com" rel="noreferrer" target="_blank">www.google.com</a><br>
<br>
PING <a href="http://www.google.com" rel="noreferrer" target="_blank">www.google.com</a> (216.58.192.4) 56(84) bytes of data.<br>
<br>
64 bytes from <a href="http://nuq04s29-in-f4.1e100.net" rel="noreferrer" target="_blank">nuq04s29-in-f4.1e100.net</a> (216.58.192.4): icmp_seq=1<br>
ttl=52<br>
time=8.24 ms<br>
<br>
64 bytes from <a href="http://nuq04s29-in-f4.1e100.net" rel="noreferrer" target="_blank">nuq04s29-in-f4.1e100.net</a> (216.58.192.4): icmp_seq=2<br>
ttl=52<br>
time=7.31 ms<br>
<snip><br>
<br>
--- <a href="http://www.google.com" rel="noreferrer" target="_blank">www.google.com</a> ping statistics ---<br>
<br>
11 packets transmitted, 11 received, 0% packet loss, time 10015ms<br>
<br>
rtt min/avg/max/mdev = 7.022/7.816/8.519/0.451 ms<br>
<br>
cje@cje-ultralap440:~$<br>
<br>
*My second question*: Are these ping speeds normal?<br>
<br>
My third question: What can I do to find the problem with the system?<br>
<br>
Thanks!<br>
<br>
--<br>
Christian Einfeldt<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
--<br>
Christian Einfeldt<br>
<br>
_______________________________________________<br>
Tech mailing list<br>
<a href="mailto:Tech@lists.partimus.org" target="_blank">Tech@lists.partimus.org</a><br>
<a href="http://lists.partimus.org/listinfo.cgi/tech-partimus.org" rel="noreferrer" target="_blank">http://lists.partimus.org/listinfo.cgi/tech-partimus.org</a><br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
--<br>
Christian Einfeldt<br>
<br>
</blockquote>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Christian Einfeldt</div>
</div>