Manual:Tools/Speed Test
The Speed Test is an easy test tool for measuring ping, jitter, TCP and UDP throughput from one MikroTik device, to another.
«speed-test» command is based on Ping Tool and Bandwidth Test. In order to use this command — Bandwidth test server needs to be accessible.
General interface properties
Sub-menu: /tool speed-test
| address (IP address; Default: «») | IP address of host |
| connection-count (integer; Default: 20) | If device has more than 20 cores — core count will be used |
| password (string; Default: ) | Password for the remote device |
| test-duration (integer; Default: 10) | Duration for each test (By default: 5 tests * 10 sec duration + 1sec pause between each test = 55sec) |
| user (string; Default: admin) | Remote device username |
Usage example
Bandwidth and speed tests should be conducted through the devices, not on them to ensure real life simulation and not to overload the CPU on the devices under testing,(DUT) due to traffic generating process.
To run a simple test from device A (192.168.88.1) to device B (192.168.88.2):
[admin@MikroTik]] > /tool speed-test address=192.168.88.1 status: done time-remaining: 0s ping-min-avg-max: 541us / 609us / 3.35ms jitter-min-avg-max: 0s / 76us / 2.76ms loss: 0% (0/100) tcp-download: 921Mbps local-cpu-load:30% tcp-upload: 920Mbps local-cpu-load:30% remote-cpu-load:25% udp-download: 917Mbps local-cpu-load:6% remote-cpu-load:21% udp-upload: 916Mbps local-cpu-load:20% remote-cpu-load:6%
If any of device CPU utilization during test reaches 100% warning message will appear:
[admin@MikroTik]] > /tool speed-test address=192.168.88.1 ;;; results can be limited by cpu, note that traffic generation/termination performance might not be representative of forwarding performance status: done time-remaining: 0s ping-min-avg-max: 541us / 609us / 3.35ms jitter-min-avg-max: 0s / 76us / 2.76ms loss: 0% (0/100) tcp-download: 721Mbps local-cpu-load:78% tcp-upload: 820Mbps local-cpu-load:100% remote-cpu-load:84% udp-download: 906Mbps local-cpu-load:10% remote-cpu-load:54% udp-upload: 895Mbps local-cpu-load:55% remote-cpu-load:12%
«test-duration» parameter allows changing duration of all of the 5 tests:
- ) Ping test with 50ms delay
- ) TCP recieve
- ) TCP send
- ) UDP recieve
- ) UDP send
Introduction
The Speed Test is an easy test tool for measuring ping, jitter, TCP and UDP throughput from one MikroTik device, to another. The «speed-test» command is based on the Ping Tool and Bandwidth Test. In order to use this command — Bandwidth test server needs to be accessible.
General interface properties
The speed-test is based on five configurable properties:
- address — IP address of host;
- connection-count — If a device has more than 20 cores — core count will be used (default is 20);
- password — Password for the remote device;
- test-duration — Duration for each test (By default: 5 tests * 10 sec duration + 1sec pause between each test = 55sec);
- user — Remote device username;
Configuration Example
Bandwidth and speed tests should be conducted through the devices, not on them to ensure real-life simulation and not to overload the CPU on the devices under testing,(DUT) due to the traffic generating process.
To run a simple test from device A (192.168.88.1) to device B (192.168.88.2):
[admin@MikroTik] > /tool/speed-test address=192.168.88.1 status: done time-remaining: 0s ping-min-avg-max: 541us / 609us / 3.35ms jitter-min-avg-max: 0s / 76us / 2.76ms loss: 0% (0/100) tcp-download: 921Mbps local-cpu-load:30% tcp-upload: 920Mbps local-cpu-load:30% remote-cpu-load:25% udp-download: 917Mbps local-cpu-load:6% remote-cpu-load:21% udp-upload: 916Mbps local-cpu-load:20% remote-cpu-load:6%
If any of device CPU utilization during test reaches 100% warning message will appear:
[admin@MikroTik]] > /tool/speed-test address=192.168.88.1 ;;; results can be limited by cpu, note that traffic generation/termination performance might not be representative of forwarding performance status: done time-remaining: 0s ping-min-avg-max: 541us / 609us / 3.35ms jitter-min-avg-max: 0s / 76us / 2.76ms loss: 0% (0/100) tcp-download: 721Mbps local-cpu-load:78% tcp-upload: 820Mbps local-cpu-load:100% remote-cpu-load:84% udp-download: 906Mbps local-cpu-load:10% remote-cpu-load:54% udp-upload: 895Mbps local-cpu-load:55% remote-cpu-load:12%
«test-duration» parameter allows changing the duration of all of the 5 tests:
- ) Ping test with 50ms delay
- ) TCP receive
- ) TCP send
- ) UDP receive
- ) UDP send
Проверка пропускной способности между MikroTik и PC
И так, для того чтобы нам померить Пропускную способность между нашим MikroTik routerboard, нужно скачать утилиту с оф.сайта производителя ВОТ ТУТ, файл называется BTest — Bandwidth test tool for Windows . Ставим её на наш ПК между которым нужно измерить скорость соединения.
Запускаем утилиту, нажимаем на Settings.
Cтавим галочки как на скриншете.
После настройки программы на ПК, заходим в наш MikroTik через WinBox .
Производим настройку BTest Server , находится в директории Tools/BTest Server , отмечаем все как на скриншете.
Далее переходим в директорию Tools/ Bandwidth Test . В окне Test To вписываем ip нашего ПК, в Direction выбираем как именно будет происходить наш тест ( Both,send или receive ). И нажимаем Start .
Таким образом можно измерить пропускную способность между Вашим роутером и ПК как по Wi-Fi, так и по LAN,
adinata-id / bwtest.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
| IPv4: 23.162.144.120 |
| IPv6: 2605:6340:0:1b::4 |
| btest username: btest |
| btest password: btest |
| IP: 87.121.0.45 |
| U: neterra |
| P: neterra |
The above details may be from this source doesn’t work now!
Do you know any other working alternativeS?
The above details may be from this source doesn’t work now! Do you know any other working alternativeS?
IPv4: 23.162.144.120
IPv6: 2605:6340:0:1b::4
btest username: MikrotikBtest
btest password: MikrotikBtest
Useless for other locations. Nobody would be interested to test Idaho from somewhere in France etc.
The above details may be from this source doesn’t work now! Do you know any other working alternativeS?
IPv4: 23.162.144.120 IPv6: 2605:6340:0:1b::4 btest username: MikrotikBtest btest password: MikrotikBtest
Footer
You can’t perform that action at this time.