From: Brandon Applegate <brandon@burn.net>
To: Bloat@lists.bufferbloat.net
Subject: [Bloat] Getting started with sqm-scripts - latency good, bandwidth decimated
Date: Tue, 19 Jan 2016 18:33:02 -0500 [thread overview]
Message-ID: <B1BA8A7F-EDC9-4A5D-B380-12043C1E3E08@burn.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1584 bytes --]
Disclaimer: if this is the wrong list for such a question - let me know. This is specifically about the sqm-scripts package...
Hello,
I’ve been reading all I can on the bufferbloat website and also trying to understand the evolution of the various scripts (debloat, sqm, etc).
I managed to get sqm-scripts on my firewall (Ubuntu linux on a PC - no *wrt etc). Got it built with the ‘linux’ platform. Since this is Ubuntu 12.04 - I had to cheat a bit and pull down the iproute2 source from 14.04. I’ve tweaked the main sqm script to reflect this for the tc bindary - this is working. I also updated my kernel to a later version that supports fq_codel.
My topology is ‘on a stick’. I have one gig interface to a managed switch, on which are eth0.666 (outside/wan) and eth0.10 (inside).
I have 30/5 cable service, and have tried both those values as well as 90% in my /etc/sqm/*conf file.
I’ve tried both eth0 (raw/parent interface) as well as eth0.666.
No matter what I do - my bandwidth is 10% of what it should be. I get approx. 3/4mbit down + 2/3mbit up on dslreports speedtest. Bufferbloat looks great though - A+.
Is there something inherent I’m doing wrong ? Something to do with my ‘on a stick’ topology biting me ? Kernel version (Ubuntu’s 3.13.0-74-generic btw).
Thanks in advance for any help or info (or pointer to a more appropriate list).
--
Brandon Applegate - CCIE 10273
PGP Key fingerprint:
830B 4802 1DD4 F4F9 63FE B966 C0A7 189E 9EC0 3A74
"SH1-0151. This is the serial number, of our orbital gun."
[-- Attachment #1.2: Type: text/html, Size: 3445 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next reply other threads:[~2016-01-19 23:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 23:33 Brandon Applegate [this message]
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
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=B1BA8A7F-EDC9-4A5D-B380-12043C1E3E08@burn.net \
--to=brandon@burn.net \
--cc=Bloat@lists.bufferbloat.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