Here ya go guys! It should be obvious what “variables” that you need to change
:global MAXTX "20000000";
:global MAXRX "20000000";
:global THRESHHOLD "20";
:global STARTTIME "9:58:00";
:global USERNAME "admin";
:global PASSWORD "mypassword";
:global TESTDEST "8.8.8.8";
/system scheduler
add disabled=no name=bwtest2 on-event=":global \"tx-total-average\";\
\n\
\n:global \"rx-total-average\";\
\n\
\n:global upspeed 0;\
\n\
\n:global downspeed 0;\
\n\
\n/tool bandwidth-test $"TESTDEST" user=$"USERNAME" password=$"PASSWORD"
protocol=tcp duration=4s direction=both local-tx-speed=$"MAXTX" \
remote-tx-speed=$"MAXRX" do={\
\n\
\n :set upspeed (\$\"tx-total-average\"/(1024*1024));\
\n\
\n :set downspeed (\$\"rx-total-average\"/(1024*1024));\
\n\
\n :log warning \"TX is \$\"upspeed\"M, RX is \$\"downspeed\"M\"; \
\n}\
\n\
\n\
\n\
\n/tool e-mail send to=\"[email protected]\" subject=([/system identity get
name] . \" bwtest results \" . [/system clock get date]) body=\
\"Upload \$\"upspeed\"M,Download \$\"downspeed\"M\" \
\n\
\n" policy=read,write,test start-date=jan/01/1970 start-time=$"STARTTIME"
interval=24:00:00;
From: Af [mailto:[email protected]] On Behalf Of Shayne Lebrun
Sent: Thursday, April 02, 2015 1:43 PM
To: [email protected]
Subject: Re: [AFMUG] Drop in monitoring device for troubleshooting customers
Can you share this script? Something similar has been on my todo list for far
too long.
From: Af [mailto:[email protected]] On Behalf Of Paul McCall
Sent: Thursday, April 2, 2015 12:08 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [AFMUG] Drop in monitoring device for troubleshooting customers
And, its easy to have an automated BW test script on a Mikrotik to test back to
another TIK at a preset interval.. say once every 30 minutes do a 10 or 30
second BW test.
We have insisted on Tik’s at every install since Jan 2014. GREATLY improved
abilities to troubleshoot. If say a business customer has a VPN router that
they manage etc, then we put a 951-2n (now the cheaper replacement even) in
with all interfaces bridged that we can monitor. Its worth the $ 40 (now $ 20)
in those instances.
Most customers get a 951-2HnD or a 2011 at their house or business with the
radio bridged.
Paul
From: Af [mailto:[email protected]] On Behalf Of Kurt Fankhauser
Sent: Thursday, April 02, 2015 11:44 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [AFMUG] Drop in monitoring device for troubleshooting customers
I drop in a Mikrotik RB941 to customers that have suspected issues. I can
comptletely monitor their entire network that way, WIFI and all.
Kurt Fankhauser
Wavelinc Communications
P.O. Box 126
Bucyrus, OH 44820
http://www.wavelinc.com<http://www.wavelinc.com/>
tel. 419-562-6405
fax. 419-617-0110
On Thu, Apr 2, 2015 at 11:41 AM, That One Guy /sarcasm
<[email protected]<mailto:[email protected]>> wrote:
Im dealing with a customer with what appears to be a legitimate complaint of
slowness, high latency.
The biggest problem is its happenning at night so its not like we can go to his
house and troubleshoot. The issue doesnt appear to be visible in any of our
monitoring, but we are limited to viewing from this end and not his
I had him download pingplotter and leave it running to a specific IP so show us
his outbound path when this is going on, but so far it hasnt resulted in
anything useful.
I do have an air router set up as a monitoring bridge between his 450 and his
router from when we were troubleshooting his 2.4 fsk before we switch him to
3.65. As far as I can tell this isnt a radio issue, hes always 8x/8x
Is there any custom load to drop into this air router that would give me some
tools like iperf or any other nifty networking tools that would give me the
equivalent of a console at his house to troubleshoot from?
We have a bunch of old thin clients laying around here I have considered
dropping some lightweight linux onto for a drop in toolset, is anyone aware of
any specific load for that purpose?
--
If you only see yourself as part of the team but you don't see your team as
part of yourself you have already failed as part of the team.
