From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=cD8LG65C7E3SIj/Vy+5zMpRcpGi6f9W21aYLlKZotiY=; b=OFoFAhOiKm2r3+KvpizVKYHmbduo1pzp38IfjuYgJ9Q6j8bExoHzP5FpwOqH7K5HsF BmgF5XNkTcwD6ng4RAApXOO1TH03x+cqn8UxUtpEcchulxGcyWEmuinRqVZMb7mHG8zw nPAmPZU+LDLl/5TvhDMwaMgrPQnr1/jiWurrc+vGZKFsF5WovF+iGaJazYdOj9G0nKb9 jB+qFE5K2xzkbtde4j5KaL8fnLpYDR9Mu89L0z+y+7Rtbjf6ZGt4ZhIXuJSMIQjexkXb zib/wfdTvqf3FF2KViqDzHPDKQL5MkSLIj/Kqj+V4IfIWqDrd8qF/bocdBNs/XyaMhrO XFkA== Message-ID: <54184BB9.8010802@gmail.com> Date: Tue, 16 Sep 2014 23:39:53 +0900 From: Toshiaki Makita MIME-Version: 1.0 References: <1410554691-18467-1-git-send-email-vyasevic@redhat.com> <1410554691-18467-4-git-send-email-vyasevic@redhat.com> <5415B6C2.5030702@gmail.com> <54170372.4080903@redhat.com> <54181EC1.2010608@lab.ntt.co.jp> <54183BCF.8070506@redhat.com> In-Reply-To: <54183BCF.8070506@redhat.com> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [PATCH 3/3] bridge; Automatically filter vlans configured on top of bridge List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: vyasevic@redhat.com, Toshiaki Makita , Vladislav Yasevich , netdev@vger.kernel.org Cc: shemminger@vyatta.com, bridge@lists.linux-foundation.org (14/09/16 (火) 22:31), Vlad Yasevich wrote: > On 09/16/2014 07:28 AM, Toshiaki Makita wrote: >> On 2014/09/16 0:19, Vlad Yasevich wrote: >>> On 09/14/2014 11:39 AM, Toshiaki Makita wrote: >>>> (14/09/13 (土) 5:44), Vladislav Yasevich wrote: >>>>> If the user configures vlan devices on top of the bridge, >>>>> automatically set up filter entries for it as long as >>>>> bridge vlan protocol matches that of the vlan. >>>>> This allows the user to atomatically receive vlan traffic >>>>> for the vlans that are convifgured. >>>> >>>> Changing br->vlan_proto seems to cause inconsistency between vlan >>>> interfaces and filter settings. >>>> Can we automatically change filters when setting vlan_proto? >>>> >>> >>> I thought we already do that in br_vlan_set_proto()? Nothing >>> here introduces any new kinds of issue with that code. >> >> I'm referring to a case like this: >> 1. create br0.10 (802.1ad) >> 2. change br->vlan_proto into 88a8 >> >> When creating br0.10 (1), br->vlan_proto is 8100 and different from >> protocol of br0.10, so it is ignored by br_vlan_rx_add_vid(). >> After changing br->vlan_proto (2), we might expect vlan 10 is not >> filtered on br0, but it will be filtered. > > Ok, I see what you mean. This one is a bit tough. Our options are: > 1) Return an error when configuring br0.10. This might break user-space. Not good. > 2) Ignore protocol when crating the filter. This is not good either as the user > may not switch the bridge vlan_proto value and we'd end up with a wrong filter. > 3) Re-implement .1ad support per-vlan instead of per-bridge. > > You see another other alternatives? We might be able to configure filterings on changing vlan_proto. 4) Memorize different protocol's filtering requests in br_vlan_rx_add_vid() and use them when switching vlan_proto. 5) Scan vlan devices on bridge device when changing vlan_proto. Thanks, Toshiaki Makita