While this might not generally be a bug, it allows for misuse and also brings up a feature request for proper management and isolation (designation) of net interfaces on toolkit instances.
The problem is that now, if I want to dedicate an interface for latency measurements, I still have to open the BWCTL port. Especially on multi-homed systems where both performance measurements are enabled this leads to the iperf tool available for initiation of tests, even if this is undesirable.
Please make sure with the new design that with BWCTL configuration management to be possible to define a list of allowed measurement tools by network interface.
Hi guys,
While this might not generally be a bug, it allows for misuse and also brings up a feature request for proper management and isolation (designation) of net interfaces on toolkit instances.The problem is that now, if I want to dedicate an interface for latency measurements, I still have to open the BWCTL port. Especially on multi-homed systems where both performance measurements are enabled this leads to the iperf tool available for initiation of tests, even if this is undesirable.Please make sure with the new design that with BWCTL configuration management to be possible to define a list of allowed measurement tools by network interface.
Best regards, Ivan