From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org
Subject: Re: [Bridge] [PATCH net-next] net: bridge: add per-port group_fwd_mask with less restrictions
Date: Fri, 29 Sep 2017 08:14:20 -0700 [thread overview]
Message-ID: <20170929081420.3b069170@xeon-e3> (raw)
In-Reply-To: <1506517964-17479-1-git-send-email-nikolay@cumulusnetworks.com>
On Wed, 27 Sep 2017 16:12:44 +0300
Nikolay Aleksandrov <nikolay@cumulusnetworks.com> wrote:
> We need to be able to transparently forward most link-local frames via
> tunnels (e.g. vxlan, qinq). Currently the bridge's group_fwd_mask has a
> mask which restricts the forwarding of STP and LACP, but we need to be able
> to forward these over tunnels and control that forwarding on a per-port
> basis thus add a new per-port group_fwd_mask option which only disallows
> mac pause frames to be forwarded (they're always dropped anyway).
> The patch does not change the current default situation - all of the others
> are still restricted unless configured for forwarding.
> We have successfully tested this patch with LACP and STP forwarding over
> VxLAN and qinq tunnels.
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
LACP is fine, but STP must not be forwarded if STP in user or kernel
mode is enabled.
Please update this patch or revert it.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next] net: bridge: add per-port group_fwd_mask with less restrictions
Date: Fri, 29 Sep 2017 08:14:20 -0700 [thread overview]
Message-ID: <20170929081420.3b069170@xeon-e3> (raw)
In-Reply-To: <1506517964-17479-1-git-send-email-nikolay@cumulusnetworks.com>
On Wed, 27 Sep 2017 16:12:44 +0300
Nikolay Aleksandrov <nikolay@cumulusnetworks.com> wrote:
> We need to be able to transparently forward most link-local frames via
> tunnels (e.g. vxlan, qinq). Currently the bridge's group_fwd_mask has a
> mask which restricts the forwarding of STP and LACP, but we need to be able
> to forward these over tunnels and control that forwarding on a per-port
> basis thus add a new per-port group_fwd_mask option which only disallows
> mac pause frames to be forwarded (they're always dropped anyway).
> The patch does not change the current default situation - all of the others
> are still restricted unless configured for forwarding.
> We have successfully tested this patch with LACP and STP forwarding over
> VxLAN and qinq tunnels.
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
LACP is fine, but STP must not be forwarded if STP in user or kernel
mode is enabled.
Please update this patch or revert it.
next prev parent reply other threads:[~2017-09-29 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 13:12 [Bridge] [PATCH net-next] net: bridge: add per-port group_fwd_mask with less restrictions Nikolay Aleksandrov
2017-09-27 13:12 ` Nikolay Aleksandrov
2017-09-29 5:04 ` David Miller
2017-09-29 15:14 ` Stephen Hemminger [this message]
2017-09-29 15:14 ` Stephen Hemminger
2017-09-29 21:01 ` [Bridge] " Nikolay Aleksandrov
2017-09-29 21:01 ` Nikolay Aleksandrov
2017-09-29 21:51 ` [Bridge] " Stephen Hemminger
2017-09-29 21:51 ` Stephen Hemminger
2017-09-29 22:11 ` [Bridge] " Nikolay Aleksandrov
2017-09-29 22:11 ` Nikolay Aleksandrov
2017-09-29 22:21 ` [Bridge] " Roopa Prabhu
2017-09-29 22:21 ` Roopa Prabhu
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=20170929081420.3b069170@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
/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.