I thought about adding IP tracking. One reason I have not is that I am not that good on the Mikrotik when it comes to firewall rules needed to track and log IPs during a bandwidth test.
However, I do know how to use Cisco access-lists with permits that can log IPs through my core 10-gig Cisco router to get from the Internet to/from my Mikrotik Bandwidth tester.
Some good news. I kicked up the peak throughput testing to now support up to 1.2 GIG bandwidth testing.
With the original system, I did not see any abusers. Everybody was good.
Please wait at least 1 minute between tests. My simple queue needs this time for the average traffic to drop so that it can again peak back up to 1.2 gig for another test.
Below is a CLI method to perform the test (if you are a command prompt type of person):
bandwidth-test 207.32.195.2 user=btest password=btest protocol=udp duration=30 direction=receive
bandwidth-test 207.32.195.2 user=btest password=btest protocol=udp duration=30 direction=transmit
If you use the CLI method shown above; then look at your tx-or-rx “10-second-average:” when the test is completed.
FYI information:
At this time, my Internet connection should have the ability to support this load at all times
My Internet connection comes out at Seattle Washington U.S.A. although I am actually located in North Idaho U.S.A.
If you do not get the speeds you think you should be getting, then wait about 5 minutes. Somebody else could be testing which could effect your testing.
I am not sure how well bandwidth tests will perform near or above 1-gig (due to the nature of the Internet connected routers and switches and physical transports)
Please post your positive or negative results or thoughts about this tester.
Please no abusers. The function of this tester is only intended to good and proper use
First rule will reject any new connection from any address in the “btest” address list. The second rule will generate that list as connections come in. I used 1 day in the example.
Again, as long as folks aren’t abusing it, great… but this may help if things become a problem.
Another way to do authentication, would be radius, which could use an SQL back-end, easily managed by a web front end where users could register, be verified, then granted access. I won’t pretend to have the patience for building something like this, but I’m sure if you were to ask the community, someone would be more than happy to step up and help you out.
I would like others to consider configuring their own public Mikrotik Bandwidth Tester systems also and placing them on-line for other Mikrotik network admins to be able to btest to/from with.
I have had mine on-line for almost two months now and the last week has been opened up to be able to btest up to 1.2 gig (note a continuous btest will drop down to 100 meg). So far, I have not seen any effects on my business ISP network.
If you have the bandwidth to spare, I would like to suggest you consider also making a btest server. From my point of view, I have the bandwidth and I have only heard positive comments and so-far I have not seen any abuse - thank you.
Also - If anybody has a desire to perform any really high-throughput bandwidth testing, you are welcome to drop me a message and we can set up a time where I can crank up my btest server to be able to sustain up to 3-gig (Yes I have that kind of spare bandwidth).
Thank you very much for providing this! My results are below.
Are you planning to keep this server running permanently (for the foreseeable future, or until you run out of spare bandwidth)? Or is this a temporary project only?
It would be awesome if it’s long-term, but either way, thank you!
BTest.JPG
novical - are you measuring what you are supposed to be getting ?
If there are no abusers, I plan on keeping it on-line and available (aka long-term).
I plan on keeping it available as long as I have the extra un-used bandwidth to support btest connections.
At this time, do not see having to reduce the speed to less than 1 gig.
Yes, getting very close to what I’m supposed to. 25 up / 25 down, but there is lots of other stuff running so I estimated it would be closer to 15-20Mbps.
That would be great. I would like to set up a test server too at some point, but it may be a while before I can do that so in the meantime it’s really nice having this. Are you aware of any other servers or yours is the only one as far as you know?
Great - I must admit that I did now know how well 1.2 gig would traverse through the Internet.
I am thinking about kicking it up to 2.4 gig then later 3.6 gig - might do the first later this week.
It would be nice if the btest server had a setting for how long a test can run to/from a client. If I had this kind of control of the server, then I would remove all limits and let it run up to 10-gig for 10 seconds or longer.
Now you may test your Internet download speeds up to 3.5 Gig !!!
btest-squeue.jpg
Good news for you
I opened up my best server to be much faster !!!
It now supports 3.5 Gig bandwidth tests to you (your download speed)
It now supports 2.2 Gig bandwidth tests from you (your upload speed)
LOL - that actually made a needle like spike in my Cacti bandwidth graphs
If you don’t mind, I have some questions for you:
What do you get when you btest to your local loopback IP address of 127.0.0.1 ?
On my ESXi VMware hosted 32-bit x86 ROS, I get around 17 gig.
What do you get when you btest to the IP address of your WAN on your Mikrotik?
I get 9 gig.
I have never played with a CCR device, so I really have no idea just how well they perform under heavy load and testing. I sure would like to replace my 32-bit x86 ROS btest server with a 64-bit ROS btest server. Anybody willing to donate one (or a physical miktorik that can handle a public btest server up to 10-gig ???
In both cases I get around 850Mb/s…and a sigle cpu core at 100%.
And Bandwidth Test uses only a single CPU core…so the tilera cpu isn’t the best option on which to run the btest server…
FYI - Although I am running my ROS in a VMware ESXi environment, I am running two Intel Xeon 10-core E5-2690 3-GHz CPUs (20-meg CPU cache) (Hyper-Threading disabled), of which I have allocated 2 CPUs to the virtual ROS.
I was not aware that btest only used a single core. I might drop it down to a single CPU and see if it makes any difference.
FYI - the Mikrotik x86 ROS must of crashed a couple of days ago - I just noticed it was not talking so I re-started it.
207.32.195.2
btest user: btest
btest password: btest
This time I put a network monitor on it to alert me if it happens to go down.
I suspect I may of crashed it when I was performing some bandwidths from a 64-bit ROS and had all rate-limiting disabled.