We have published an updated version of our Bandwidth Test version for Windows with some minor tweaks and authentication support for RouterOS versions newer than 6.43.
Please remember that Bandwidth Test uses a lot of resources. If you want to test real throughput of a router, you should run Bandwidth Test through the tested router not from or to it. To do this you need at least 3 devices connected in chain: the Bandwidth Test server, the router being tested and the Bandwidth Test client.
However after a quick test, it doesn’t seems like it’s working correctly:
If local Tx/Remote Tx speeds are not set, it will just not do anything (if using direction=receive):
If direction is set to send, it starts sending data but at very low rate like 1264bps and never goes above that:
With speeds set manually, TCP testing is now working well: (deleted the UDP testing screenshots, as Tx sizes were incorrect and prevented it from working… DOH!)
All testing done between directly connected PC and RB800, link at 1Gb/s. Router CPU never went above 50%. Using no firewalls or any software that would prevent it from working.
Small update: Local Tx and Remote Tx speeds just must not be grayed out. If you set them to 0 bps, btest will automatically ramp up the rate and now everything works.
Also tried using the server feature in btest, but router can’t connect to it, no matter if using UDP or TCP.
Going to server tab, checking “Enabled” and pressing “Apply settings” does nothing. I don’t even see open btest TCP port…
I have no firewall software, not even the windows one, double checked it’s turned off and disabled on all interfaces.
Also used process explorer to see what ports is btest.exe using and it does have no open or listening ports when it should be running.
Never mind, found the culprit: Some other SW had TCP port 2000 open…
And if it can’t bind the TCP port 2000, UDP server also doesn’t work…
Also found you can get some debug messages if you redirect btest.exe stdout to file: btest.exe > log.txt
This version is very stable and convenient to use, I am very grateful to MikroTik that I am able to use it without involving WebFig, I’d love to have settings search though so I could find the thing I want to change easier, but it’s rather an overall WinBox design complain. Also design is good, not really Material Design but fits well in Android ecosystem.
Tab button not working is annoying but the most annoying is we must input tx speed. This is bandwidth test, to measure maximum speed we can get. Isnt it silly if we must input tx speed?
I was able to get it to work, but had to add in 1000M into TX and RX field, or otherwise it didn’t really push bandwidth. Also the Tab between fields I noticed doesn’t work. But this utility was helpful for me to optimize local networks between laptop and mikrotik routers to fine tune settings on NIC and WILAN. Thanks for making improvements.
Verified with Task Manager on my PC and interface traffic graph on the Tik side.
PC and Tik show numbers which are more or less in the same area (a bit of difference is always possible).
PC Btest app shows something at least 10 times lower but I can not really put a figure on it. It seems to fluctuate ?
But for TCP all 3 measurements are more or less in line.
Nevertheless, very handy tool regardless to do some quick tests (as in showing the difference between powerline connection and real CAT6 cable :lol: )
