netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Bohac <jbohac@suse.cz>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Jay Vosburgh <fubar@us.ibm.com>, Jiri Bohac <jbohac@suse.cz>,
	netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: PATCH: fix bridged 802.3ad bonding
Date: Wed, 4 Jun 2008 10:24:25 +0200	[thread overview]
Message-ID: <20080604082425.GA3272@midget.suse.cz> (raw)
In-Reply-To: <20080603215519.298c0cd3@extreme>

On Tue, Jun 03, 2008 at 09:55:19PM -0700, Stephen Hemminger wrote:
> I prefer the following because it process all link-local frames through
> the normal input path. This means the frames will:
> 	* be filterable by netfilter

Well, the LACP frames are not filtered by netfilter when there is
bonding on its own (not part of a bridge), so I don't see why
this should change when the bond is made part of a bridge.

Maybe it is a good idea to run the LACP frames through netfilter,
but I think this should be done consistently in the bonding code,
whether or not bridging is set up, and probably on the individual
slave interfaces. It does not make sense to filter bonding's LACP
frames in ebtables, IMHO.

> 	* not forwarded across bridge (this is important).

I thought this was the case with my second patch as well (?)

 
> --- a/net/bridge/br_input.c	2008-06-03 21:44:54.000000000 -0700
> +++ b/net/bridge/br_input.c	2008-06-03 21:52:20.000000000 -0700
> @@ -135,15 +135,12 @@ struct sk_buff *br_handle_frame(struct n
>  		/* Pause frames shouldn't be passed up by driver anyway */
>  		if (skb->protocol == htons(ETH_P_PAUSE))
>  			goto drop;
> -
> -		/* Process STP BPDU's through normal netif_receive_skb() path */
> -		if (p->br->stp_enabled != BR_NO_STP) {
> -			if (NF_HOOK(PF_BRIDGE, NF_BR_LOCAL_IN, skb, skb->dev,
> -				    NULL, br_handle_local_finish))
> -				return NULL;
> -			else
> -				return skb;
> -		}
> +
> +		if (NF_HOOK(PF_BRIDGE, NF_BR_LOCAL_IN, skb, skb->dev,
> +			    NULL, br_handle_local_finish))
> +			return NULL;	/* frame consumed by filter */
> +		else
> +			return skb;	/* continue processing */
>  	}
>  
>  	switch (p->state) {

where did the "if (p->br->stp_enabled != BR_NO_STP)" condition
go? Is it not needed? I thought it was there to prevent the STP
BPDUs from being handled when STP is turned off.

-- 
Jiri Bohac <jbohac@suse.cz>
SUSE Labs, SUSE CZ


  reply	other threads:[~2008-06-04  8:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 13:21 PATCH: fix bridged 802.3ad bonding Jiri Bohac
2008-06-03 14:13 ` Patrick McHardy
2008-06-03 16:46 ` Stephen Hemminger
2008-06-03 19:32   ` Jiri Bohac
2008-06-03 20:13     ` Stephen Hemminger
2008-06-03 21:20       ` Jiri Bohac
2008-06-03 21:22       ` Jay Vosburgh
2008-06-03 21:43         ` Stephen Hemminger
2008-06-04  4:55         ` Stephen Hemminger
2008-06-04  8:24           ` Jiri Bohac [this message]
2008-06-04 16:06             ` Stephen Hemminger
2008-06-05 10:13               ` Jiri Bohac
2008-06-10 22:42                 ` David Miller
2008-06-17 15:33                   ` Jiri Bohac

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=20080604082425.GA3272@midget.suse.cz \
    --to=jbohac@suse.cz \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --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).