From: Pete Heist <pete@heistp.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Cake on elements of a bridge
Date: Thu, 6 Sep 2018 20:51:20 +0200 [thread overview]
Message-ID: <6C556301-015B-4903-AE5A-F22D3517FFCC@heistp.net> (raw)
In-Reply-To: <87efe65wol.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
> On Sep 6, 2018, at 8:04 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Pete Heist <pete@heistp.net <mailto:pete@heistp.net>> writes:
>
>> 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:
>
> DHCP relay and normal routing? Or bridging with a kernel software bridge
> rather than the hardware switch?
I bet a regular software bridge would work. I’ll try it.
It looks like I’ll also need to do stateful firewalling for the neighbors. I was able to get my transparent bridge to do this with net.bridge.bridge-nf-call-iptables=1, I believe, so this should also theoretically work fine, somehow… :)
[-- Attachment #2: Type: text/html, Size: 5534 bytes --]
next prev parent reply other threads:[~2018-09-06 18:51 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
2018-09-06 18:51 ` Pete Heist [this message]
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=6C556301-015B-4903-AE5A-F22D3517FFCC@heistp.net \
--to=pete@heistp.net \
--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