[B.A.T.M.A.N.] Interested in contributing

[B.A.T.M.A.N.] Interested in contributing

[leftbydefault]

Hello folks,

I came across the list of improvements and ideas to work on 
B.A.T.M.A.N-Adv from Gsoc2013 Ideas here 
https://wiki.freifunk.net/Ideas_GSoC_2013
I am interested to work on implementing a proposed solution to any of 
the mentioned problem. The wiki has a list of problems but, there is no 
description about the current status of each problem listed (whether 
they have been already implemented or still looking for contributions?).

If there are any other problems apart from the above list, I would also 
like to know those to see if I can contribute.

Re: [B.A.T.M.A.N.] Interested in contributing

[Linus Lüssing]

On Mon, Sep 26, 2016 at 10:17:48PM +0530, leftbydefault@riseup.net wrote:
> Hello folks,
> 
> I came across the list of improvements and ideas to work on B.A.T.M.A.N-Adv
> from Gsoc2013 Ideas here https://wiki.freifunk.net/Ideas_GSoC_2013
> I am interested to work on implementing a proposed solution to any of the
> mentioned problem. The wiki has a list of problems but, there is no
> description about the current status of each problem listed (whether they
> have been already implemented or still looking for contributions?).
> 
> If there are any other problems apart from the above list, I would also like
> to know those to see if I can contribute.


Hi!

We had been discussing priorities at the last Wireless Battlemesh
and the top ones are currently:

1) Implementing aggregation for BATMAN V
   (or better, implement some routing algorithm independent
   aggregation)
2) Then the "Dead node fast path switching/invalidating" point
   (current codename: "RIP") to increase scalibility/responsiveness
   through such a reactive addition to the protocol


Regarding larger community mesh networks, it also seems that we
need some deeper evaluation and maybe improvements for DAT. At
least some statistics indicate that larger, open mesh networks
still have a non-negligable amount of broadcast traffic caused by
ARP.

Then there were also some discussions about some "Privacy
Extension" for clients, but there is no easy or even satisfying
concept yet.

I personally would love to improve the current multicast
optimizations to allow real multicast streaming, but we came to
the conclusion at WBM, that this is a "nice-to-have" for now until
1)+2) are done.


Of course, priorities depend on real use-cases, so other people
can probably throw in other ideas or preferences. Or, asking
you, what are the scenarios and use-cases you would like to
improve and feel motivated to work on :-)?

Regards, Linus

PS: Also something, if you might already have some experience with
kernel code, would be to simply help in reviewing pending patches.
Maybe not as exciting as contributing something new and fancy. But
it doesn't help to send patchsets for new features if too many, prior
patches are still pending. So reviewing actually helps a lot and
might contribute even more than submitting something new and fancy.

PPS: Great that you want to contribute! :-)

Re: [B.A.T.M.A.N.] Interested in contributing

[Sven Eckelmann]

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

On Dienstag, 27. September 2016 01:07:41 CEST Linus Lüssing wrote:
> PS: Also something, if you might already have some experience with
> kernel code, would be to simply help in reviewing pending patches.
> Maybe not as exciting as contributing something new and fancy. But
> it doesn't help to send patchsets for new features if too many, prior
> patches are still pending. So reviewing actually helps a lot and
> might contribute even more than submitting something new and fancy.

You can find the current pending patches at
 https://patchwork.open-mesh.org/project/b.a.t.m.a.n./list/

The correct way to announce your review is to submit comments inline as reply 
to the original mail (can be found in patchwork as mbox for each patch). If no 
problems could be found then please announce this also. The correct way to do 
it is described in https://www.kernel.org/doc/Documentation/SubmittingPatches 
under 13, 11 and 12.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [B.A.T.M.A.N.] Interested in contributing

[leftbydefault]

Hello again,

On 2016-09-27 04:37, Linus Lüssing wrote:
> Hi!
> 
> We had been discussing priorities at the last Wireless Battlemesh
> and the top ones are currently:
> 
> 1) Implementing aggregation for BATMAN V
>    (or better, implement some routing algorithm independent
>    aggregation)
> 2) Then the "Dead node fast path switching/invalidating" point
>    (current codename: "RIP") to increase scalibility/responsiveness
>    through such a reactive addition to the protocol

Both of these 2 problems seems interesting.

> 
> 
> Regarding larger community mesh networks, it also seems that we
> need some deeper evaluation and maybe improvements for DAT. At
> least some statistics indicate that larger, open mesh networks
> still have a non-negligable amount of broadcast traffic caused by
> ARP.
> 
> Then there were also some discussions about some "Privacy
> Extension" for clients, but there is no easy or even satisfying
> concept yet.
> 
> I personally would love to improve the current multicast
> optimizations to allow real multicast streaming, but we came to
> the conclusion at WBM, that this is a "nice-to-have" for now until
> 1)+2) are done.
> 
> 
> Of course, priorities depend on real use-cases, so other people
> can probably throw in other ideas or preferences. Or, asking
> you, what are the scenarios and use-cases you would like to
> improve and feel motivated to work on :-)?

I am currently undergoing a masters degree on Networks & Internet 
Engineering from India. Also we are actively trying to establish a 
wireless community Network in our place (https://pymeshnet.gitlab.io). 
We have done few exercises like flashing the router with OpenWRT 
firmware and installing batman-adv & batctl 2016 on it and have 
successfully meshed them both in range via ad-hoc mode.

I am particularly interested with b.a.t.m.a.n-adv as a routing protocol 
itself and so I am starting to understand the internals of this 
protocol. So consider myself as a beginner.

As a community volunteer, we wanted to deploy a wireless mesh routing 
protocol and as a academic student, I am interested in studying the 
protocol and trying to figure out limitations or issues with the 
protocol & identify a solution.

> Regards, Linus
> 
> PS: Also something, if you might already have some experience with
> kernel code, would be to simply help in reviewing pending patches.

I have very little experience trying to learn to write modules for linux 
kernel, nevertheless I can learn it.

> 
> PPS: Great that you want to contribute! :-)

Very glad to see b.a.t.m.a.n list is open to new comers like me. 
Currently, I am going through the wiki pages 
(https://www.open-mesh.org/projects/batman-adv/wiki/Wiki). I request you 
people to help me get clarified certain things, when I am in doubt. I 
will definitely pick up.