A better way to monitor my internet connection other than ping

All we need is an easy explanation of the problem, so here it is.

edit: despite the very good answer I once accepted, now I’m look for a simpler tool that requires no installation or preparation. Something like a ping with a timestamp would be of great help already.

Once in a while I get bad Internet connection access points. Be it physical cables, WiFi or 3G spots. And I always figured how good would it be to have a way to monitor it, to determine exactly where’s the issue and either consider trying to fix it or just accept there’s no way.

My current way of doing it is freaking ping. I ping any Internet IP I memorized and the Gateway. That tells me if the router is bad, eventually. Or that the Internet fell down, and it’s not my computer issue, but not for how long it’s down. Neither that it did so X hours ago, and that’s why my download didn’t went through, rather than some torrent issue, or server maintenance. And so on. Ping is a very old tool and not full featured at all.

Currently came to my attention another way of doing it: logmein logs (idea came from looking at console). But I couldn’t make much use of any of those logs so far. Anyway…

Here I ask if there is any software, free and/or paid, that can give us those basic stats about our current network connection. And a connection graphic over time would be a big plus!

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

You are looking for mtr. I always leave mtr 8.8.8.8 running.

If you’re not familiar with 8.8.8.8, it’s Google’s global DNS service, using anycast, so you always get a nearby node, and it’s a dead easy IP to remember. So it works no matter where you are located, and if you move.

Once mtr starts press d once, then you’ll see the last X pings, beautiful.

                            My traceroute  [v0.82]
host.local (0.0.0.0)                                   Sat Jun 14 14:10:27 2014
Keys:  Help   Display mode   Restart statistics   Order of fields   quit

                             Last  50 pings
 1. 192.168.1.1              .....?.........?...............?.........??.......
 2. 87.186.224.71            ..................................................
 3. 87.190.171.194           ..................................................
 4. b-ea6-i.B.DE.NET.DTAG.DE ..................................................
 5. 194.25.211.30            ..................................................
 6. 209.85.249.182           ..................................................
 7. 66.249.95.175            ..................................................
 8. 216.239.48.53            ..................................................
 9. 0.0.0.0                  ??????????????????????????????????????????????????
10. google-public-dns-a.goog .................................................?

Scale:  .:3 ms  1:6 ms  2:9 ms  3:17 ms  a:35 ms  b:53 ms  c:85 ms

Pro tip: Stretch your window to the last 200 pings… 🙂

Method 2

If all of your devices can do SNMP, you could use MRTG http://oss.oetiker.ch/mrtg/

Alternately, you could run smokeping. http://oss.oetiker.ch/smokeping/

Either one should give you some nice graphs, you can see when your network use is high, when it’s utterly flat, etc.

You can use Nagios to alert you when there’s a problem, smokeping might do it to, it’s been awhile since I’ve used it.

Method 3

I created this simple batch file:

@echo off
echo Internet Service Availability for %date%
:again
ping 70.45.95.8 -n 1 -l 1
time /T
timeout /T 300 > nul
goto again

Run it redirecting it to a file the like c:>run.bat > statuslog.txt. The /T flag of the timeout command sets the pooling time interval, in this case 5 minutes. The /T flag for the time command provides the time stamp. You can then check the created file for reply or request time out patterns.

Another alternative (the one I prefer), is to use one of the following freeware utilities that provides a more professional result:

Pingplotter Freeware
EMCO Ping Monitor free
Internet Connectivity Monitor (java app)

Method 4

  1. Switch from using ping to tracepath (traceroute)
  2. Install Nagios (it is available for Windows too), then write a tracepath/ping module (or take something from a standart bundle)

Method 5

…or use fping:

$ fping -lsQ 60 192.168.0.1

192.168.178.1 : xmt/rcv/%loss = 60/60/0%, min/avg/max = 2.04/3.57/7.67
192.168.178.1 : xmt/rcv/%loss = 60/60/0%, min/avg/max = 2.01/3.30/8.47
^C192.168.178.1 : xmt/rcv/%loss = 156/156/0%, min/avg/max = 2.01/3.40/8.47

       1 targets
       1 alive
       0 unreachable
       0 unknown addresses

       0 timeouts (waiting for response)
     156 ICMP Echos sent
     156 ICMP Echo Replies received
       0 other ICMP received

 2.01 ms (min round trip time)
 3.40 ms (avg round trip time)
 8.47 ms (max round trip time)
      156.000 sec (elapsed real time)

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply