From: Marek Kierdelewicz <marek@piasta.pl>
To: "Ethy H. Brito" <ethy.brito@inexo.com.br>
Cc: netfilter@vger.kernel.org
Subject: Re: shaping vlans - revisited
Date: Sat, 5 Feb 2011 13:46:21 +0100 [thread overview]
Message-ID: <20110205134621.44b63335@catus> (raw)
In-Reply-To: <20110204142417.30dbe5fa@pulsar.inexo.com.br>
Hi,
>IFB??
>
>it may be a good way out.
>Do you know any discussion list or forum for it?
>I just read a few sites and have some questions.
You could do it this way:
1) make sure ifb is modprobed and interface ifb0 is up
2) redirect outgoing traffic on each vlan interface to ifb0
tc qdisc add dev $DEV root handle 1: htb default 1
tc class add dev $DEV parent 1: classid 1:1 htb rate 100mbit
rc filter add dev $DEV protocol ip parent 1: prio 4 u32 \
match ip dst 0.0.0.0/0 flowid :1 \
action mirred egress redirect dev ifb0
... where $DEV is vlanX, vlanY ...
3) Add shaping on ifb0 just like you did earlier on eth1.
Best regards,
Marek Kierdelewicz
next prev parent reply other threads:[~2011-02-05 12:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 17:29 Fw: shaping vlans - revisited Ethy H. Brito
2011-02-03 18:50 ` Andrew Beverley
2011-02-03 20:01 ` Ethy H. Brito
2011-02-04 2:59 ` Andrew Beverley
2011-02-04 7:43 ` Marek Kierdelewicz
2011-02-04 14:05 ` Ethy H. Brito
2011-02-04 14:24 ` Andrew Beverley
2011-02-04 16:24 ` Ethy H. Brito
2011-02-05 2:10 ` Andrew Beverley
2011-02-05 12:46 ` Marek Kierdelewicz [this message]
2011-02-05 14:42 ` Ethy H. Brito
2011-02-05 14:52 ` Marek Kierdelewicz
2011-02-05 16:32 ` Ethy H. Brito
2011-02-05 16:41 ` Marek Kierdelewicz
2011-02-05 23:26 ` Ethy H. Brito
2011-02-04 3:28 ` Jan Engelhardt
2011-02-04 3:42 ` Grant Taylor
2011-02-04 14:06 ` Ethy H. Brito
2011-02-05 13:56 ` Ethy H. Brito
-- strict thread matches above, loose matches on Subject: below --
2011-02-03 15:38 Ethy H. Brito
2011-02-03 15:46 ` Marek Kierdelewicz
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=20110205134621.44b63335@catus \
--to=marek@piasta.pl \
--cc=ethy.brito@inexo.com.br \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.