All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moritz Warning <moritzwarning@web.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [RFC] batman-adv boot setup scheme on OpenWRT
Date: Sun, 09 Dec 2012 12:10:56 +0100	[thread overview]
Message-ID: <50C471C0.2060407@web.de> (raw)
In-Reply-To: <CAHD-aqLUc7YAsmgOdGS2nxdU06U3KTbCAtjXHa4v_64fzHNhWg@mail.gmail.com>

I have tried batman-adv-netifd-proto-batadv.patch along with some Makefile adjustments to get it compile.
Afaict it works.

On 12/02/2012 02:19 PM, Gui Iribarren wrote:
> Really Sorry for the whitespace headaches :( hope to get it straight this time.
> 
> As we discussed on irc with Marek, here's a first stab at netifd integration.
> I'm surprised at how simple it actually is to add a custom "proto" with netifd
> 
> No race condition with this approach, at least on the hardware i have
> at hand (ubnt2 , and tplinks)
> 
> an example uci config scheme changes from
> 
> batman-adv.bat0=mesh
> batman-adv.bat0.interfaces='mesh0 mesh1 mesh2'
> batman-adv.bat0.bridge_loop_avoidance=1
> network.mesh{0,1,2}=interface
> network.mesh{0,1,2}.proto=none
> network.mesh{0,1,2}.mtu=1528
> wireless.@wifi-iface[]=wifi-iface
> wireless.@wifi-iface[].network=mesh{0,1,2}
> wireless.@wifi-iface[].mode=adhoc
> 
> to
> 
> batman-adv.bat0=mesh
> batman-adv.bat0.bridge_loop_avoidance=1
> network.mesh{0,1,2}=interface
> network.mesh{0,1,2}.proto=batadv
> network.mesh{0,1,2}.mesh=bat0
> network.mesh{0,1,2}.mtu=1528
> wireless.@wifi-iface[1]=wifi-iface
> wireless.@wifi-iface[1].network=mesh{0,1,2}
> wireless.@wifi-iface[1].mode=adhoc
> 
> So /etc/config/batman-adv now deals only with bat0 tweakable parameters,
> /etc/config/network defines interfaces to be added to bat0
> and /etc/config/wireless is unchanged
> 
> and netifd is responsible of avoiding race conditions
> of course, this makes batman-adv package (on openwrt) depend on
> netifd, but openwrt devs are pushing it that way (and it's finally
> looking like an elegant move after all ;) )
> 
> Cheers!
> 
> On Mon, Nov 26, 2012 at 7:45 AM, Sven Eckelmann <sven@narfation.org> wrote:
>> On Monday 26 November 2012 18:40:20 Marek Lindner wrote:
>>> On Friday, November 23, 2012 22:00:47 Gui Iribarren wrote:
>>>> Boring bootlog at http://pastebin.com/59FEPttY
>>>>
>>>> Proposed patch follows (against current batman-adv in openwrt 'packages'
>>>> feed)
>>>>
>>>> Signed-off-by: Gui Iribarren <gui@altermundi.net>
>>>
>>> I made the necessary changes myself after I successfully de-scrambled your
>>> patch. You will find the patch in OpenWrt trunk. Give it try!
>>> Next time, please configure your mail client to not wrap lines.
>>
>> http://lxr.linux.no/linux+v2.6.30/Documentation/email-clients.txt
>>
>> Kind regards,
>>         Sven


  reply	other threads:[~2012-12-09 11:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 12:52 [B.A.T.M.A.N.] [RFC] batman-adv boot setup scheme on OpenWRT Gui Iribarren
2012-11-23 14:00 ` Gui Iribarren
2012-11-26 10:40   ` Marek Lindner
2012-11-26 10:45     ` Sven Eckelmann
2012-12-02 13:19       ` Gui Iribarren
2012-12-09 11:10         ` Moritz Warning [this message]
2012-12-09 14:31           ` Marek Lindner
2012-12-09 16:03             ` Moritz Warning
2012-12-09 16:20               ` Antonio Quartulli
2012-12-09 16:35               ` Gui Iribarren
2012-12-10  0:13                 ` Jo-Philipp Wich
2012-12-09 16:50               ` Moritz Warning
2012-11-25 17:12 ` Marek Lindner

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=50C471C0.2060407@web.de \
    --to=moritzwarning@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.