From: Dev <dev@logicalwebhost.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] fq_codel on bridge throughput test/config
Date: Fri, 4 Jan 2019 12:33:28 -0800 [thread overview]
Message-ID: <18FA4204-3E2E-48D6-9B51-7B1AC7767AA9@logicalwebhost.com> (raw)
In-Reply-To: <CAA93jw505QOZou=gVHXvD9WZk9WaUSMhrmDR8q45QB9nc2R0Hg@mail.gmail.com>
Okay, thanks to some help from the list, I’ve configured a transparent bridge running fq_codel which works for multiple subnet traffic. Here’s my setup:
Machine A ——— 192.168.10.200 — — bridge fq_codel machine B —— laptop C 192.168.10.150
Machine D ——— 192.168.3.50 — —|
On Machine A:
straight gigE interface 192.168.10.200
Bridge Machine B: enp3s0 mgmt interface
enp2s0 bridge interface 1
enp1s0 bridge interface 2
br0 bridge for 1 and 2
# The loopback network interface
auto lo br0
iface lo inet loopback
# The primary network interface
allow-hotplug enp3s0
iface enp3s0 inet static
address 172.16.0.5/24
gateway 172.16.0.5
dns-nameservers 8.8.8.8
iface enp1s0 inet manual
tc qdisc add dev enp1s0 root fq_codel
iface enp2s0 inet manual
tc qdisc add dev enp2s0 root fq_codel
# Bridge setup
iface br0 inet static
bridge_ports enp1s0 enp2s0
address 192.168.3.75
broadcast 192.168.3.255
netmask 255.255.255.0
gateway 192.168.3
note: I still have to run this command later, will troubleshoot at some point (unless you have suggestions to make it work):
tc qdisc add dev enp1s0 root fq_codel
To start, my pings from Machine A to Laptop C were around 0.75 msec, then I flooded the link from Machine A to Laptop C using:
dd if=/dev/urandom | ssh user@192.168.10.150 dd of=/dev/null
Then my pings went up to around 170 msec. Once I enabled fq_codel on the bridge machine B, my pings dropped to around 10 msec.
Hope this helps someone else working on a similar setup.
- Dev
next prev parent reply other threads:[~2019-01-04 20:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 17:32 [Bloat] fq_codel on bridge multiple subnets? Dev
2019-01-03 18:12 ` Toke Høiland-Jørgensen
2019-01-03 18:54 ` Pete Heist
2019-01-04 5:22 ` Dev
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 ` Dev [this message]
2019-01-04 20:40 ` [Bloat] fq_codel on bridge throughput test/config 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=18FA4204-3E2E-48D6-9B51-7B1AC7767AA9@logicalwebhost.com \
--to=dev@logicalwebhost.com \
--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