Hi George
I have been on this list for a long time, but I don't normally respond.With that said, you should keep in mind that when you are using a VM / there is a software IP stack that is touching and playing with your packets.I would consider if it is easy to try the following to give yourself a more controlled test environment.1. run a USB OS without a VM on raw metal to remove the extra network routing stacks2. directly cable into your router to eliminate any potential "802.11" interference from other devices and neighbors3. see if you get the same/similar results4. For optimal test results - PowerCycle your router to be sure that it has freshly reset it's memory -5. Do a traceroute to see if your connection is experiencing any interference / packetloss in the route between yourself and the remote server.George -ps: If you would like to google hangout or zoom.us to check the configuration / I could spend a few minutes with you.On Thu, Jan 17, 2019 at 11:25 PM Azin Neishaboori <azin.neishaboori@gmail.com> wrote:Dear allI have some contradictory results on my WiFi link. I run flent's rrul test using several bufferbloat mitigation algorithms, and see that, compared to FQ_codel, TCP BBR, etc., a simple prioritized ACK works the best. Why is that I have no idea. I also am not clear as to why using BBR on the client end increases the download throughput, but not upload (still doing worse than prioritized ACK on cubic in download anyway). Attached please see the plot.What am I missing?My setup is pretty simple. I am on WiFi on my PC, and run flent on an Ubuntu VM on a virtual machine, and connect to netperf.bufferbloat.net. All configurations are done on my VM end of course.Any help/hint would be appreciated.Thanks a lotBest
Azin_______________________________________________
Bloat-devel mailing list
Bloat-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat-devel
--P THINK BEFORE PRINTING: is it really necessary?
This e-mail and its attachments are confidential and solely for the
intended addressee(s). Do not share or use them without approval. If received in error, contact the sender
and delete them.