[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOaVG17nHuoRsf2Kss6LnpgC-Aojcso_zLYyBa18Vn9CGGY+GA@mail.gmail.com>
Date: Mon, 8 Apr 2013 11:58:48 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Antonio Quartulli <antonio@...n-mesh.com>
Cc: "David S. Miller" <davem@...emloft.net>,
bridge@...ts.linux-foundation.org, netdev@...r.kernel.org
Subject: Re: [PATCH 1/3] if.h: add IFF_BRIDGE_RESTRICTED flag
The standard way to do this is to use netfilter. Considering the
additional device flags and skb flag changes, I am not sure that your
method is better.
On Mon, Apr 8, 2013 at 10:41 AM, Antonio Quartulli
<antonio@...n-mesh.com> wrote:
> This new flag tells whether a network device has to be
> considered as restricted in the new bridge forwarding logic.
>
> Signed-off-by: Antonio Quartulli <antonio@...n-mesh.com>
> ---
> include/uapi/linux/if.h | 1 +
> net/core/dev.c | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/if.h b/include/uapi/linux/if.h
> index 1ec407b..5c3a9bd 100644
> --- a/include/uapi/linux/if.h
> +++ b/include/uapi/linux/if.h
> @@ -83,6 +83,7 @@
> #define IFF_SUPP_NOFCS 0x80000 /* device supports sending custom FCS */
> #define IFF_LIVE_ADDR_CHANGE 0x100000 /* device supports hardware address
> * change when it's running */
> +#define IFF_BRIDGE_RESTRICTED 0x200000 /* device is bridge-restricted */
>
>
> #define IF_GET_IFACE 0x0001 /* for querying only */
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 3655ff9..49eafc8 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -4627,7 +4627,7 @@ int __dev_change_flags(struct net_device *dev, unsigned int flags)
>
> dev->flags = (flags & (IFF_DEBUG | IFF_NOTRAILERS | IFF_NOARP |
> IFF_DYNAMIC | IFF_MULTICAST | IFF_PORTSEL |
> - IFF_AUTOMEDIA)) |
> + IFF_AUTOMEDIA | IFF_BRIDGE_RESTRICTED)) |
> (dev->flags & (IFF_UP | IFF_VOLATILE | IFF_PROMISC |
> IFF_ALLMULTI));
>
> --
> 1.8.1.5
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists