Re: [B.A.T.M.A.N.] Antwort: Re: Antwort: Antwort: Re: Antwort: Re: Question concerning batman-adv bug #173 "Mesh packets on bat0"

2015-02-19 Thread Marek Lindner
On Thursday, February 19, 2015 09:31:08 Andreas Pape wrote: > 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 i

Re: [B.A.T.M.A.N.] Antwort: Re: Antwort: Antwort: Re: Antwort: Re: Question concerning batman-adv bug #173 "Mesh packets on bat0"

2015-02-19 Thread Andreas Pape
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 b

Re: [B.A.T.M.A.N.] Antwort: Re: Antwort: Antwort: Re: Antwort: Re: Question concerning batman-adv bug #173 "Mesh packets on bat0"

2015-02-18 Thread Marek Lindner
On Wednesday, February 18, 2015 17:10:12 Andreas Pape wrote: > The essential call is in patch 2 as assumed. As soon as I add the > netdev_master_upper_dev_link call again to the compilable code, the > problem starts to occur (mesh doesn't work as soon as bat0 is added to the > bridge, ogm packets c

[B.A.T.M.A.N.] Antwort: Re: Antwort: Antwort: Re: Antwort: Re: Question concerning batman-adv bug #173 "Mesh packets on bat0"

2015-02-18 Thread Andreas Pape
Hi Marek, I reverted the changes step by step starting with patch 0002-remove-netdev_calls.patch, as patch 1 did not help and patch 3 containes in compat.h and soft-interface.c, I tried out myself earlier today. The essential call is in patch 2 as assumed. As soon as I add the netdev_master_u