From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 9 Sep 2020 22:14:24 +0200 From: Linus =?utf-8?Q?L=C3=BCssing?= Subject: Re: [PATCH maint v2 3/4] batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh Message-ID: <20200909201424.GE2391@otheros> References: <20200904182803.8428-1-linus.luessing@c0d3.blue> <20200904182803.8428-4-linus.luessing@c0d3.blue> <2973088.WcO1NEu1zB@prime> <20200909145357.GB2391@otheros> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200909145357.GB2391@otheros> Content-Transfer-Encoding: quoted-printable Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: To: The list for a Better Approach To Mobile Ad-hoc Networking On Wed, Sep 09, 2020 at 04:53:57PM +0200, Linus L=C3=BCssing wrote: > So the only solution I could think of for now is > excluding DHCPv6 from multicast feature in TX of the originator... > (in batadv_mcast_forw_mode_check_ipv6(), adding excludes for > ff02::1:2 and ff05::1:3). Ah, wait, we could distinguish them. Just noticed that the gateway feature uses a unicast 4 address header, while the multicast feature uses a simple, 3 address unicast header. That should work. But might look a bit hacky. And would disallow using a 4 address header from the multicast feature in the future.