>What exactly is your problem with getting Flent to run today?
It's nothing specific to Flent. I install software sporadically. Whenever I do,
I face the kinds of problems described in the article (old 2.7 version of
Python, some silly version of Qt, etc.) I don't have a formal system for
I read an intriguing article - [Run more stuff in
Docker](https://jonathan.bergknoff.com/journal/run-more-stuff-in-docker/). It
showed a solution to a big frustration: getting the right version of Flent,
Python, netperf, and all the other libraries onto my computer without screwing
up other
Closed #202.
--
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/202#event-3143077429___
Flent-users mailing list
Flent-users@flent.org
**Update:** Telling OpenWrt not to use the ISP's DNS servers, but to use
something reliable solves the problem.
Moral of the story: Friends don't let friends use their ISP's resolvers...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
It's actually more frustrating than that... My ISP (Consolidated
Communications, a DSL provider) has me using their resolver at 64.222.212.243
and 64.222.165.243
`dig flent-fremont.bufferbloat.net @ 8.8.8.8` (or @1.1.1.1) return a
perfectly reasonable address.
Using my ISP's
Using Flent 1.9.9-git-34ed663 on macOS 10.15.3, I am having trouble with the
"-6" option. My default test host is `flent-fremont.bufferbloat.net`
Using that hostname with the -6 option causes both fping and flent to fail with
unknown host.
What's a good IPv6 host to use with Flent? Thanks.
Closed #194.
--
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/194#event-2999729331___
Flent-users mailing list
Flent-users@flent.org
My coffee-shop-speed-test.sh started to give an error message: `1.1.1.1:
nodename nor servname provided, or not known` This appears to occur because
`fping -6` attempts to ping an IPv4 address, 1.1.1.1. (see full output below).
This doesn't happen when I set
> Well, by "switch" I just meant "new command line option". The obvious
form of that would be, as you say, just the ability to set the netperf
xfer size directly...
Yes. And let's remember why we're having this discussion - I asked why the
charts for very slow links had so little granularity.
Sorry for the delay in responding... The higher granularity makes much better
plots (see below). Using `-m 2048,2048` I don't see a whole lot of load on my
Mac 2.5 GHz Intel Core i7 at 7mbps/768kbps. Thanks.
Closed #184.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/184#event-2647685942___
Flent-users mailing list
Flent-users@flent.org
Better. Thanks!
```
Started Flent 1.9.9-git-fa47b0f using Python 3.7.3.
Starting rrul test. Expected run time: 70 seconds.
Data file written to
./rrul-2019-09-19T123807.165015.Rich_Test_-_Flent_1_9_9-git-fa47b0f.flent.gz
Summary of rrul test run from 2019-09-19 16:38:07.165015
Title:
> Basically, the problem is the way netperf determines its data output
> intervals in demo mode:
Ahah! That was the explanation, but I wasn't (yet) smart enough to comprehend
it. [To further test out my understanding... If netperf were to use a smaller
"data output interval" when it's
*answering the questions in the opposite order*
> Any suggestions as for where to put this so it's easy to find?
The bufferbloat.net site has an [RRUL Chart
Explanation](https://www.bufferbloat.net/projects/bloat/wiki/RRUL_Chart_Explanation/)
page. I have always felt the Flent site could
Using Flent 1.9.9-git-67ac0f7 on macOS 10.12.6:
There are two visual problems with the Flent GUI on my Mac:
1. By default, Flent opens up using a large font. Choosing View / Refresh Plot
changes the plot to use a smaller font, and the plots fill more of the space
provided.
2. Moving the mouse
Here's an RRUL plot from my 7mbps/768kbps DSL circuit. The download has good
granularity, while the upload plot seems only to have a half-dozen data points.
This makes it seem faulty, or somehow different/disconnected from the other two
plots.
I think I once saw a justification for the
Looks good. Displayed ping averages are much more reasonable.
Does the plotted Ping Average include/average in the extra host (1.1.1.1)? Is
this new? Thanks.
```
Started Flent 1.9.9-git-83a0308 using Python 3.7.3.
Starting rrul test. Expected run time: 70 seconds.
Data file written to
OK New run, this time with result and log files... (Charts are substantially
the same as above.) Thanks!
[rrul_be-2019-09-15T125209.510692.Richs-MBP-10337_lan.log](https://github.com/tohojo/flent/files/3614011/rrul_be-2019-09-15T125209.510692.Richs-MBP-10337_lan.log)
Using Flent 1.9.9-git-2a08dd9:
I have been looking hard at Flent results for Dave's tests for coffee shops
[(my latest script.)](https://github.com/richb-hanover/coffee-shop-bloat-test)
I have a few fussy observations about the Flent output for the tests:
* I like how the rrul and rrul_be
Confirmed. I like `N/A` better than my suggestion. Thanks.
```
bash-3.2$ flent -x -L -H flent-fremont.bufferbloat.net -t
"flent-fremont.bufferbloat.net" --te=upload_streams=4 --te=ping_hosts=1.1.1.1
tcp_nup
Started Flent 1.9.9-git-2a08dd9 using Python 3.7.3.
Starting tcp_nup test. Expected run
I do see your point. I'm casting about to find a good way to show this,
especially when pulling results from separate data files, where the file names
won't be a particularly good way to indicate a difference. Alternatives:
* The legend at the bottom "Local/Remote:
Sorry to re-open, but the new version (Flent 1.9.9-git-ff46520) seems to fix
the upload values for the Average - the individual streams sum to the displayed
sum.
But the Median values still don't look right. Here are two runs of the same
command:
```
bash-3.2$ flent -x -L -H
I don't pretend to understand the metadata - there is a lot stuff in the JSON
file - but I don't think including the information in the filename would be
necessary.
I don't foresee a transition problem here. Flent can continue to default to
using the -H host for its latency measurements. The
Closed #178.
--
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/178#event-2628972439___
Flent-users mailing list
Flent-users@flent.org
I am going to close this for now. Two reasons:
1. The primary reason for this report was that I misunderstood how Flent
measures latency for its default plot. Currently, that plot shows latency to
the -H host. As noted in
https://github.com/tohojo/flent/issues/181#issuecomment-530500478, there
Update: dtaht (in
https://github.com/tohojo/flent/issues/178#issuecomment-528885331) said of the
ping times, "I have seen this statistic be wildly wrong in the summary but
correct in the graph."
Related?
--
You are receiving this because you are subscribed to this thread.
Reply to this email
Update: I'm trying to get repeatable test showing a difference of latency
between the Flent ping_host values and a separate/concurrent fping run. (I saw
it two days ago, but can't reproduce now... This is roundabout way to say that,
for the moment, the Flent ping_host and separate fping runs
Actually, I want the ability to plot the "best"`ping_host` (that is, lowest
latency host), since that's going to display the biggest variance. A few
milliseconds of additional bloat added to the 90msec from my house to Fremont
is easy to ignore. Tacking a few milliseconds onto 16msec from
> Doing this dynamically in the GUI would be a nice feature, though, but
not quite trivial unfortunately...
Yes. I once worked on the plotting portion of a program, and nothing is
trivial.
So I come back to my request to select the ping_host value in lieu of latency
to the -H host in the
Update to the update: The `qt.qpa.cocoa.window: Window position outside any
known screen, using primary screen` message is *not* present when I re-launched
the Flent GUI after combining the chart and the plot selector windows.
--
You are receiving this because you are subscribed to this
PS Why am I perseverating about this now? I have taken Dave's script and
packaged it for ease of use. See [Coffee Shop Bloat
Script](https://github.com/richb-hanover/coffee-shop-bloat-test)
I can conceal a lot of the options into the script if I know what they are.
Thanks again.
--
You are
> > 2. Why is there a discrepency between the
`--test-parameter=ping_hosts=...` reading (showing 30-38 msec in my
tests) and a separate, concurrent fping test (see original post, where
it was running 20-22 msec)?
> Good question. IPv4 vs IPv6 maybe?
I don't think so. Here's fping for both
> > 1. Could flent charts use the `--test-parameter=ping_hosts=...` instead of
> > values from the -H host?
> Well, it should probably show both by default. For now, there's a separate
> plot type you can use to see the extra flows (-p ping_extra).
I don't see how to use the `-p` option. When
Hmmm... The `--test-parameter=ping_hosts=gstatic.com` information appears in
the command-line summary but not in the charts. Is this correct?
If so, the charts display significantly different latency depending on which -H
host gets used. The Terminal display (bottom) shows fairly consistent
Ahah! I see the difference. I was testing against `gstatic.com` with Terminal;
Flent was testing against `flent-fremont.bufferbloat.net`
This seems a pretty big disparity between test results. Is there an option to
tell Flent to ping a more local host? Thanks.
```
bash-3.2$ fping -c 1000
Here's the log file: https://pastebin.com/aBXCgjD1
NB I'll be away for the weekend, so won't follow up for a while. Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hmmm, not this time... What else could I check?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Using Flent 1.3.0 with fping 4.2 on macOS 10.2.6:
I see high ping times (>100 msec in the following report) despite the fact that
actual ping times (measured by fping during the flent test) are 20-30 msec, and
none higher that 47 msec. (I am on 7mbps/768kbps DSL, so the 6.95mbps seems
Closed #177.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/177#event-2610513157___
Flent-users mailing list
Flent-users@flent.org
Good advice. Done.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/177#issuecomment-528351721___
Flent-users mailing list
Flent-users@flent.org
Spurred on by Dave's [Coffee Shop Bloat
Test](https://lists.bufferbloat.net/pipermail/bloat/2019-September/009336.html)
script, I decided to try it on my Mac (10.12.6) with Flent 1.3.0. This command
seemed to work fine:
`flent -x -H flent-fremont.bufferbloat.net -t Rich_Test
41 matches
Mail list logo
