All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vladimir Oltean <olteanv@gmail.com>,
	netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Ido Schimmel <idosch@idosch.org>,
	Nikolay Aleksandrov <razor@blackwall.org>,
	Roopa Prabhu <roopa@nvidia.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Florian Westphal <fw@strlen.de>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>,
	Marc Muehlfeld <mmuehlfe@redhat.com>
Subject: Re: [PATCH net-next 01/10] net: bridge: add document for IFLA_BR enum
Date: Tue, 21 Nov 2023 11:10:22 +0800	[thread overview]
Message-ID: <ZVwfniWZnX65w6sj@Laptop-X1> (raw)
In-Reply-To: <86124486-3290-4507-8158-57eaf5bbb8a4@lunn.ch>

On Sun, Nov 19, 2023 at 07:21:25PM +0100, Andrew Lunn wrote:
> > > + * @IFLA_BR_GROUP_FWD_MASK
> > > + *   The group forward mask. This is the bitmask that is applied to
> > > + *   decide whether to forward incoming frames destined to link-local
> > > + *   addresses. The addresses of the form is 01:80:C2:00:00:0X, which
> > > + *   means the bridge does not forward any link-local frames coming on
> > > + *   this port).
> > > + *
> > > + *   The default value is 0.
> 
> Where was the default value of 0 derived from?

I doc it as 0 because I saw in br_dev_setup()

        br->stp_enabled = BR_NO_STP;
        br->group_fwd_mask = BR_GROUPFWD_DEFAULT;
        br->group_fwd_mask_required = BR_GROUPFWD_DEFAULT;

and #define BR_GROUPFWD_DEFAULT     0

Thanks
Hangbin
> 
> br_handle_frame() seems to handle 01-80-C2-00-00-00 using is used for
> BPDUs. 01-80-C2-00-00-01 is explicitly dropped, since its Pause, which
> i doubt you want to forward. LLDP has some level of processing.
> 
> Should the default value reflect this?
> 
>        Andrew

  reply	other threads:[~2023-11-21  3:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17  9:31 [PATCH net-next 00/10] Doc: update bridge doc Hangbin Liu
2023-11-17  9:31 ` [PATCH net-next 01/10] net: bridge: add document for IFLA_BR enum Hangbin Liu
2023-11-18 17:45   ` Jakub Kicinski
2023-11-21  3:28     ` Hangbin Liu
2023-11-21 16:21       ` Jakub Kicinski
2023-11-23 14:07         ` Hangbin Liu
2023-11-19 16:46   ` Vladimir Oltean
2023-11-19 18:21     ` Andrew Lunn
2023-11-21  3:10       ` Hangbin Liu [this message]
2023-11-21  3:06     ` Hangbin Liu
2023-11-17  9:31 ` [PATCH net-next 02/10] net: bridge: add document for IFLA_BRPORT enum Hangbin Liu
2023-11-20 11:31   ` Vladimir Oltean
2023-11-21  3:10     ` Hangbin Liu
2023-11-17  9:31 ` [PATCH net-next 03/10] net: bridge: add document for bridge sysfs attribute Hangbin Liu
2023-11-17  9:31 ` [PATCH net-next 04/10] docs: bridge: Add kAPI/uAPI fields Hangbin Liu
2023-11-17  9:31 ` [PATCH net-next 05/10] docs: bridge: add STP doc Hangbin Liu
2023-11-20 11:39   ` Vladimir Oltean
2023-11-21  3:02     ` Hangbin Liu
2023-11-24 13:18       ` Nikolay Aleksandrov
2023-11-24 14:01         ` Hangbin Liu
2023-12-03 20:12       ` Stephen Hemminger
2023-11-17  9:31 ` [PATCH net-next 06/10] docs: bridge: add VLAN doc Hangbin Liu
2023-11-17  9:31 ` [PATCH net-next 07/10] docs: bridge: add multicast doc Hangbin Liu
2023-11-17  9:31 ` [PATCH net-next 08/10] docs: bridge: add switchdev doc Hangbin Liu
2023-11-20 11:56   ` Vladimir Oltean
2023-11-17  9:31 ` [PATCH net-next 09/10] docs: bridge: add netfilter doc Hangbin Liu
2023-11-17  9:31 ` [PATCH net-next 10/10] docs: bridge: add other features Hangbin Liu

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=ZVwfniWZnX65w6sj@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=fw@strlen.de \
    --cc=idosch@idosch.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=mmuehlfe@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.com \
    --cc=stephen@networkplumber.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.