Hi,
Are recent batman-acv versions unusable with 3.10 or 3.8 kernels?
The reason i'm asking is that with 2104.1.0 with two connected sta after restarting the wifi (also the same if restarting all the network) it gives the following message:
root@Laguna1:/etc/config# wifi [37620.920000] batman_adv: bat0: Interface deactivated: adhoc0 [37621.140000] batman_adv: bat0: Removing interface: adhoc0 [37621.250000] br-mesh: port 2(bat0) entered disabled state [37621.250000] device bat0 left promiscuous mode [37621.260000] br-mesh: port 2(bat0) entered disabled state [37631.340000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 [37641.390000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 [37651.410000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 …
And only restarting is possible to get the device back to work.
Going back to 2014.0.0 it's worst with the system being very unstable and continuously restarting.
After following the instructions from cmsv cmsv@wirelesspt.net and replacing the feeds.conf with src-git routing https://github.com/libre-mesh/openwrt-routing-packages
I was able to compile the 2013.4.0 release which is very stable.
But I really would like the vlan support from recent releases.
My systems are: Laguna board OpenWrt trunk r38938 batctl 2013.4.0 [batman-adv: 2013.4.0] Linux Laguna1 3.8.13 #6 SMP Thu Mar 27 16:10:18 WET 2014 armv6l GNU/Linux
Router station OpenWrt trunk r38938 batctl 2013.4.0 [batman-adv: 2013.4.0] Linux RSPro2 3.10.18 #2 Thu Mar 27 18:24:29 WET 2014 mips GNU/Linux
Thanks in advance, Bruno
On Monday 31 March 2014 12:23:52 Bruno Antunes wrote:
root@Laguna1:/etc/config# wifi [37620.920000] batman_adv: bat0: Interface deactivated: adhoc0 [37621.140000] batman_adv: bat0: Removing interface: adhoc0 [37621.250000] br-mesh: port 2(bat0) entered disabled state [37621.250000] device bat0 left promiscuous mode [37621.260000] br-mesh: port 2(bat0) entered disabled state [37631.340000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 [37641.390000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 [37651.410000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1
This is a known 2014.1.0 regression which recently has been fixed. You can either update your openwrt package to fetch these fixes or extract the patches from our batman-adv git repository or wait for the next release.
And only restarting is possible to get the device back to work.
Going back to 2014.0.0 it's worst with the system being very unstable and continuously restarting.
After following the instructions from cmsv cmsv@wirelesspt.net and replacing the feeds.conf with src-git routing https://github.com/libre-mesh/openwrt-routing-packages
Note that this is not the official openwrt-routing repository but a fork maintained by 'people on the internet'. If you do experience problems with the code coming from this repository, please contact the people maintaining this fork.
Cheers, Marek
Inline:
On 03/31/2014 09:02 AM, Marek Lindner wrote:
On Monday 31 March 2014 12:23:52 Bruno Antunes wrote:
root@Laguna1:/etc/config# wifi [37620.920000] batman_adv: bat0: Interface deactivated: adhoc0 [37621.140000] batman_adv: bat0: Removing interface: adhoc0 [37621.250000] br-mesh: port 2(bat0) entered disabled state [37621.250000] device bat0 left promiscuous mode [37621.260000] br-mesh: port 2(bat0) entered disabled state [37631.340000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 [37641.390000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 [37651.410000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1
This is a known 2014.1.0 regression which recently has been fixed. You can either update your openwrt package to fetch these fixes or extract the patches from our batman-adv git repository or wait for the next release.
And only restarting is possible to get the device back to work.
Going back to 2014.0.0 it's worst with the system being very unstable and continuously restarting.
After following the instructions from cmsv cmsv@wirelesspt.net and replacing the feeds.conf with src-git routing https://github.com/libre-mesh/openwrt-routing-packages
Note that this is not the official openwrt-routing repository but a fork maintained by 'people on the internet'. If you do experience problems with the code coming from this repository, please contact the people maintaining this fork.
As far as i know; it is a clone of the batman-adv 2013.* without any modification. Perhaps the maintainer could shed some light into this subject. https://github.com/libre-mesh/openwrt-routing-packages/tree/master/batman-ad... I have it fully working without any problems as a clone of batman-adv 2013.* without any modifications from "people on the internet".
There are also other ways to use the current official openwrt-routing-packages repository and selecting only the 2013.* releases.
Cheers, Marek
On 03/31/2014 09:25 PM, cmsv wrote:
After following the instructions from cmsv cmsv@wirelesspt.net and replacing the feeds.conf with src-git routing https://github.com/libre-mesh/openwrt-routing-packages
Note that this is not the official openwrt-routing repository but a fork maintained by 'people on the internet'. If you do experience problems with the code coming from this repository, please contact the people maintaining this fork.
As far as i know; it is a clone of the batman-adv 2013.* without any modification. Perhaps the maintainer could shed some light into this subject.
Indeed, currently it's just a "snapshot" of the official openwrt-routing/packages as it was back in december.
I guess cmsv suggested Bruno to use this as an easy way to get 2013.4.0 source code, instead of properly checking out an older version of the official repo
something like
$ cd feeds/routing $ git log batman-adv # find your favorite old version $ git checkout e2cfab7f287673b1d6854c59db6e710668d145f3
https://github.com/libre-mesh/openwrt-routing-packages/tree/master/batman-ad... I have it fully working without any problems as a clone of batman-adv 2013.* without any modifications from "people on the internet".
As long as those people on the internet don't decide is time to move "master" further on, and break your tree on your next git pull :)
There are also other ways to use the current official openwrt-routing-packages repository and selecting only the 2013.* releases.
Indeed, and you should do so,
maybe even add your own frozen fork to the list, https://github.com/openwrt-routing/packages/network and be surprised when another random folk starts using it? yay! :P
cheerfully,
gui
Cheers, Marek
* Gui Iribarren gui@altermundi.net [01.04.2014 10:08]:
something like
$ cd feeds/routing $ git log batman-adv # find your favorite old version $ git checkout e2cfab7f287673b1d6854c59db6e710668d145f3
IMHO this does not work, because 'scripts/feeds' throws away the history ("git clone --depth 1").
bye, bastian
Hi,
On 31 Mar, 2014, at 14:02 , Marek Lindner mareklindner@neomailbox.ch wrote:
On Monday 31 March 2014 12:23:52 Bruno Antunes wrote:
root@Laguna1:/etc/config# wifi [37620.920000] batman_adv: bat0: Interface deactivated: adhoc0 [37621.140000] batman_adv: bat0: Removing interface: adhoc0 [37621.250000] br-mesh: port 2(bat0) entered disabled state [37621.250000] device bat0 left promiscuous mode [37621.260000] br-mesh: port 2(bat0) entered disabled state [37631.340000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 [37641.390000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1 [37651.410000] unregister_netdevice: waiting for adhoc0 to become free. Usage count = 1
This is a known 2014.1.0 regression which recently has been fixed. You can either update your openwrt package to fetch these fixes or extract the patches from our batman-adv git repository or wait for the next release.
Compiled with the latest update (31 Mar) and up until now it's working fine on both devices.
And only restarting is possible to get the device back to work.
Going back to 2014.0.0 it's worst with the system being very unstable and continuously restarting.
After following the instructions from cmsv cmsv@wirelesspt.net and replacing the feeds.conf with src-git routing https://github.com/libre-mesh/openwrt-routing-packages
Note that this is not the official openwrt-routing repository but a fork maintained by 'people on the internet'. If you do experience problems with the code coming from this repository, please contact the people maintaining this fork.
Didn't found any problems with this fork.
But has Gui commented I could have used the official repository to compile previous versions. We are always learning...
Thanks, Bruno
Cheers, Marek
On Tuesday 01 April 2014 11:01:16 Bruno Antunes wrote:
This is a known 2014.1.0 regression which recently has been fixed. You can either update your openwrt package to fetch these fixes or extract the patches from our batman-adv git repository or wait for the next release.
Compiled with the latest update (31 Mar) and up until now it's working fine on both devices.
Great!
Note that this is not the official openwrt-routing repository but a fork maintained by 'people on the internet'. If you do experience problems with the code coming from this repository, please contact the people maintaining this fork.
Didn't found any problems with this fork.
I did not mean to imply using some other repository is necessarily a bad thing. Just keep in mind to bother the right people _in case_ something goes awry.
Cheers, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
Bastian Bittorf -
Bruno Antunes -
cmsv -
Gui Iribarren -
Marek Lindner