From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: In-Reply-To: <1549090.s6anOn0kWk@voltaire> References: <23381002.yeogTpj88W@voltaire> <1549090.s6anOn0kWk@voltaire> MIME-Version: 1.0 From: Andreas Pape Message-ID: Date: Thu, 19 Feb 2015 09:31:08 +0100 Content-Type: text/plain; charset="US-ASCII" Subject: Re: [B.A.T.M.A.N.] Antwort: Re: Antwort: Antwort: Re: Antwort: Re: Question concerning batman-adv bug #173 "Mesh packets on bat0" 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-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking Hi Marek, the problem seems to be a little bit more complex. Your latest patch does not solve the problem. But I found out, that commenting out the following line in your patch makes bat0 work: slave->master = master; But as this is the core of "enslaving" a device to a master device, this breaks the complete concept behind this I guess (I'm not a skilled kernel developer). From this I conclude that there might be a bug somewhere deeper in the kernel version I use. I don't want to give up too early, but it looks a little bit as if this "enslaving concept using rtnl" might not be usable in these older kernels. What do you think? Regards, Andreas