From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Pete Heist <pete@heistp.net>, Georgios Amanakis <gamanakis@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Cake on elements of a bridge
Date: Thu, 06 Sep 2018 20:04:58 +0200 [thread overview]
Message-ID: <87efe65wol.fsf@toke.dk> (raw)
In-Reply-To: <139B295B-7371-43DE-B472-DE629C9B8432@heistp.net>
Pete Heist <pete@heistp.net> writes:
> I happen to also be working on a bridge setup, but it’s different. For
> one, I used fq_codel on a transparent bridge for a couple years in
> production and it worked well, so I trust it also would for cake.
>
> But now, my neighbor will access the Internet through my CPE device,
> but they must have a separate IP obtained through DHCP (i.e. a
> separate MAC address as well), and I want to use cake to manage the
> queue for both of us. I could do this with two routers and a
> transparent bridge, but I want to see if I can make it work with as
> few devices as possible, preferably just one EdgeRouter-X. I had two
> failures thus far:
>
> Fail #1: Do routing for the neighbors on their NS5AC Loco, and use the
> ER-X’s internal switch to bridge the neighbor’s and my WAN interfaces
> to the CPE. Doing cake on switch0 results in my WAN traffic going
> through the qdisc, but unsurprisingly, the neighbor’s traffic passes
> through the switch without going through the qdisc layer.
>
> Fail #2: Use the ER-X’s pseudo-ethernet functionality to add a second
> virtual Ethernet interface to the ER-X’s WAN interface. I could use
> IFB if I got two WAN interfaces working on the same box. This looks
> promising and I can pick up two DHCP addresses on one physical
> interface, but the ER-X doesn’t handle the routing situation where two
> interfaces have the same default router IP. (Using policy-based
> routing, what does it do when next-hop is the same for two different
> LAN subnets?)
>
> There will be a solution here, I just haven’t found it yet. I’m now
> thinking of a setup with a smart switch / VLANs and a transparent
> bridge through two physical interfaces of the ER-X (which only has 5
> ports total), but I’ll figure it out… :)
DHCP relay and normal routing? Or bridging with a kernel software bridge
rather than the hardware switch?
-Toke
next prev parent reply other threads:[~2018-09-06 18:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 10:19 Georgios Amanakis
2018-09-04 10:31 ` Toke Høiland-Jørgensen
2018-09-04 12:01 ` Georgios Amanakis
2018-09-06 17:37 ` Pete Heist
2018-09-06 18:04 ` Toke Høiland-Jørgensen [this message]
2018-09-06 18:51 ` Pete Heist
2018-09-10 19:29 ` Pete Heist
2018-09-10 19:55 ` Dave Taht
2018-09-10 22:40 ` [Cake] Cake vs fq_codel and c/burst on an ER-X bridge Pete Heist
2018-09-11 7:54 ` Sebastian Moeller
2018-09-11 8:20 ` Dave Taht
2018-09-11 8:20 ` Sebastian Moeller
2018-09-11 8:30 ` Dave Taht
2018-09-11 8:43 ` Sebastian Moeller
2018-09-11 18:27 ` Pete Heist
2018-09-11 18:29 ` Dave Taht
2018-09-11 18:42 ` Dave Taht
2018-09-19 13:27 ` Sebastian Moeller
2018-09-19 17:02 ` Dave Taht
2018-09-20 10:34 ` Sebastian Moeller
2018-09-20 17:05 ` Dave Taht
2018-09-20 18:19 ` Sebastian Moeller
2018-09-20 18:31 ` Dave Taht
2018-09-11 18:09 ` Pete Heist
2018-09-11 18:28 ` Sebastian Moeller
2018-09-11 18:45 ` Pete Heist
2018-09-11 18:47 ` Dave Taht
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=87efe65wol.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=gamanakis@gmail.com \
--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