General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: moeller0 <moeller0@gmx.de>
To: Brandon Applegate <brandon@burn.net>
Cc: Alan Jenkins <alan.christopher.jenkins@gmail.com>,
	Bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Getting started with sqm-scripts - latency good, bandwidth decimated
Date: Wed, 20 Jan 2016 16:10:05 +0100	[thread overview]
Message-ID: <30331643-7B24-4411-91D1-C4862E05E8C4@gmx.de> (raw)
In-Reply-To: <7C9E895A-B3CC-44D9-9E5B-D99BDCDA0D41@burn.net>

Hi Brandon,

> On Jan 20, 2016, at 15:51 , Brandon Applegate <brandon@burn.net> wrote:
> 
>> 
>> On Jan 20, 2016, at 7:06 AM, Alan Jenkins <alan.christopher.jenkins@gmail.com> wrote:
>> 
>> 
>> No offense to your work on sqm-scripts.
>> 
>> 
>> 1) It's just in case the problem is *outside* of sqm-scripts, it could be useful to try the minimum commands necessary to demonstrate the problem.  Maybe it's unfair but I assumed running on a PC is also a less tested case, as well as the "firewall on a stick" part.
>> 
>> Equally, since AFAICT Brandon hasn't had a working AQM setup on this box before.  It could be useful if the Gentoo script works, to prove that AQM + fq_codel can work correctly on Brandon's box.
>> 
>> If the Gentoo script _wasn't_ working, that's when I'd suggest tearing it down e.g. to eliminate fq_codel as an issue.  Rather than specify fifo explicitly, just don't run the fq_codel command (assuming that actually does something sensible, which can be checked using `tc qdisc`).
>> 
>> 
>> 2) More specifically, you didn't mention trying "simplest.qos". This would i) simplify the setup we're trying to debug, and ii) it might show if there's a bug with the more complex bandwidth calculations / assignments in "simple.qos".
>> 
>> 
>> And again - I suggest starting by checking `tc class show dev eth0.666`, because it's not a 100% obvious command, and we don't want to miss if there are bad rates there :).
>> 
>> 
>> Alan
> 
> Wow, thanks for all the ideas and feedback.  I did indeed find the Gentoo wiki script and gave it a shot - basically the same behavior as sqm-scripts.
> 
> I’m really thinking my on-a-stick topology is tying things in knots as my traffic is on the same interface twice in inverse directions.  I have another NIC in the box used for some back end NFS stuff - I can steal him temporarily to rejigger my interfaces.  My goal is to get eth0.666 to just be eth0 (public wan, no dot1q).  I’ll post my results from this - and barring any great success there - will loop back to this thread and try what folks have mentioned.

	Please, before you change the set up, run the few commands Alan (and I asked for) so we can get a rough idea what was happening. This smells like a bug in sqm-scripts and I would love to either confirm and fix it or get sqm-scripts acquitted ;)


> 
> We are snowed in today so the kids are home from school - I’m sure I’ll get plenty of feedback from them - ‘dad the internet is down’.  :)

So I would fully understand if any testing will have to wait until the weather permits outdoor activity again ;)

Best Regards
	Sebastian

  reply	other threads:[~2016-01-20 15:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 23:33 Brandon Applegate
2016-01-20  0:09 ` Jonathan Morton
2016-01-20  0:14   ` Brandon Applegate
2016-01-20  2:36     ` Jonathan Morton
2016-01-20 17:32   ` Simon Barber
2016-01-20 10:12 ` Alan Jenkins
2016-01-20 10:15   ` Alan Jenkins
2016-01-20 11:47     ` moeller0
2016-01-20 11:43   ` moeller0
2016-01-20 12:06     ` Alan Jenkins
2016-01-20 12:25       ` moeller0
2016-01-20 14:51       ` Brandon Applegate
2016-01-20 15:10         ` moeller0 [this message]
2016-01-20 15:15   ` Brandon Applegate
2016-01-20 16:05     ` Sebastian Moeller
2016-01-20 16:10       ` Brandon Applegate
2016-01-20 16:32         ` Alan Jenkins
2016-01-20 16:34         ` Brandon Applegate
2016-01-20 16:47           ` Etienne Champetier
2016-01-20 16:54             ` Brandon Applegate
2016-01-20 17:09               ` Etienne Champetier
2016-01-20 17:42                 ` moeller0
2016-01-20 17:50                   ` Etienne Champetier
2016-01-20 17:40         ` moeller0
2016-01-20 11:30 ` moeller0
2016-01-20 12:37   ` Rich Brown
2016-01-20 14:42     ` Brandon Applegate
2016-01-20 15:30   ` Brandon Applegate
2016-01-20 16:09     ` Sebastian Moeller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30331643-7B24-4411-91D1-C4862E05E8C4@gmx.de \
    --to=moeller0@gmx.de \
    --cc=Bloat@lists.bufferbloat.net \
    --cc=alan.christopher.jenkins@gmail.com \
    --cc=brandon@burn.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox