From: cmsv <cmsv@wirelesspt.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] old batman-adv within 15.05 brunch?
Date: Thu, 10 Dec 2015 05:49:41 -0500 [thread overview]
Message-ID: <566958C5.8010206@wirelesspt.net> (raw)
In-Reply-To: <56694780.2010902@rund.freifunk.net>
On 12/10/2015 04:36 AM, Ufo wrote:
> so who wants to do that? :-o
> or maybe there are other purposes to keep the older version within 15-05
> brunch?
Maybe's in the land of 1's and 0's don't make sense.
>
> On 01.08.2015 20:27, Sven Eckelmann wrote:
>> On Saturday 01 August 2015 18:05:36 Ufo wrote:
>>> is there a reason for staying with batman-adv 2014 for openwrt 15.05?
>>>
>>> our current freifunk leipzig running batman-adv 2015.0 and it seems
>>> to work
I am building CC r47678 with batctl 2015.1 [batman-adv: 2015.1] and so
far testing it with 2 routers and no problems at all.
If anyone has some feedback in regards why we should not give it a go to
2015, let us know
>>>
>>> https://github.com/openwrt-routing/packages/tree/master/batman-adv
>>>
>>> vs.
>>>
>>> https://github.com/openwrt-routing/packages/tree/for-15.05/batman-adv
>> I would even say that it should switch to 2015.1 (not yet released)
Make your own local repo and feed and you are ready to build.
>> because it
>> fixes some nasty problems:
>>
>> batman-adv 2015.1
>>
>> * support latest kernels (2.6.29 - 4.2)
>> * cleanup of coding style
>> * cleanup of the compatibility layer
>> * convert to the Linux source directory structure
>> * adjust default configuration
>> - disable network coding
>> - enable bridge loop avoidance
>> * bugs squashed:
>> - avoid DAT to mess up local LAN state
>> - fix race conditions in DAT/NC/TT/MCAST TVLV handlers
>> - fix build system POSIX compatibility
>> - fix gateway selection in fast connection (1) gw_mode
>> - fix initialization of detected gateway
>> - fix race conditions in the translation table
>> - fix kernel crash due to missing NULL checks in vlan handlers
>> - fix potentially broken header access by multicast optimization
>> - fix broadcast packets cleanup for purged outgoing interface
>>
>> -- XXX, XX Aug 2015 XX:XX:XX +0200
>>
>> batman-adv 2015.0
>>
>> * support latest kernels (2.6.29 - 4.1)
>> * cleanup of coding style and add kerneldoc
>> * bugs squashed:
>> - fix incorrect lockdep warning in network coding
>> - fix condition when bonding should be used
>> - fix support of bridged batman-adv devices with kernel < 2.6.39
>>
>> -- Tue, 28 Apr 2015 20:20:02 +0200
>
>
prev parent reply other threads:[~2015-12-10 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 16:05 [B.A.T.M.A.N.] old batman-adv within 15.05 brunch? Ufo
2015-08-01 18:27 ` Sven Eckelmann
2015-12-10 9:36 ` Ufo
2015-12-10 10:49 ` cmsv [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566958C5.8010206@wirelesspt.net \
--to=cmsv@wirelesspt.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox