Offline

Tue Jan 3 13:14:11 MST 2017

MTR began being installed by default in place of traceroute.  If you don't
know mtr, get it in your life.  It's usually how I know when cox has
saturation issues at their peering with buffers killing my internet, and
replaces traceroute in any number of ways.

> mtr google.com

> mtr --report -c 5 google.com
Start: Tue Jan  3 13:11:33 2017
HOST: host                       Loss%   Snt   Last   Avg  Best  Wrst StDev
 1.|-- fw1.peoria1.unifiedconver  0.0%     5    0.3   0.3   0.2   0.3   0.0
 2.|-- ???                       100.0     5    0.0   0.0   0.0   0.0   0.0
 3.|-- 100.127.69.154             0.0%     5    9.3   9.1   8.2  10.6   0.7
 4.|-- 72.215.229.22              0.0%     5    9.1  11.0   9.1  13.4   2.0
 5.|-- langbprj02-ae1.0.rd.la.co  0.0%     5   21.7  21.7  21.2  22.5   0.0
 6.|-- 72.14.215.221              0.0%     5   21.1  21.4  21.1  22.1   0.0
 7.|-- 216.239.51.33              0.0%     5   22.9  22.0  21.4  22.9   0.5
 8.|-- 209.85.246.187             0.0%     5   22.2  21.7  20.6  22.4   0.5
 9.|-- 64.233.174.207             0.0%     5   37.3  37.5  36.3  40.8   1.7
10.|-- 209.85.246.39              0.0%     5   36.4  36.8  35.7  37.8   0.7
11.|-- 108.170.243.1              0.0%     5   39.7  36.9  35.5  39.7   1.5
12.|-- 108.170.237.105            0.0%     5   35.9  36.1  35.0  37.6   0.9
13.|-- sfo03s01-in-f206.1e100.ne  0.0%     5   36.7  36.7  35.4  38.2   1.0

-mb

On Tue, Jan 3, 2017 at 12:41 PM, Carruth, Rusty <Rusty.Carruth at smartm.com>
wrote:

> Excellent step-by-step!  +100 upvotes! ;-)
>
>
>
> The only thing I’d add is that, if you can get an external IP address
> (e.g. 204.110.11.131 (inficad.com - don’t ask) or 216.58.194.206 (one
> possible value for google.com) and then do a traceroute -n to that
> address, you can see (without needing DNS) if the packets get out, and how
> far they get if they don’t get all the way out….
>
>
>
> So, “traceroute -n 216.58.194.206”
>
>
>
> Unfortunately, traceroute is not always installed by default - GO DO THAT
> NOW!!! ;-) Since when you need it, you won’t be able to get it!
>
>
>
> *From:* PLUG-discuss [mailto:plug-discuss-bounces at lists.phxlinux.org] *On
> Behalf Of *Michael Butash
> *Sent:* Tuesday, January 03, 2017 12:34 PM
> *To:* Main PLUG discussion list
> *Subject:* Re: Offline
>
>
>
> Just work your way up the network osi model in troubleshooting.  Everyone
> should learn some networking these days, one way or another (speaking as a
> bofh network guy that deals with non-networking app and developers folk
> commonly - don't be part of the problem).
>
>
> ####
>
> ## Layer 1/2, got link? note "state"
>
>
>
> > ip link
>
>
>
> ## If no link,  check cable plugged in for blinky lights
>
>
> ####
>
> ## Layer 3, got ip?
>
>
>
> > ip addr
>
>
>
> ## If no ip, check dhcp on the network
>
> ## Optional: Set static ip for temporary troubleshooting, insert proper
> subnets here:
>
>
>
> ip addr add 192.168.1.100 255.255.255.0 dev eth0
>
> ip route add default 192.168.1.1
>
>
> ####
>
> ## Layer 3, verify arp to gateway
>
>
>
> ip nei | grep `ip route | grep default | awk '{ print $3 }'`
>
>
>
> ## If no arp for gateway, check router/switch network
>
>
> ####
>
> ## Layer 3, ping the gateway (whatever that is for you)
>
>
>
> ping `ip route | grep default | awk '{ print $3 }'`
>
>
>
> ## If no response, check prior steps again
>
>
> ####
>
> ## Layer 3/4, verify resolv.conf dns resolution and life beyond default
> route
>
>
>
> ping google.com
>
>
>
> ## If no dns life outside router, check the router has connectivity to the
> internet
>
>
>
> ####
>
> ## pull up a browser to google.com to test layer 4-7 stuff
>
>
>
> On Tue, Jan 3, 2017 at 9:10 AM, Carruth, Rusty <Rusty.Carruth at smartm.com>
> wrote:
>
> I’ll guess that DHCP server on your router was dead.
>
>
>
> But to know for sure - are all your systems using DHCP, or are some using
> static?
>
>
>
> IF your windows side is set for static, and the Linux side is DHCP, then
> this would be expected - windows works, linux doesn’t.
>
>
>
> But I’m just guessing (however, I had a router once that would lose its
> DHCP server on a semi-regular basis.  I considered putting it on some sort
> of auto-reboot device (power cycle it once a day) - finally just replaced
> the stupid thing ;-)
>
>
>
> Rusty
>
>
>
> *From:* PLUG-discuss [mailto:plug-discuss-bounces at lists.phxlinux.org] *On
> Behalf Of *Michael
> *Sent:* Monday, January 02, 2017 1:42 PM
> *To:* PLUG
> *Subject:* Re: Offline
>
>
>
> I'm back. I just had to reset the router..... but why would that work if
> windows still worked?
>
>
>
> On Mon, Jan 2, 2017 at 11:31 AM, Michael <bmike1 at gmail.com> wrote:
>
> The TV server, also linux, is still online. It is part of the same network.
>
>
>
> On Jan 2, 2017 11:22 AM, "Michael" <bmike1 at gmail.com> wrote:
>
> I am now offline in my Linux box. Windows is up and happy and the modem is
> up and happy too. Heck, the network connection shows I'm connected too. I
> don't know what to do. What led up to this is I was trying something with
> th faulty SD card. .. grated said to run, chkdsk /f , twice so I boot into
> Windows to do that ,couldn't do it though. Then when I boot back to Linux
> to reformat it there was no connectivity.
>
>
>
>
>
> --
>
> :-)~MIKE~(-:
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20170103/0a4cf6f3/attachment.html>