Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Alban <albeu@free.fr>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net, Alban <albeu@free.fr>
Subject: Re: [Cake] Recommendations for using cake in complex setup (wireguard + vlan + bond)
Date: Mon, 1 Jul 2019 15:13:16 +0200	[thread overview]
Message-ID: <20190701151316.2f037eea@eos> (raw)
In-Reply-To: <87tvc654he.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]

On Mon, 01 Jul 2019 14:22:37 +0200
Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Alban <albeu@free.fr> writes:
> 
> > Hi everybody,
> >
> > I am setting a new router with a non trivial setup and I really
> > like to get some recommendations on how to best use cake. First of
> > all the router is using VLAN on top of 2 bonded gigabit Ethernet
> > interface:
> >
> >                         +--> VLAN1 (LAN)
> >  eth0 <--+              |
> >          +---> bond0 <--+--> VLAN2 (WAN1)
> >  eth1 <--+              |
> >                         +--> VLAN3 (WAN2)
> >
> > The bond is using LACP, but mainly for redundancy and not for the
> > increased bandwidth. Both WAN VLAN are going to ISP provided
> > FritzBox connected to 50/10Mbit VDSL2 lines.  
> 
> What are the physical interfaces connected to? How is the traffic
> getting to the FritzBoxes?

I should have mentioned that the above diagram depict the logical
interfaces inside the router. The router only physical connection
is via the bond to a switch stack, the logical separation of LAN and
WAN is done using VLANs.

The physical interfaces (eth0/1) are gigabit Ethernet, one FritzBox is
directly connected to the same switch, the second one is connected via
yet another switches as it is not in the same physical location. Like
this:

             (VLAN1)      (VLAN1)
             clients      clients
                |            |
             +-----+      +-----+
  Router <-->| SW1 |<---->| SW2 |
             +--+--+      +--+--+
                |            |
               FB1          FB2
             (VLAN2)      (VLAN3)

Alban

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-07-01 13:13 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 [this message]
2019-07-02  3:28 ` David Lang

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=20190701151316.2f037eea@eos \
    --to=albeu@free.fr \
    --cc=cake@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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