Btest mikrotik не работает

Resolve Mikrotik bandwidth test connection error.

Mikrotik bandwidth test connection error message that reads “can’t connect to host” can be frustrating when trying to determine the throughput on a wireless link. Apart from not being able to test from the affected device, further checks will reveal that the LAN interface is under-performing.

At the time of writing this article, there is no material anywhere else on the causes and solution to this problem. However, as frustrating as the Mikrotik bandwidth test connection error problem can be, the solution is quite simple and easy to implement. First, let’s look at the cause of this problem.

Why Mikrotik bandwidth test connection error?

There are two main types of Mikrotik bandwidth test error messages that a user can receive while attempting to perform a bandwidth test. One is authentication error and the other is connection error. Authentication errors are caused by entering the wrong server login credentials and can simply be corrected by typing in the correct username and password of the device you are testing to. The latter is caused by interface duplex mismatch that affects the overall performance of your link and is what this article is about. Read on.

It is very easy to find cheap 10/100 switches on so many networks today. This is because most people do not want to spend money on network infrastructures let alone on a switch; a plug-and-play device. The Mikrotik bandwidth test connection error is caused when a Mikrotik radio with 10/100/1000 ethernet port negotiates a 10mbps connection on a switchport. This happens because the interface negotiation on Mikrotik devices is set to auto by default. Once this happens, two major issues will arrise. Firstly, performing bandwidth test on the affected device to any other Mikrotik device will display an error message saying “can’t connect to host”. However, test from other devices to the wireless interface of the affected Mikrotik device will work. Secondly, the speed on the affected LAN port will not go beyond 10mbps.

Solution to Mikrotik bandwidth test connection error

To resolve Mikrotik bandwidth test connection error on a Mikrotik device, simply go to interfaces and double-click on the LAN port, click on ethernet and uncheck the box for 10mbps on both tx and rx. If you have a gigabit switch, you can uncheck the box for 100M to force a gigabit interface negotiation. See image below.

After performing the task above, the Mikrotik device LAN port will renegotiate interface speed with the LAN switch and connection will be re-established. Bandwidth test from the device to other devices will work effectively and speed test from the LAN will no longer be limited to 10Mbps.

If you enjoyed this tutorial, please subscribe to this blog to receive my posts via email. Also subscibe to my YouTube channel, like my Facebook page and follow me on Twitter

Источник

РеКС — друг в мире компьютеров

Для оценки эффективности работы сетевого оборудования путем измерения фактической полосы трафика проходящего через сетевые коммутаторы и маршрутизаторы компания Mikrotik предлагает использовать утилиту BTest для Windows.

Rick Frey consulting: Btest Server & Bandwidth Test Tools //rickfreyconsulting.com

Введение

Метод тестирования прост. На любых компьютерах в локальной сети или в сетях, между которыми выполняется маршрутизация запускаются утилиты BTest, которые создают между собой соединения с заданными параметрами входящего и исходящего трафика и отображают фактическую полосу.

Утилита BTest не требует установки, ее достаточно запустить на каждом компьютере, который будет участвовать в тестировании.

Настройки

Прежде чем приступить к тестированию сети, утилиту BTest необходимо настроить кнопкой Settings…:

• Server Enabled разрешает утилите открыть порт на прослушивание входящих подключений.
• Authentication Required требует авторизации для входящих подключений, список разрешенных пользователей находится внизу окна настроек.
• Max. Accepted Connectiion ограничивает число подключений.
• Allocate UDP Ports From
• Launch Program On System Startup регистрирует утилиту в качестве системной службы, которая будет запускать автоматические при каждом включении компьютера.

Утилита или служба запущенная с разрешением удаленного подключения открывает на прослушивание порты TCP:2000 и UDP:2000, которые следует разрешить в настройках брандмауэра.

Тестирование

Основное окно BTest позволяет задать параметры соединения с портом утилиты на удаленном компьютере.

• Address — адрес другого компьютера для подключения.
• Protocol — тип протокола соединения TCP или UDP.
• Local Tx Size
• Remote Tx Size
• Direction — направление трафика
  • receive — получение
  • send — передача
  • both — оба направления
• Local Tx Speed — ограничение полосы исходящего трафика
• Remote Tx Speed — ограничение полосы трафика отправляемого с удаленного компьютера.
• User/Password — для авторизации подключения к тем компьютерам, где в настройках BTest определена необходимость аутентификации Authentication Required.
• Random Data

