lealog <notifications@github.com> writes:

>> Well, it would require an underlying test tool that could produce
>> this sort of traffic. I wouldn't be opposed to adding support for
>> such a tool if it materialised, but I am not aware of any either.
>
> I would say that we can do this using iperf3. Iperf3 can specify the
> DS and US bandwidth using the option "-b". Does this make sense for
> you?

The trouble with the iperf UDP tests it that they just send off packets
and don't provide any feedback on how much makes it through. You may or
may not get a result at the end from the other side at the end of the
test, but that can also easily get lost. So while it can generate a base
load, this kind of test is not really suitable for graphing data *about*
those flows during the test.

>> Some orchestration is possible already by a combination of tests with
>> multiple remote endpoints, and remote test runners. It requires a bit
>> of fiddling with the CLI and/or batch files to set up, but it's
>> doable. Extending support for running tests through the GUI would be
>> neat, but unless someone dedicates resources to this I don't think
>> it's likely to happen anytime soon, unfortunately...
>
> I would say that supporting this on GUI is a "nice to have" :)
> Regarding the CLI, how can we do this? Can you share your idea?

Well, there are two options: Reverse the setup and run the Flent test
from the "other side" with different flows going to each of your two
test hosts. Or run Flent on one of the two "local" hosts, and use the
--remote-host option to execute some of the test runners on the other
host (preferably using a dedicated control connection between the two).
I've been using the former setup for WiFi tests, but which one is
easiest to do really depends on the details of your test network...


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/217#issuecomment-747477879