search

tohojo / flent

The FLExible Network Tester.
https://flent.org
Other
430 stars 77 forks source link

Plot 'ping' failed: Error loading plotter #193

Closed loko-it closed 4 years ago

loko-it commented 4 years ago

I'am using flent 1.3.2 on Ubuntu 18 and it works perfect except for the voip test. It will give this error:

ERROR: Plot 'ping' failed: Error loading plotter: Unable to find plot configuration 'ping'. Falling back to default plot 'voip_delay'.

Anybody knows how to fix this?

tohojo commented 4 years ago

What were you trying to do when you got this error?

loko-it commented 4 years ago

First of all thank you for responding.

I use the GUI and select the VOIP, one way stream test to this server flent-london.bufferbloat.net It will give the error but still show a graph only it seems the off.

The voip delay is giving over 1000ms but normal ping is 15ms. This could also be the server i am using for this test so i also made a capture using wireshark while running the test. Had a look at the delta between packets and non of them suggest a 1700ms latency so it seems this is not correct.

As the error says: Falling back to default plot 'voip_delay'. it seems to be related to the voip delay plot.

In the end i like to test voip and then voip with rrul to see the difference under load and the fact there is a MOS score is also interesting.

Wireshark delta time voip test flent afbeelding

And voip delay afbeelding

tohojo commented 4 years ago

loko-it notifications@github.com writes:

First of all thank you for responding.

I use the GUI and select the VOIP, one way stream test to this server flent-london.bufferbloat.net It will give the error but still show a graph only it seems the off. The voip delay is giving over 200ms but normal ping is 15ms. But it could also be the server i am using for this test.

In the end i like to test voip and then voip with rrul to see the difference under load and the fact there is a MOS score is also interesting.

Hmm, could you please share the data file produced by your test run? Can't immediately reproduce this when I'm running a test myself...