Closed #214.
--
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/214#event-4086781836___
Flent-users mailing list -- flent-users@flent.org
To
Great! Closing this, then :)
--
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/214#issuecomment-741039524___
Flent-users mailing list --
Quoting Toke Høiland-Jørgensen (2020-12-08 17:19:18)
> You could try setting up irtt on both server and client and see if that
> fares better - Flent should automatically pick it up if it's installed
> on the client, and you just need to start it along with netserver on the
> server-side:
>
>
Jonas Smedegaard writes:
> Quoting Toke Høiland-Jørgensen (2020-12-06 13:03:02)
>> Or it may be that the same UDP issue you linked also affects the UDP_RR
>> test; I'll dig around in the netperf source code a bit and see what I
>> can find :)
>
> Thanks - much appreciated!
OK, poked around in
Quoting Toke Høiland-Jørgensen (2020-12-06 13:03:02)
> Or it may be that the same UDP issue you linked also affects the UDP_RR
> test; I'll dig around in the netperf source code a bit and see what I
> can find :)
Thanks - much appreciated!
--
You are receiving this because you are subscribed to
Jonas Smedegaard writes:
> Output graph for an RRUL test is missing the 3 UDP ping series, but
> all other series seem to have gotten through. Perhaps this is no
> issue in flent after all, just my cloud provider blocking UDP ping...
Or it may be that the same UDP issue you linked also affects
Sorry, I was too quick to conclude the exact cause of error messages I saw in
the GUI.
When I saw those errors I cancelled the test, expecting no results at all - but
trying more patiently to let it run its course I now see that output is
generate (so something works) and those error messages
Jonas Smedegaard writes:
> I want to test my internet connection, and wanted to test against a
> virtual machine at Scaleway - which uses 1:1 NAT (seen from the host
> itself is a private 10.x.x.x/23 IPv4 address mapped to a public IPv4
> address) which apparently require setting [an
