General • Re: Public-Mikrotik-Bandwidth-Test-Server(s)

Today ( 3/21/2024 ) I performed the following on my public-access Mikrotik btest server I host.

IPv4: 23.162.144.120
IPv6: 2605:6340:0:1b::4
btest username: MikrotikBtestServer
btest password: MikrotikBtestServer



- ROS upgrade/update
From: 7.13.5
To: 7.14.1

- I also changed the btest username and passoword
From: MikrotikBtest
To: MikrotikBtestServer

- I also moved this Mikrotik CHR ROS btest server to a different hypervisor
From: VmWare ESXi
To: Proxmox

- During the migration from VmWare ESXi to Proxmox , I changed the Ethernet interfaces
From VmWare ESCi : vmxnet3
To Proxmox: VirtIO ( paravirtualized )

Note: I may be having some IPv6 connectivity to this btest server. (( I am rebuilding everything IPv6 at the ISP I manage ))


Please let me know if you experience any issues not that I have made some changes to this server.


Quick notes - limit total testing time to less than 10 minutes.
You must wait 27 hours until you can btest again.
If you attempt to btest more than 10 minutes , then you go to btest jail for 7+ days until you can btest again
If you attempt to btest without waiting 27 hours , then you go to btest jail for 7+ days until you can btest again.
If you attempt to btest and you are in 7-day btest jail , then you reset 7-day btest jail back to 7+ days.
No automatic btest scripts on a timed schedule are permitted.
All btest must be manually performed by a human.
Repeated login failures using the old btest/btest user/password may auto place your IP address in a 7-Day btest jail.

Note: Please read all of my conditions prior to using my btest server.

North Idaho Tom Jones

Statistics: Posted by TomjNorthIdaho — Thu Mar 21, 2024 6:58 pm

---