To add, iperf3 should be fairly easy to add - My understanding is that it's being ported to some CPE in the states. Along the same lines, there is a binary that should be compatible for latency / Jitter called OWAMP, integration of that would be great as well assuming the clock is accurate enough to support it. I've done some work in making it work in VMs inside of other network hardware capable of running a virtualized perfSonar system in-skin. Having the binaries directly in the RouterOS would allow for a very robust meshing of tests back to a central perfSonar MU. I am in favor of having these things, it brings significant value.Ok, Mikrotik, can we have any rough statement to this? At least if iperf was denied, or if we can expect it in v7 since its beginning or in v6 yet since 6.39.2?
That would be a killer feature to have built into ROS!Having the binaries directly in the RouterOS would allow for a very robust meshing of tests back to a central perfSonar MU. I am in favor of having these things, it brings significant value.
Can I run 'iperf -s' on a computer, use Mikrotik Traffic generator to send traffic to this computer and read meaningful measures on either device (Mikrotik host or computer) ?Hello,
we already have a bandwidth testing tool which is fully integrated into RouterOS and works properly with the RouterBOARD ethernet drivers. The tool is called 'Traffic generator' (available both in WinBox and from the command line interface). Please take a look. We hope you like it - https://wiki.mikrotik.com/wiki/Manual:T ... _Generator
Nah, let's make it useful and comfortable. You've already lost the fight for pure router anyway. Existing BTest, CAPsMAN, Dude, GPS, Graphing, KVM or MetaROUTER, NTP server, User manager, Web proxy, ... and if you're real purist, you'll probably find other stuff that proper router shouldn't have.don't put development effort in tools that do not belong on a router !