Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Alban <albeu@free.fr>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Recommendations for using cake in complex setup (wireguard + vlan + bond)
Date: Mon, 1 Jul 2019 20:28:40 -0700 (PDT)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1907012026330.5396@qynat-yncgbc> (raw)
In-Reply-To: <20190701135251.08defe75@eos>

As a general rule, you want to put Cake (or any other sqm system) just before 
your bottleneck link.

That's unlikely to be the LAN links, it's almost always going to be your WAN 
links.

If you have them there for redundancy, not for added bandwidth, I think the 
right thing to do is to put Cake on the bonded (logical) interface that they 
share, but set it to a bandwidth that either link can satisfy if the other is 
down.

David Lang

      parent reply	other threads:[~2019-07-02  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 11:52 Alban
2019-07-01 12:22 ` Toke Høiland-Jørgensen
2019-07-01 13:13   ` Alban
2019-07-02  3:28 ` David Lang [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/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.1907012026330.5396@qynat-yncgbc \
    --to=david@lang.hm \
    --cc=albeu@free.fr \
    --cc=cake@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