Hi,
I want to test the Bridge loop avoidance II with our OpenWrt Freifunk firmware. Is there a version that works and can be tested? Which git repo do I have to use and what are the main steps to compile it into openwrt?
Regards Clemens
On Sunday 25 December 2011 22:36:18 Clemens John wrote:
Hi,
I want to test the Bridge loop avoidance II with our OpenWrt Freifunk firmware. Is there a version that works and can be tested? Which git repo do I have to use and what are the main steps to compile it into openwrt?
Simon Wunderlich is the maintainer of the bridge loop avoidance II patchset. His current version can be found in his repo [1] in branch blaII (or another branch with blaII in the name). It is currently not rebased on top of master or v2011.4.0... so you cannot take the patchset and put it in OpenWRT.
A quick and easy way would be to clone the repo, make a diff using `git diff v2011.4.0..origin/blaII > blaII.patch` and place the resulting patch in the patches directory [2]. Keep in mind that this patch removes some changes that were added before the release of 2011.4.0 and adds some other ones which were already applied in master. His next-blaII branch is also a little bit newer (includes some fixes for smaller problems) and could be a better starting point.
You can find the patches merged after the release of v2011.4.0 and not part of the blaII patchset using:
git log --no-merges '^v2011.4.0' 8dd0e9973429c80f52483e8045862f61a74b6fd6
I am sorry that I cannot give a perfect answer right now.
Kind regards, Sven
[1] http://git.open-mesh.org/?p=simon/batman-adv.git;a=summary [2] https://dev.openwrt.org/browser/packages/net/batman-adv/patches
On Sonntag, 25. Dezember 2011 23:29:42 you wrote:
On Sunday 25 December 2011 22:36:18 Clemens John wrote:
Hi,
I want to test the Bridge loop avoidance II with our OpenWrt Freifunk firmware. Is there a version that works and can be tested? Which git repo do I have to use and what are the main steps to compile it into openwrt?
Simon Wunderlich is the maintainer of the bridge loop avoidance II patchset. His current version can be found in his repo [1] in branch blaII (or another branch with blaII in the name). It is currently not rebased on top of master or v2011.4.0... so you cannot take the patchset and put it in OpenWRT.
Simon commited another patchset today so I took the latest snapshot of his blaII_rebase branch [1] and put it on our own server [2]. I changed the name of the folder inside the snapshot to 2011.4.0 and the md5sum and the url to download the source in the OpenWrt Makefile [3]. For batctl I used the latest 2011.4.0 release and copied it to our server. But when I try to compile OpenWrt, I get the following error: http://pastebin.com/PcNH15EC
Anything I can do?
[1] http://git.open-mesh.org/?p=simon/batman- adv.git;a=snapshot;h=ebdc92a614b3de8a32c66c92a46df286afe4bf6a;sf=tgz [2] http://dev.freifunk-ol.de/batman-adv-2011.4.0.tar.gz [3] http://trac.freifunk- ol.de/browser/firmware/Trunk/build_patches/bla2/Makefile
Sry for this questions but I´m absolutely not very familar with this things so I need your help to test it.
Regards Clemens
On Dienstag, 27. Dezember 2011 23:06:36 Clemens John wrote:
Simon commited another patchset today so I took the latest snapshot of his blaII_rebase branch [1] and put it on our own server [2]. I changed the name of the folder inside the snapshot to 2011.4.0 and the md5sum and the url to download the source in the OpenWrt Makefile [3]. For batctl I used the latest 2011.4.0 release and copied it to our server. But when I try to compile OpenWrt, I get the following error: http://pastebin.com/PcNH15EC
Ok I created a patch from this version now and put it into the patches folder. This worked. So forget about the last mail.
What´s about the make option to enable bla2? How does this need to be applied to the makefile in openwrt or is there no need to change anything because the option in in batman advanced own makefile is set to y?
Regards Clemens
On Tuesday 27 December 2011 23:27:51 Clemens John wrote:
On Dienstag, 27. Dezember 2011 23:06:36 Clemens John wrote:
Simon commited another patchset today so I took the latest snapshot of his blaII_rebase branch [1] and put it on our own server [2]. I changed the name of the folder inside the snapshot to 2011.4.0 and the md5sum and the url to download the source in the OpenWrt Makefile [3]. For batctl I used the latest 2011.4.0 release and copied it to our server. But when I try to compile OpenWrt, I get the following error: http://pastebin.com/PcNH15EC
Ok I created a patch from this version now and put it into the patches folder. This worked. So forget about the last mail.
What´s about the make option to enable bla2? How does this need to be applied to the makefile in openwrt or is there no need to change anything because the option in in batman advanced own makefile is set to y?
Sry for the delay, but we were busy rebasing and fixing the blaII code. There are also some other meetings we are currently attending.
But to make it short: The code is automatically built (you correctly saw the CONFIG_BATMAN_ADV_BLA=y), but you have to enable it through the new sysfs file "bridge_loop_avoidance" or the batctl option.
Kind regards, Sven
Hi,
Am Sonntag, 25. Dezember 2011, 23:29:42 schrieb Sven Eckelmann:
On Sunday 25 December 2011 22:36:18 Clemens John wrote:
Hi,
I want to test the Bridge loop avoidance II with our OpenWrt Freifunk firmware. Is there a version that works and can be tested? Which git repo do I have to use and what are the main steps to compile it into openwrt?
Simon Wunderlich is the maintainer of the bridge loop avoidance II patchset. His current version can be found in his repo [1] in branch blaII (or another branch with blaII in the name). It is currently not rebased on top of master or v2011.4.0... so you cannot take the patchset and put it in OpenWRT.
We used the rebased version and got the module compiled (yeah! ;).
I enabled blaII on one node, and after that all nodes connected to the vpn went unreachable. Most of them use 2011.0.0, some others 2011.4.0, running an ad-hoc iface as bat-adv-iface and bat0, tap0 and ath0(master, for clients) as a bridge. Do the blaII-packets "kill" all the other nodes? I thought the blaII-packets would have no effect on the other nodes because of the compat- layer.
regards Bjoern
[...]
I enabled blaII on one node, and after that all nodes connected to the vpn went unreachable. Most of them use 2011.0.0, some others 2011.4.0, running an ad-hoc iface as bat-adv-iface and bat0, tap0 and ath0(master, for clients) as a bridge. Do the blaII-packets "kill" all the other nodes? I thought the blaII-packets would have no effect on the other nodes because of the compat- layer.
You should use the same version everywhere. The compat layer is only to get a version running on an older kernel... not for incompatibilities between the different features/versions of batman-adv.
Marek already suggested that the packet format version should be increased to clearly state that these versions are not compatible. But it could also be that you triggered a bug in the new bla implementation... still I don't understand why you are doing this. Which node should detect the ARP packets? Maybe you can explain it again to better understand your network architecture.
Thanks, Sven
On Tuesday, January 03, 2012 07:10:02 Sven Eckelmann wrote:
Marek already suggested that the packet format version should be increased to clearly state that these versions are not compatible. But it could also be that you triggered a bug in the new bla implementation... still I don't understand why you are doing this. Which node should detect the ARP packets? Maybe you can explain it again to better understand your network architecture.
Before you update all your nodes to the same version it would be really helpful to find out if there is an incompatibility between the old BLA and the new BLA. We are not 100% sure about that.
By the way, looking at our compatibility number table (http://www.open- mesh.org/wiki/batman-adv/Compatversion) I see that 2011.0.0 has compat 12 whereas 2011.4.0 has compat number 14. That could be the reason why your setup is not working.
Cheers, Marek
b.a.t.m.a.n@lists.open-mesh.org