From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: [PATCH net-next] bridge: multicast to unicast Date: Mon, 09 Jan 2017 13:44:03 +0100 Message-ID: <1483965843.17582.37.camel@sipsolutions.net> References: <20170102193214.31723-1-linus.luessing@c0d3.blue> <1483706872.4089.8.camel@sipsolutions.net> <20170107151530.GG3134@otheros> <1483949149.17582.1.camel@sipsolutions.net> <20170109124231.GA9086@otheros> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org, linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, Michael Braun , "David S . Miller" , Felix Fietkau To: Linus =?ISO-8859-1?Q?L=FCssing?= Return-path: In-Reply-To: <20170109124231.GA9086@otheros> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: bridge-bounces@lists.linux-foundation.org Errors-To: bridge-bounces@lists.linux-foundation.org List-Id: netdev.vger.kernel.org > >          A host SHOULD silently discard a datagram that is received via > >          a link-layer broadcast (see Section 2.4) but does not specify > >          an IP multicast or broadcast destination address. > > This example is the other way round. It specifies how the IP > destination should look like in case of link-layer broadcast. Not > how the link-layer destination should look like in case of a > multicast/broadcast IP destination. You stopped reading too early - snipped the context part for you :) johannes