Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: David Lang <david@lang.hm>,  cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Turris Omnia
Date: Mon, 07 Nov 2016 09:35:19 -0500	[thread overview]
Message-ID: <m3bmxrcq8o.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <325AB103-34B2-45A1-BB34-EBA0BD73B43E@gmx.de> (Sebastian Moeller's message of "Mon, 7 Nov 2016 10:59:55 +0100")

>>>>> "SM" == Sebastian Moeller <moeller0@gmx.de> writes:

DL> I wonder if you are running into the problem with encryption and
DL> packet re-ordering that was solved a couple months ago, try disabling
DL> fq_codel or test without encryption to see if that's the problem.

SM> 	I believe this problem only occurred with the fq code built
SM> into the wifi driver or ieee80211 subsystem, so running fq_codel on
SM> top of a wifi interface should not cause re-ordering that could
SM> confuse the driver.

As I noted in my last reply to David, rebooting w/ /etc/init.d/wshaper
disabled fixed things.

In the working scenario tc -d q reports:

qdisc noqueue 0: dev lo root refcnt 2 
qdisc mq 0: dev eth0 root 
qdisc fq_codel 0: dev eth0 parent :1 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth0 parent :2 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth0 parent :3 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth0 parent :4 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth0 parent :5 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth0 parent :6 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth0 parent :7 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth0 parent :8 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc mq 0: dev eth1 root 
qdisc fq_codel 0: dev eth1 parent :1 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth1 parent :2 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth1 parent :3 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth1 parent :4 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth1 parent :5 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth1 parent :6 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth1 parent :7 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth1 parent :8 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc mq 0: dev eth2 root 
qdisc fq_codel 0: dev eth2 parent :1 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth2 parent :2 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth2 parent :3 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth2 parent :4 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth2 parent :5 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth2 parent :6 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth2 parent :7 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev eth2 parent :8 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc noqueue 0: dev br-lan root refcnt 2 
qdisc mq 0: dev wlan1 root 
qdisc fq_codel 0: dev wlan1 parent :1 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan1 parent :2 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan1 parent :3 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan1 parent :4 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc mq 0: dev wlan0 root 
qdisc fq_codel 0: dev wlan0 parent :1 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan0 parent :2 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan0 parent :3 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 
qdisc fq_codel 0: dev wlan0 parent :4 limit 1024p flows 1024 quantum 1514 target 5.0ms interval 100.0ms ecn 

Starting wshaper changes that with this diff:

@@ -29 +29,5 @@
-qdisc noqueue 0: dev br-lan root refcnt 2 
+qdisc htb 1: dev br-lan root refcnt 2 r2q 10 default 20 direct_packets_stat 0 ver 3.17 direct_qlen 1000
+qdisc sfq 10: dev br-lan parent 1:10 limit 127p quantum 1514b depth 127 flows 128/1024 divisor 1024 perturb 10sec 
+qdisc sfq 20: dev br-lan parent 1:20 limit 127p quantum 1514b depth 127 flows 128/1024 divisor 1024 perturb 10sec 
+qdisc sfq 30: dev br-lan parent 1:30 limit 127p quantum 1514b depth 127 flows 128/1024 divisor 1024 perturb 10sec 
+qdisc ingress ffff: dev br-lan parent ffff:fff1 ---------------- 

br-lan only has eth0 and eth2, which are not in use, so the difference
must be somewhere else in what it does.

Thanks.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6

      reply	other threads:[~2016-11-07 14:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-06 21:54 James Cloos
2016-11-07  0:52 ` David Lang
2016-11-07  1:01   ` James Cloos
2016-11-07  1:45     ` David Lang
2016-11-07  5:29       ` James Cloos
2016-11-07  5:47         ` David Lang
2016-11-07 14:30           ` James Cloos
2016-11-07 14:54             ` Toke Høiland-Jørgensen
2016-11-07 16:00               ` James Cloos
2016-11-07 17:41             ` Dave Täht
2016-11-07  9:59         ` Sebastian Moeller
2016-11-07 14:35           ` James Cloos [this message]

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=m3bmxrcq8o.fsf@carbon.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    --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