[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130410134609.46bcaeae@nehalam.linuxnetplumber.net>
Date: Wed, 10 Apr 2013 13:46:09 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Antonio Quartulli <antonio@...n-mesh.com>
Cc: Jamal Hadi Salim <jhs@...atatu.com>,
"David S. Miller" <davem@...emloft.net>,
"bridge@...ts.linux-foundation.org"
<bridge@...ts.linux-foundation.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH 1/3] if.h: add IFF_BRIDGE_RESTRICTED flag
On Wed, 10 Apr 2013 18:54:34 +0200
Antonio Quartulli <antonio@...n-mesh.com> wrote:
> Hi Jamal, all,
>
> On Tue, Apr 09, 2013 at 08:49:17 -0700, Jamal Hadi Salim wrote:
> > 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).
> >
>
> Thanks for your hints. After having struggled a bit I found out how to do it
> using ebtables and the mark target :)
>
> Thanks a Lot!
>
> These patches seem to be useless now
>
> Cheers,
>
Come back again, though. The ebtables method offers more flexibility which can
be a good or bad thing...
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists