From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 31 May 2017 17:56:31 +0200 From: Linus =?utf-8?Q?L=C3=BCssing?= Message-ID: <20170531155631.GG29826@otheros> References: <13855542.45yYzsjnKj@prime> <20170531142013.GD29826@otheros> <8268015.CIqWAenRvX@prime> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <8268015.CIqWAenRvX@prime> Subject: Re: [B.A.T.M.A.N.] MAC addresses of loop detect frames in global translation-table List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking On Wed, May 31, 2017 at 04:40:56PM +0200, Simon Wunderlich wrote: > we actually want those frames to pass through the mesh - otherwise we can't > find out if "regular" packets would loop through the mesh, so we have handle > those special packets like regular ones. Ah, okay, thanks for the clarification! :) > If we don't want to see them, we have to hide them, but we can't remove the > packet without hurting the functionality. :) Yes, then filtering in batadv_tt_global_add() makes sense. Although, sending these mesh wide sounds like it could create quite some overhead? Is this new to BLA2? Regards, Linus