Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932414AbdCUKSw (ORCPT ); Tue, 21 Mar 2017 06:18:52 -0400 Received: from mail.us.es ([193.147.175.20]:52104 "EHLO mail.us.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932373AbdCUKSs (ORCPT ); Tue, 21 Mar 2017 06:18:48 -0400 Date: Tue, 21 Mar 2017 11:11:21 +0100 From: Pablo Neira Ayuso To: Linus =?iso-8859-1?Q?L=FCssing?= Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org, Florian Westphal , linux-kernel@vger.kernel.org, coreteam@netfilter.org, netfilter-devel@vger.kernel.org, Jozsef Kadlecsik , "David S . Miller" Subject: Re: [Bridge] [PATCH net] bridge: ebtables: fix reception of frames DNAT-ed to bridge device Message-ID: <20170321101121.GB1719@salvia> References: <20170315031811.22714-1-linus.luessing@c0d3.blue> <20170315102608.GB24366@breakpoint.cc> <20170315104211.GA24409@salvia> <20170315142720.GU15692@otheros> <20170315181539.GA31875@salvia> <20170315211619.GA3464@otheros> <20170315220605.GA1766@salvia> <20170317131044.GA11995@salvia> <20170319165506.GA15475@otheros> <20170321000947.GA31709@otheros> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170321000947.GA31709@otheros> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1767 Lines: 47 On Tue, Mar 21, 2017 at 01:09:47AM +0100, Linus L?ssing wrote: > On Sun, Mar 19, 2017 at 05:55:06PM +0100, Linus L?ssing wrote: > > On Fri, Mar 17, 2017 at 02:10:44PM +0100, Pablo Neira Ayuso wrote: > > > Wait. > > > > > > May this break local multicast listener that are bound to the bridge > > > interface? Assuming the bridge interface got an IP address, and that > > > there is local multicast listener. > > > > > > Missing anything here? > > > > Hm, for multicast packets usually the code path a few lines > > later in br_handle_frame_finish() should be taken instead. > > > > But you might be right for IP multicast packets with a unicast MAC > > destination (due to whatever reason, for instance via DNAT'ing > > again). > > > > Will check that - thanks! > > Ok, I tested DNAT'ing an IP multicast packet to the unicast MAC address > of the bridge interface. > > Both ping-ing to an IPv4 and IPv6 multicast listener on br0 worked > and was replied to fine, both with or without changing skb->pkt_type > from PACKET_MULTICAST to PACKET_HOST. > ("$ ping 224.1.0.123" and "$ ping6 ff02::1:ff40:707c%in0" from a > network namespace, tied into the bridge via veth) > > Also, a DNAT'ed PACKET_BROADCAST worked, with or without changing > it to PACKET_HOST. > > I also checked via tcpdump that the destination MAC was changed > successfully. Thanks for looking into this more in depth. > So, so far I wasn't able to find any bugs with the current > patch. But I think I like the idea of leaving the skb->pkt_type > unaltered for PACKET_MULTICAST and PACKET_BROADCAST, seems cleaner. Yes, and matching on skb->pkt_type would not break from netfilter. > I'd just add an "if (skb->pkt_type == PACKET_OTHERHOST)" check > then and resend a PATCH v2. Thanks.