После каждого нажатия кнопки Start утилита BTest устанавливает соединение с удаленным компьютером и генерирует трафик с заданными параметрами. Фактические показатели соединения отображаются в отдельном окне. Утилита позволяет открыть произвольное число соединений с произвольными удаленными компьютерами, на которых тоже запущен утилита, либо работает служба.

2 мысли о “BTest от Mikrotik: Утилита тестирования полосы сетевого трафика”

Классная программа. Всегда ей провожу тест перед тем как войти на свой сайт.

Источник

Btest mikrotik не работает

Thu Feb 14, 2019 3:32 am

Hello mikrotik fans,

I will be bringing up a btest server soon. I have preprared one RB800 and a 1Gbit connection dedicated only for the sake of testing.
It is ready, but I want to limit the usage somehow before I post it public. I have created filter rule for input that puts your IP in ban address list for X period of time.

I can’t figure out how to limit the test sessions per time. You can basically let it run indefinately. Can you tell me how to disconnect every btest connection for example on 5min?

Re: NEW Public Bandwith Test Server

Thu Feb 14, 2019 1:21 pm

You can check out the configuration of TomjNorthIdaho posted here:

Re: NEW Public Bandwith Test Server

Thu Feb 14, 2019 1:33 pm

Re: NEW Public Bandwith Test Server

Thu Feb 14, 2019 6:04 pm

I did check his config and set it up nicely. Everything works except when the timer runs out for «testing» address list it wouldnt drop the traffic server>client only the other way. This issue appears only when testing UDP. With TCP test there is no problem. I worked on this for about 6 hours last night and I couldnt find a solution. Anyone else experenced this iisue?

Should I provide any screenshots?

Re: NEW Public Bandwith Test Server

Thu Feb 14, 2019 6:09 pm

Have you enabled fasttrack? I will probably bypass raw firewall, however doesn’t explain why tcp is working.

Please do no post screenshots, just export config ( /export hide-sensitive ) and paste in code blocks.

Also.. TomjNorthIdaho mentioned more than a terabyte of traffic per month hosting public bandwidth server.
Are you sure your connection can handle such large amount of traffic?

Re: NEW Public Bandwith Test Server

Fri Feb 15, 2019 12:25 pm

I have enabled fasttrack, but it doesn’t count packets so I guess i doesn’t apply for this.

I will post config as soon as I can.

The mikrotik will be in a datacenter for the clients to test their bandwith and also for public use. So yes the network behind it will handle alot

Re: NEW Public Bandwith Test Server

Fri Feb 15, 2019 11:52 pm

Re: NEW Public Bandwith Test Server

Tue Feb 26, 2019 4:01 am

Hello again.
It seems I fixed it and it’s now working as expected. RAW rules needed tweaking. I will post before and after output so you can compare:

Before:
[user@Server] /ip firewall> raw print
Flags: X — disabled, I — invalid, D — dynamic
0 D ;;; special dummy rule to show fasttrack counters
chain=prerouting action=passthrough
1 ;;; testers accepted
chain=prerouting action=accept log=no log-prefix=»» src-address-list=tester
2 ;;; previous testers drop
chain=prerouting action=drop log=no log-prefix=»» src-address-list=previous
3 ;;; add to tester
chain=prerouting action=add-src-to-address-list dst-port=2000-3000 log=no log-prefix=»» protocol=tcp address-list=tester address-list-timeout=15m
4 ;;; add to tester
chain=prerouting action=add-src-to-address-list dst-port=2000-3000 log=no log-prefix=»» protocol=udp address-list=tester address-list-timeout=15m
5 ;;; add to previous
chain=prerouting action=add-src-to-address-list dst-port=2000-3000 log=yes log-prefix=»» protocol=tcp address-list=previous address-list-timeout=1d
6 ;;; add to previous
chain=prerouting action=add-src-to-address-list dst-port=2000-3000 log=yes log-prefix=»» protocol=udp address-list=previous address-list-timeout=1d

