From: Eric Dumazet <eric.dumazet@gmail.com>
To: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
Cc: netdev@vger.kernel.org
Subject: Re: IFB and bridges
Date: Sun, 11 Dec 2011 09:58:26 +0100 [thread overview]
Message-ID: <1323593906.4016.42.camel@edumazet-laptop> (raw)
In-Reply-To: <1323566146.3159.186.camel@denise.theartistscloset.com>
Le samedi 10 décembre 2011 à 20:15 -0500, John A. Sullivan III a écrit :
> Hello, all. This is more an "out of curiosity" question. I'm starting
> to build a test environment for all I've learned about Linux traffic
> shaping over the last week. One of the devices happens to be configured
> as a bridge. It quickly became apparent that I needed to do shaping on
> the individual ports and not the bridge port.
>
> This would be a real pain if I have lots of ports - 8 or 10 or 20
> identical configurations. Would this be an ideal use for IFB? That is,
> to redirect all ports to IFB and apply one set qdiscs/classes? Thanks -
I have no idea what your problem is.
You want to shape either egress or ingress, for different reasons (most
people shape egress), but on proxies an ingress and egress combination
is welcomed.
But having to use ingress on the same machine in place of egress, I dont
see why.
next prev parent reply other threads:[~2011-12-11 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 1:15 IFB and bridges John A. Sullivan III
2011-12-11 8:58 ` Eric Dumazet [this message]
2011-12-11 22:38 ` John A. Sullivan III
2011-12-11 22:00 ` Eric Dumazet
2011-12-12 0:42 ` John A. Sullivan III
2011-12-14 19:36 ` Paweł Staszewski
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1323593906.4016.42.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=jsullivan@opensourcedevel.com \
--cc=netdev@vger.kernel.org \
/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