From: Nick Carter <ncarter100@gmail.com>
To: David Lamparter <equinox@diac24.net>
Cc: netdev@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>,
davem@davemloft.net
Subject: Re: [PATCH 2/2] bridge: pass through 802.1X & co. in 'dumb' mode
Date: Wed, 29 Jun 2011 23:56:18 +0100 [thread overview]
Message-ID: <BANLkTinJCtr8ZTYHZVc=+oWJGHjq3W3HhQ@mail.gmail.com> (raw)
In-Reply-To: <1309298599-11266-2-git-send-email-equinox@diac24.net>
On 28 June 2011 23:03, David Lamparter <equinox@diac24.net> wrote:
> when operating without STP, we're a dumb switch and should be able to
> forward ethernet management protocols like 802.1X, LLDP and GVRP.
I don't like the idea of tying STP on / off with the forwarding of
these other protocols. These other protocols are not dependent on
STP. These diffs change the default behaviour so that if someone
writes an 802.1X authenticator in userspace then all deployments will
have to turn STP on to be able to use it !!
If I was a sysadmin and I configured 'bridge_stp off' in say
/etc/interfaces, i would be very surprised and alarmed to find I had
turned *on* forwarding a load of protocols.
Also many of these addresses are reserved for future use. Do we
really want to forward them before we know what they will be used for
?
Nick
>
> if this is not desired, it can be enacted as local policy through
> ebtables.
>
> if we're in STP mode we basically claim to be an intelligent switch and
> should implement these protocols properly (in userspace).
>
> Signed-off-by: David Lamparter <equinox@diac24.net>
> ---
> compile-tested only
>
> net/bridge/br_input.c | 9 ++++++---
> 1 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/net/bridge/br_input.c b/net/bridge/br_input.c
> index c873db5..4cee1b5 100644
> --- a/net/bridge/br_input.c
> +++ b/net/bridge/br_input.c
> @@ -167,16 +167,19 @@ rx_handler_result_t br_handle_frame(struct sk_buff **pskb)
> if (dest[5] == 0x01 || dest[5] == 0x02)
> return RX_HANDLER_PASS;
>
> - /* If STP is turned off, then forward */
> - if (p->br->stp_enabled == BR_NO_STP && dest[5] == 0)
> + /* If STP is turned off, we're a dumb switch and therefore
> + * forward the remaining link-locals. (STP, 802.1X, LLDP,
> + * GVRP & co.) */
> + if (p->br->stp_enabled == BR_NO_STP)
> goto forward;
>
> if (NF_HOOK(NFPROTO_BRIDGE, NF_BR_LOCAL_IN, skb, skb->dev,
> NULL, br_handle_local_finish)) {
> return RX_HANDLER_CONSUMED; /* consumed by filter */
> } else {
> + /* stay on physdev for userspace implementation */
> *pskb = skb;
> - return RX_HANDLER_PASS; /* continue processing */
> + return RX_HANDLER_PASS;
> }
> }
>
> --
> 1.7.5.3
>
>
next prev parent reply other threads:[~2011-06-29 22:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 21:39 [PATCH] bridge: Forward EAPOL Kconfig option BRIDGE_PAE_FORWARD Nick Carter
2011-06-23 22:29 ` Stephen Hemminger
2011-06-24 18:29 ` Nick Carter
2011-06-24 19:08 ` Stephen Hemminger
2011-06-24 21:29 ` Nick Carter
2011-06-24 23:33 ` Nick Carter
2011-06-28 15:02 ` David Lamparter
2011-06-28 15:10 ` Stephen Hemminger
2011-06-28 16:00 ` David Lamparter
2011-06-28 18:34 ` Nick Carter
2011-06-28 18:58 ` David Lamparter
2011-06-28 20:00 ` Nick Carter
2011-06-28 20:22 ` David Lamparter
2011-06-28 20:54 ` Nick Carter
2011-06-28 21:04 ` David Lamparter
2011-06-28 21:22 ` Nick Carter
2011-06-28 21:46 ` David Lamparter
2011-06-28 22:03 ` [PATCH 1/2] bridge: ignore pause & bonding frames David Lamparter
2011-06-28 22:03 ` [PATCH 2/2] bridge: pass through 802.1X & co. in 'dumb' mode David Lamparter
2011-06-29 22:56 ` Nick Carter [this message]
2011-06-28 22:10 ` [PATCH v2] bridge: ignore pause & bonding frames David Lamparter
2011-06-29 22:46 ` [PATCH] bridge: Forward EAPOL Kconfig option BRIDGE_PAE_FORWARD Nick Carter
2011-06-29 23:34 ` Stephen Hemminger
2011-07-01 10:16 ` David Lamparter
2011-07-01 14:58 ` Michał Mirosław
2011-07-01 15:16 ` bridge vs. bonding/pause frames (was: Forward EAPOL...) David Lamparter
2011-07-01 17:59 ` Michał Mirosław
2011-07-01 21:10 ` Nick Carter
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='BANLkTinJCtr8ZTYHZVc=+oWJGHjq3W3HhQ@mail.gmail.com' \
--to=ncarter100@gmail.com \
--cc=davem@davemloft.net \
--cc=equinox@diac24.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).