After:
[user@Server] /ip firewall> raw print
Flags: X — disabled, I — invalid, D — dynamic
0 D ;;; special dummy rule to show fasttrack counters
chain=prerouting action=passthrough
1 ;;; testers accepted
chain=prerouting action=accept log=no log-prefix=»» src-address-list=tester
2 ;;; testers accepted
chain=output action=accept log=no log-prefix=»» dst-address-list=tester
3 ;;; previous testers drop
chain=output action=drop log=no log-prefix=»» dst-address-list=previous
4 ;;; previous testers drop
chain=prerouting action=drop log=no log-prefix=»» src-address-list=previous
5 ;;; add to tester
chain=prerouting action=add-src-to-address-list dst-port=2000-3000 log=no log-prefix=»» protocol=tcp address-list=tester address-list-timeout=15m
6 ;;; add to tester
chain=prerouting action=add-src-to-address-list dst-port=2000-3000 log=no log-prefix=»» protocol=udp address-list=tester address-list-timeout=15m
7 ;;; add to previous
chain=prerouting action=add-src-to-address-list dst-port=2000-3000 log=no log-prefix=»» protocol=tcp address-list=previous address-list-timeout=1d
8 ;;; add to previous
chain=prerouting action=add-src-to-address-list dst-port=2000-3000 log=no log-prefix=»» protocol=udp address-list=previous address-list-timeout=1d

Источник

Manual:Tools/Bandwidth Test

Applies to RouterOS: v2.9, v3, v4+

Contents

Summary

Sub-menu: /tool
Packages required: system

The Bandwidth Tester can be used to measure the throughput to another MikroTik router (either wired or wireless) and thereby help to discover network «bottlenecks».

The TCP test uses the standard TCP protocol with acknowledgments and follows the TCP algorithm on how many packets to send according to latency, dropped packets, and other features in the TCP algorithm. Please review the TCP protocol for details on its internal speed settings and how to analyze its behavior. Statistics for throughput are calculated using the entire size of the TCP data stream. As acknowledgments are an internal working of TCP, their size and usage of the link are not included in the throughput statistics. Therefore this statistic is not as reliable as the UDP statistic when estimating throughput.

The UDP tester sends 110% or more packets than currently reported as received on the other side of the link. To see the maximum throughput of a link, the packet size should be set for the maximum MTU allowed by the links which is usually 1500 bytes. There is no acknowledgment required by UDP; this implementation means that the closest approximation of the throughput can be seen.

• Up to RouterOS version 6.44beta39 Bandwidth Test used only single CPU core and reached its limits when core was 100% loaded.
• Bandwidth Test uses all available bandwidth (by default) and may impact network usability.

• 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 routers connected in chain: the Bandwidth Server, the router being tested and the Bandwidth Client.

• If you use UDP protocol then Bandwidth Test counts IP header+UDP header+UDP data. In case if you use TCP then Bandwidth Test counts only TCP data (TCP header and IP header are not included).

Bandwidth Test Server

Sub-menu: /tool bandwidth-server

Property	Description
allocate-udp-ports-from (integer 1000..64000; Default: 2000)	Beginning of UDP port range
authenticate (yes | no; Default: yes)	Communicate only with authenticated clients
enabled (yes | no; Default: yes)	Defines whether bandwidth server is enabled or not
max-sessions (integer 1..1000; Default: 100)	Maximal simultaneous test count

Example

To enable bandwidth-test server without client authentication:

Bandwidth Test Client

Command name: /tool bandwidth-test

Property	Description
address (IP address | IPv6 prefix[%interface]; Default: )	IP address of host
direction (both | receive | transmit; Default: receive)	Direction of data flow
duration (time; Default: )	Duration of the test
interval (time: 20ms..5s; Default: 1s)	Delay between reports (in seconds)
local-tx-speed (integer 0..4294967295; Default: )	Transfer test maximum speed (bits per second)
local-udp-tx-size (integer: 28..64000 )	Local transmit packet size in bytes
password (string; Default: «»)	Password for the remote user
protocol (udp | tcp; Default: udp)	Protocol to use
random-data (yes | no; Default: no)	If random-data is set to yes, the payload of the bandwidth test packets will have incompressible random data stream so that links that use data compression will not distort the results (this is CPU intensive and random-data should be set to no for low speed CPUs)
remote-tx-speed (integer 0..4294967295; Default: )	Receive test maximum speed (bits per second)
remote-udp-tx-size (integer: 28..64000 )	Remote transmit packet size in bytes
tcp-connection-count (integer 1..100; Default: 20)	Number of TCP connections to use
user (string; Default: «»)	Remote user

Example

To run 15-second long bandwidth-test to the 10.0.0.32 host sending and receiving 1000-byte UDP packets and using username admin to connect:

Источник