public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Ufo <ufo@rund.freifunk.net>
To: 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 10:36:00 +0100	[thread overview]
Message-ID: <56694780.2010902@rund.freifunk.net> (raw)
In-Reply-To: <2676271.FVut4a8TrS@sven-edge>

so who wants to do that? :-o
or maybe there are other purposes to keep the older version within 15-05 
brunch?

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
>>
>> 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) 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


  reply	other threads:[~2015-12-10  9:36 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 [this message]
2015-12-10 10:49     ` cmsv

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=56694780.2010902@rund.freifunk.net \
    --to=ufo@rund.freifunk.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