From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Quartulli <antonio@open-mesh.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH 1/3] if.h: add IFF_BRIDGE_RESTRICTED flag
Date: Wed, 10 Apr 2013 13:46:09 -0700 [thread overview]
Message-ID: <20130410134609.46bcaeae@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20130410165434.GB5177@open-mesh.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Wed, 10 Apr 2013 18:54:34 +0200
Antonio Quartulli <antonio@open-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...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Quartulli <antonio@open-mesh.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/3] if.h: add IFF_BRIDGE_RESTRICTED flag
Date: Wed, 10 Apr 2013 13:46:09 -0700 [thread overview]
Message-ID: <20130410134609.46bcaeae@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20130410165434.GB5177@open-mesh.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Wed, 10 Apr 2013 18:54:34 +0200
Antonio Quartulli <antonio@open-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...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-10 20:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 17:41 [Bridge] [PATCH 0/3] bridge: implement restricted forwarding policy Antonio Quartulli
2013-04-08 17:41 ` Antonio Quartulli
2013-04-08 17:41 ` [Bridge] [PATCH 1/3] if.h: add IFF_BRIDGE_RESTRICTED flag Antonio Quartulli
2013-04-08 17:41 ` Antonio Quartulli
2013-04-08 18:58 ` [Bridge] " Stephen Hemminger
2013-04-08 18:58 ` Stephen Hemminger
2013-04-09 6:33 ` [Bridge] " Antonio Quartulli
2013-04-09 6:33 ` Antonio Quartulli
2013-04-09 7:56 ` [Bridge] " Antonio Quartulli
2013-04-09 7:56 ` Antonio Quartulli
2013-04-09 12:57 ` [Bridge] " Jamal Hadi Salim
2013-04-09 12:57 ` Jamal Hadi Salim
2013-04-09 13:51 ` [Bridge] " Antonio Quartulli
2013-04-09 13:51 ` Antonio Quartulli
2013-04-09 15:49 ` [Bridge] " Jamal Hadi Salim
2013-04-09 15:49 ` Jamal Hadi Salim
2013-04-10 16:54 ` [Bridge] " Antonio Quartulli
2013-04-10 16:54 ` Antonio Quartulli
2013-04-10 20:46 ` Stephen Hemminger [this message]
2013-04-10 20:46 ` Stephen Hemminger
2013-04-11 10:56 ` [Bridge] " Antonio Quartulli
2013-04-11 10:56 ` Antonio Quartulli
2013-04-11 11:03 ` [Bridge] " Jamal Hadi Salim
2013-04-11 11:03 ` Jamal Hadi Salim
2013-04-08 17:41 ` [Bridge] [PATCH 2/3] sk_buff: add bridge_restricted flag Antonio Quartulli
2013-04-08 17:41 ` Antonio Quartulli
2013-04-08 17:41 ` [Bridge] [PATCH 3/3] bridge: implement restricted port forwarding policy Antonio Quartulli
2013-04-08 17:41 ` Antonio Quartulli
2013-05-06 18:48 ` Using skb->mark outside netfilter (was: [PATCH 0/3] bridge: implement restricted forwarding policy) Antonio Quartulli
2013-05-07 13:04 ` Using skb->mark outside netfilter Jamal Hadi Salim
2013-05-07 13:23 ` Antonio Quartulli
2013-05-07 13:30 ` Jamal Hadi Salim
2013-05-07 14:17 ` Antonio Quartulli
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=20130410134609.46bcaeae@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=antonio@open-mesh.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.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 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.