From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Brandon Applegate <brandon@burn.net>,
Sebastian Moeller <moeller0@gmx.de>
Cc: Bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Getting started with sqm-scripts - latency good, bandwidth decimated
Date: Wed, 20 Jan 2016 16:32:10 +0000 [thread overview]
Message-ID: <569FB68A.6000100@gmail.com> (raw)
In-Reply-To: <55C85334-20A2-4625-BAD2-71BF536DF19D@burn.net>
On 20/01/16 16:10, Brandon Applegate wrote:
> I’m getting more confused as I go on :)
>
> So I’ve rebooted and the tc classes seem to have come back. Since this is Ubuntu 12.04 - it doesn NOT have systemd. I mention this because I see there is a systemd config in the sqm-scripts package.
>
> I have not added any hooks to run 'sqm start’ - neverthless - I have all the rules seemingly there on a fresh boot. I also have a new ‘interface’ - ifb4eth0.666. Since I’ve never messed with tc - I have no idea how/where/what is ‘saving’ these rules and making them persistent. I’m struggling to use google and grep -ir to see where Ubuntu is saving this.
>
> Furthermore - the scripts seem to be working now. Slightly embarassing - it could be the result of having mucked with the gentoo script and having two many variables flying around at once.
>
> I currently lose a small fraction of my bandwidth - but bufferbloat gets an A on the dslreports speedtest.
>
> I’m going to concentrate on understanding how / where these rules are getting made ‘persistent’.
Excellent.
There's nothing that saves `tc` rules (like iptables-save +
iptables-restore). The fact that you have "ifb4eth0.666" re-appearing
shows pretty clearly you've got something running "sqm start".
On OpenWRT the scripts run automatically when the network interface
comes up. udev is different, although you could have something hooked
in like `/etc/network/if-up.d`.
Alan
next prev parent reply other threads:[~2016-01-20 16:32 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
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 [this message]
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=569FB68A.6000100@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=Bloat@lists.bufferbloat.net \
--cc=brandon@burn.net \
--cc=moeller0@gmx.de \
/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