connmon connmon - Internet connection monitoring

[Doug Nix]

Running connmon on my RT-AC68U without a hitch. My connection is (theoretically) 1000 Gbs down/25 Gbs up. Working like a champ!

Thanks for another great tool Jack!

 

[Zonkd]

Fantastic script Jack, running perfectly on AC86U 24/7 for weeks now since first release. You're a legend, pat on the back.

 

[Doug Nix]

Jack,
I upgraded my RT-AC68U to the 380.11 firmware, and now the graphs are broken. Itried reinstalling the connmon script, but no change. Any thoughts?

 

[visortgw]

Jack,
I upgraded my RT-AC68U to the 380.11 firmware, and now the graphs are broken. Itried reinstalling the connmon script, but no change. Any thoughts?
View attachment 17564

Try launching common from the command line.

 

[QuikSilver]

Jack,
I upgraded my RT-AC68U to the 380.11 firmware, and now the graphs are broken. Itried reinstalling the connmon script, but no change. Any thoughts?
View attachment 17564

I assume you meant 384.11 not 380.11. I've gotten that as well and usually wait....the graphs don't generate instantly.

 

[Jack Yaz]

v1.1.0 is available
Changelog:

New directory structure in /jffs/scripts
uiDivStats compatibility

After updating also run

connmon startup

 

[webs0r]

Hi Jack thanks for the script
I just updated to 1.1.0, previously working fine.

After update I get this on the webui

I don't run Diversion/uidivstats. Any ideas?

 

[visortgw]

Hi Jack thanks for the script
I just updated to 1.1.0, previously working fine.

After update I get this on the webui
View attachment 17587

I don't run Diversion/uidivstats. Any ideas?

Did you execute "connmon startup" after the upgrade?

 

[webs0r]

I did. Hm, for some reason, the problem has resolved itself! Maybe just needed some time.

Thanks!

 

[QuikSilver]

I did. Hm, for some reason, the problem has resolved itself! Maybe just needed some time.

Thanks!

The graphs don’t generate instantly, they take some time.


Sent from my iPhone using Tapatalk

 

[RiskyBusiness]

Last 7 Days

Above, the past 7 days, center graph is labeled "Jitter" but the index (little green box) says ping.

 

[Swistheater]

Running connmon on my RT-AC68U without a hitch. My connection is (theoretically) 1000 Gbs down/25 Gbs up. Working like a champ!
View attachment 17300 View attachment 17301

Thanks for another great tool Jack!

I remember running the spdmerlin test and it rebooting my router at these theoretical speeds.

 

[Doug Nix]

So my graphs are displaying perfectly now as you can see below...

As far as connmon causing my router any instability, although my line speed to the Rogers backbone is theoretically 1000/25 Mb/s , my real speed to the Internet is normally below 250/15 Mb/s :-(. Just reality of Canadian internet service...

 

[joe scian]

very interesting results overnight. My ping reduced from 38ms ( where it has been for over a month ) to 17ms. My public IP address didnt change - its fixed. I wonder what changed in my service provider network? This has definitely happened before - great to capture this with connmon. Thanks Jack.
I will do a traceroute if it goes back to 38ms and see if the routing is different? Does this sound like a correct approach? Not that I could really do anything about it or that Exetel would do anything about it. I guess this is all to do with load balancing in the service provider network??

traceroute to www.google.com (216.58.199.68), 30 hops max, 38 byte packets
 1  20.1.233.220.static.exetel.com.au (220.233.1.20)  16.942 ms  17.233 ms  16.907 ms
 2  10.1.23.238 (10.1.23.238)  17.718 ms  17.641 ms  17.942 ms
 3  161.8.96.58.static.exetel.com.au (58.96.8.161)  17.212 ms  21.388 ms  17.505 ms
 4  108.170.247.49 (108.170.247.49)  18.962 ms  108.170.247.81 (108.170.247.81)  18.023 ms  108.170.247.49 (108.170.247.49)  19.310 ms
 5  209.85.248.253 (209.85.248.253)  18.049 ms  209.85.248.173 (209.85.248.173)  17.822 ms  209.85.248.253 (209.85.248.253)  18.148 ms
 6  syd15s01-in-f4.1e100.net (216.58.199.68)  18.201 ms  17.862 ms  17.457 ms

 

[Swistheater]

very interesting results overnight. My ping reduced from 38ms ( where it has been for over a month ) to 17ms. My public IP address didnt change. I wonder what changed in my service provider network? This has definitely happened before - great to capture this with connmon. Thanks Jack.
I will do a traceroute if it goes back to 38ms and see if the routing is different? Does this sound like a correct approach?

traceroute to www.google.com (216.58.199.68), 30 hops max, 38 byte packets
 1  20.1.233.220.static.exetel.com.au (220.233.1.20)  16.942 ms  17.233 ms  16.907 ms
 2  10.1.23.238 (10.1.23.238)  17.718 ms  17.641 ms  17.942 ms
 3  161.8.96.58.static.exetel.com.au (58.96.8.161)  17.212 ms  21.388 ms  17.505 ms
 4  108.170.247.49 (108.170.247.49)  18.962 ms  108.170.247.81 (108.170.247.81)  18.023 ms  108.170.247.49 (108.170.247.49)  19.310 ms
 5  209.85.248.253 (209.85.248.253)  18.049 ms  209.85.248.173 (209.85.248.173)  17.822 ms  209.85.248.253 (209.85.248.253)  18.148 ms
 6  syd15s01-in-f4.1e100.net (216.58.199.68)  18.201 ms  17.862 ms  17.457 ms

View attachment 18333
View attachment 18334View attachment 18335View attachment 18336

the ISP probably noticed there was optimizations need along that route due to your continuous pinging and they are now using it to monitor you more closely..... or maybe the location you chose to ping is more responsive to you now, maybe it opened closer servers.

 

[Adamm]

very interesting results overnight. My ping reduced from 38ms ( where it has been for over a month ) to 17ms. My public IP address didnt change - its fixed. I wonder what changed in my service provider network? This has definitely happened before - great to capture this with connmon. Thanks Jack.
I will do a traceroute if it goes back to 38ms and see if the routing is different? Does this sound like a correct approach? Not that I could really do anything about it or that Exetel would do anything about it. I guess this is all to do with load balancing in the service provider network??

traceroute to www.google.com (216.58.199.68), 30 hops max, 38 byte packets
 1  20.1.233.220.static.exetel.com.au (220.233.1.20)  16.942 ms  17.233 ms  16.907 ms
 2  10.1.23.238 (10.1.23.238)  17.718 ms  17.641 ms  17.942 ms
 3  161.8.96.58.static.exetel.com.au (58.96.8.161)  17.212 ms  21.388 ms  17.505 ms
 4  108.170.247.49 (108.170.247.49)  18.962 ms  108.170.247.81 (108.170.247.81)  18.023 ms  108.170.247.49 (108.170.247.49)  19.310 ms
 5  209.85.248.253 (209.85.248.253)  18.049 ms  209.85.248.173 (209.85.248.173)  17.822 ms  209.85.248.253 (209.85.248.253)  18.148 ms
 6  syd15s01-in-f4.1e100.net (216.58.199.68)  18.201 ms  17.862 ms  17.457 ms

View attachment 18333
View attachment 18334View attachment 18335View attachment 18336

Exetel have been recently upgrading their network while deploying IPv6. They must have improved peering to google while correcting other issues this week, Telstra for example had 160ms latency for months during the switch over to superloop backhaul. Scratch that, latency to some telstra services still sucks.

 

[consorts]

can we hard code in the ip4 this app is pinging to? if so, where/how?

 

[Jack Yaz]

can we hard code in the ip4 this app is pinging to? if so, where/how?

option 2 on the menu

 

[joe scian]

That didnt last very long at all with Exetel - not even 24 hrs - back to 38ms ping -

traceroute to www.google.com (172.217.25.164), 30 hops max, 38 byte packets
 1  20.1.233.220.static.exetel.com.au (220.233.1.20)  38.842 ms  38.533 ms  38.703 ms
 2  10.1.23.238 (10.1.23.238)  38.717 ms  38.898 ms  39.156 ms
 3  161.8.96.58.static.exetel.com.au (58.96.8.161)  42.422 ms  38.914 ms  45.169 ms
 4  108.170.247.33 (108.170.247.33)  40.195 ms  40.927 ms  40.468 ms
 5  108.170.235.193 (108.170.235.193)  39.251 ms  108.170.235.195 (108.170.235.195)  38.845 ms  39.024 ms
 6  sin01s16-in-f4.1e100.net (172.217.25.164)  39.149 ms  38.866 ms  39.124 ms

 

[Grisu]

would have been too nice ...