Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] Fwd:  Cake on elements of a bridge
Date: Tue, 4 Sep 2018 14:06:26 +0200	[thread overview]
Message-ID: <E3C77CD8-3F7F-4AE1-8849-787D631F3C35@gmx.de> (raw)
In-Reply-To: <BA23B98A-85F3-4BDD-A871-5416C2E1C4FD@gmx.de>

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

Dear All,

again I sent privately what should have been on the list. Now, this does not add much to Toke's response, but since Georgios referenced it it seems doubly awkward to keep it off-list...

Best Regards
	Sebastian


> Begin forwarded message:
> 
> From: Sebastian Moeller <moeller0@gmx.de>
> Subject: Re: [Cake] Cake on elements of a bridge
> Date: September 4, 2018 at 12:31:15 GMT+2
> To: Georgios Amanakis <gamanakis@gmail.com>
> 
> Hi Georgios,
> 
> I believe this should work, it is also easy to test ;) 
> 
> I would note that in this situation you do not need to employ an ifb device, you can shape on each interfaces egress side to achieve the same effect with a little less computation. Nat will not work as it needs access to data structures only available in the host that actually performs the masquerading. I believe almost everything else should work.... Since you are behind the NAT router, even the dual-xxxhost options should just work...
> 
> Best Regards
> 	Sebastian
> 
> 
>> On Sep 4, 2018, at 12:19, Georgios Amanakis <gamanakis@gmail.com> wrote:
>> 
>> Dear All,
>> 
>> I was giving a transparent firewall a try, and wondered whether cake can be applied on the interfaces of a bridge. I want to put an extra router in-line between clients and the ISP-modem-router. It will have two interfaces (eth0 facing wan, eth1 facing lan), bridged together as br0. 
>> 
>> Can I fearlessly apply cake on eth0 and eth1? Would this be compatible with features like ingress, ack-filter or even nat?
>> 
>> Georgios
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
> 


[-- Attachment #2: Type: text/html, Size: 4296 bytes --]

           reply	other threads:[~2018-09-04 12:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <BA23B98A-85F3-4BDD-A871-5416C2E1C4FD@gmx.de>]

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=E3C77CD8-3F7F-4AE1-8849-787D631F3C35@gmx.de \
    --to=moeller0@gmx.de \
    --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