From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Kierdelewicz Subject: Re: shaping vlans - revisited Date: Sat, 5 Feb 2011 17:41:50 +0100 Message-ID: <20110205174150.1fbd7658@catus> References: <20110203152944.635b42e8@pulsar.inexo.com.br> <1296759048.7587.3.camel@andybev> <20110203180118.62970fb1@pulsar.inexo.com.br> <1296788356.7587.70.camel@andybev> <20110204120533.7f470bab@pulsar.inexo.com.br> <1296829445.1634.1.camel@andybev> <20110204142417.30dbe5fa@pulsar.inexo.com.br> <20110205134621.44b63335@catus> <20110205124235.31bcd26e@babalu.inexo.com.br> <20110205155202.02eb6e7f@catus> <20110205143201.4a563987@babalu.inexo.com.br> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110205143201.4a563987@babalu.inexo.com.br> Sender: netfilter-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: "Ethy H. Brito" Cc: netfilter@vger.kernel.org Hi, >... and since the packets are not encapsulated yet, how they will >return from ifb to vlanX to be encapsulated?? >I see no tc command doing this in you example in your previous post. >Is there a missing command? That's the way ifb works. Example of ingress shaping that uses "action mirred egress redirect": http://www.linuxfoundation.org/collaborate/workgroups/networking/ifb#Typical_Usage Best regards, Marek Kierdelewicz