From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <5164387D.8080700@mojatatu.com> Date: Tue, 09 Apr 2013 11:49:17 -0400 From: Jamal Hadi Salim MIME-Version: 1.0 References: <1365442863-32394-1-git-send-email-antonio@open-mesh.com> <1365442863-32394-2-git-send-email-antonio@open-mesh.com> <20130409075606.GB3771@open-mesh.com> <51641049.3030100@mojatatu.com> <20130409135143.GA5177@open-mesh.com> In-Reply-To: <20130409135143.GA5177@open-mesh.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [PATCH 1/3] if.h: add IFF_BRIDGE_RESTRICTED flag List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Antonio Quartulli Cc: Stephen Hemminger , "netdev@vger.kernel.org" , "bridge@lists.linux-foundation.org" , "David S. Miller" On 13-04-09 09:51 AM, Antonio Quartulli wrote: > > Does this work at the bridge level? A packet entering a port and going out from > another one can be affected by tc/mark? Yes of course. And on any construct that looks like a netdev (tunnels etc). cheers, jamal