From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Sat, 16 Jun 2012 02:56:00 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201206160256.01139.lindner_marek@yahoo.de> Subject: [B.A.T.M.A.N.] batman-adv 2012.2.0 released Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: b.a.t.m.a.n@lists.open-mesh.org Today, the B.A.T.M.A.N. team releases batman-adv 2012.2.0, packed with new= =20 features and improvements in various subsystems as well as the usual set of= =20 fixes and cleanups. As the kernel module always depends on the Linux kernel= it=20 was compiled against, it does not make sense to provide binaries on our=20 website. As usual, you will find the signed tarballs in our download sectio= n: http://downloads.open-mesh.org/batman/releases/batman-adv-2012.2.0/ as well as prepackaged binaries in your distribution. Important changes =2D---------------- This release comes with a completely rewritten bridge loop avoidance (also= =20 known as bridge loop avoidance II). The concept of the first bridge loop=20 avoidance was simple and worked well in small size LANs while larger networ= ks=20 suffered from the overhead. The new concept is very different and requires= =20 changes in your batman-adv configuration. If you were using the bridge loop= =20 avoidance you should consult our documentation before upgrading your=20 network(s). The default "per hop" penalty was increased to encourage batman-adv to take= =20 shorter routes. If you notice altered routing behavior and are unhappy with= =20 the result you should revisit the hop penalty configuration option. Thanks =2D----- Thanks to all people sending in patches: * Antonio Quartulli * Danny Kukawka * David S. Miller * Eric Dumazet * Linus Luessing * Marek Lindner * Simon Wunderlich * Sven Eckelmann * Xabier Rodriguez and to all those that supported us with good advice, code review and/or=20 rigorous testing: * Al Viro * David Laight * Jo-Philipp Wich * Martin Hundeb=F8ll batman-adv =2D--------- The new bridge loop avoidance certainly is the most prominent of the new=20 features this release has to offer (completely replacing the old bridge loo= p=20 avoidance mechanism). The major design goals were performance and scalabili= ty.=20 Since the old implementation was relying on a single gateway to be the mast= er=20 gateway to the LAN for everybody else it created a performance bottleneck.= =20 =46urthermore, the LAN was used to send traffic to and receive data from th= e=20 master gateway. With the number of bridged gateways grew the amount of=20 broadcast traffic in the LAN. The new bridge loop avoidance splits the clie= nt=20 responsibility amongst all participating gateways. Each gateway "claims" th= e=20 clients it feels responsible for and ignores the traffic from all other=20 clients to avoid the bridge loop. It also is able to handle multiple VLANs = on=20 top of the batX interface connected to different topologies. All details ab= out=20 the loop avoidance mechanism are explained in our documentation section. The routing code also received lots of attention: The recently added routin= g=20 protocol abstraction was further polished and extended to better accommodat= e=20 the needs of alternative routing protocols. B.A.T.M.A.N. IV protocol has be= en=20 enhanced with an additional flag to apply stricter forwarding rules to OGMs= =20 which allows the protocol to avert routing loops in certain corner cases.=20 Also, the B.A.T.M.A.N. IV sequence numbers are now randomized at startup to= =20 reduce the probability of a collision and thus, slowing down the protocol i= n=20 the startup phase. Rerouting of unicast payload packets during a roaming ph= ase=20 is handled with greater efficiency to avoid as much packet loss while roami= ng=20 as possible.=20 All manual HZ-jiffies-calculations have been replaced with the in-kernel=20 jiffies_to_msecs() function. To facilitate comprehension of the code base t= he=20 ETH_ALEN macro is used instead of hardcoded numeric constants. The batman-a= dv=20 internal bitarray operations have been converted to the efficient in-kernel= =20 bitmap operations. It was discovered that the TT-Request packet did not alw= ays=20 send the tt-crc field in network byte order, thereby invalidating the packe= t.=20 This has been fixed alongside the suboptimal DHCP option list parser used b= y=20 the gateway extension. OGM sequence numbers now are always printed as unsig= ned=20 long to avoid misinterpretation while printing the numbers in the debug log. batctl =2D----- The batctl utility supports the new bridge loop avoidance by providing an=20 option to conveniently enable/disable the bridge loop avoidance and exports= =20 the bridge loop avoidance claim table. It will also warn about features tha= t=20 haven't been compiled into batman-adv such as debug log and bridge loop=20 avoidance. The mini-tcpdump learned to display the newly added 'not best ho= p=20 flag' when parsing OGMs.=20 Happy routing,=20 The B.A.T.M.A.N. team