General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dev <dev@logicalwebhost.com>
To: Pete Heist <pete@heistp.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fq_codel on bridge multiple subnets?
Date: Thu, 3 Jan 2019 21:22:35 -0800	[thread overview]
Message-ID: <F1ABFFE7-414E-40DD-B34B-15D1794E15A0@logicalwebhost.com> (raw)
In-Reply-To: <E2FF4C6F-DC1F-469B-874E-7332BE5B3A0C@heistp.net>

Okay, so this is what I have for /etc/network/interfaces (replaced eth0-2 with what Debian Buster actually calls them):

auto lo br0
iface lo inet loopback

allow-hotplug enp8s0
iface enp8s0 inet static
	address 192.168.10.200
	netmask 255.255.255.0
	gateway 192.168.10.1
	dns-nameservers 8.8.8.8

iface enp7s6 inet manual
	tc qdisc add dev enp7s6 root fq_codel

iface enp9s2 inet manual
	tc qdisc add dev enp9s2 root fq_codel

# Bridge setup
iface br0 inet static
	bridge_ports enp7s6 enp9s2
	#bridge_stp on
		address 192.168.3.50
		broadcast 192.168.3.255
		netmask 255.255.255.0
		gateway 192.168.3.1
		dns-nameservers 8.8.8.8

so my bridge interfaces now show:

>: tc -s qdisc show dev enp7s6
qdisc fq_codel 0: root refcnt 2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0

and 

>: tc -s qdisc show dev enp9s2
qdisc fq_codel 0: root refcnt 2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
 Sent 12212 bytes 80 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0

with my bridge like:

ip a 

5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:04:5a:86:a2:84 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.50/24 brd 192.168.3.255 scope global br0
       valid_lft forever preferred_lft forever
    inet6 fe80::204:5aff:fe86:a284/64 scope link
       valid_lft forever preferred_lft forever

So do I have it configured right or should I change something? I haven’t gotten a chance to stress test it yet, but will try tomorrow.

- Dev

> On Jan 3, 2019, at 10:54 AM, Pete Heist <pete@heistp.net> wrote:
> 
> 
>> On Jan 3, 2019, at 7:12 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> 
>> Dev <dev@logicalwebhost.com> writes:
>> 
>>> I’m trying to create a bridge on eth1 and eth2, with a management
>>> interface on eth0, then enable fq_codel on the bridge. My bridge
>>> interface looks like:
>> 
>> You'll probably want to put FQ-CoDel on the underlying physical
>> interfaces, as those are the ones actually queueing the traffic...
> 
> I can confirm that. I'm currently using a bridge on my home router. eth3 and eth4 are bridged, eth4 is connected to the CPE device which goes out to the Internet, eth4 is where queue management is applied, and this works. It does not work to add this to br0…
> 


  reply	other threads:[~2019-01-04  5:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 17:32 Dev
2019-01-03 18:12 ` Toke Høiland-Jørgensen
2019-01-03 18:54   ` Pete Heist
2019-01-04  5:22     ` Dev [this message]
2019-01-04  9:19       ` Pete Heist
2019-01-04 18:20         ` Dev
2019-01-04 18:57           ` Dave Taht
2019-01-04 20:33             ` [Bloat] fq_codel on bridge throughput test/config Dev
2019-01-04 20:40               ` Toke Høiland-Jørgensen
2019-01-16  0:54                 ` Dev
2019-01-05  0:17               ` Stephen Hemminger
2019-01-03 21:23 ` [Bloat] reatime buffer monitoring? Dev
2019-01-03 21:51   ` Pete Heist
2019-01-03 22:31     ` Dave Taht
2019-01-04  2:06       ` Dev

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=F1ABFFE7-414E-40DD-B34B-15D1794E15A0@logicalwebhost.com \
    --to=dev@logicalwebhost.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=pete@heistp.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