public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
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.] Automatically starting adaptors at boot
Date: Wed, 20 Nov 2013 16:38:58 +0100	[thread overview]
Message-ID: <20131120153858.GC311@neomailbox.net> (raw)
In-Reply-To: <CAAxzKbRaF_a5UZdZUUQXmgO_zEp=Fe2_AdTAfSOKrTX=rFpq2A@mail.gmail.com>

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

On Tue, Nov 19, 2013 at 01:36:16PM +1000, tjhowse wrote:
> Hello Ladies and Gentlemen,
> 
> This might be a question better suited to the OpenWRT list, but I
> figure it would've been solved better here.
> 
> I've got a two-node mesh set up and working well. Config files are
> below. I have some minor woes though. Each time one of the nodes boots
> up I must:
> 
> brctl addif br-lan bat0
> ifconfig bat0 up
> 
> ...before traffic starts to flow between clients connected to the
> wlan0 radios of each node. What's the best way of having this happen
> automatically? I assume there's a better way than having an init
> script run those commands at boot.

This is totally related to openwrt and unrelated to batman-adv.

If I remember correctly you can directly configure the lan "interface" in
the /etc/config/network file. You should be allowed to specify more than one
ifname (in the same option line).

The openwrt channel/documentation can probably be more helpful.


Cheers,

-- 
Antonio Quartulli

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-11-20 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  3:36 [B.A.T.M.A.N.] Automatically starting adaptors at boot tjhowse
2013-11-20 15:38 ` Antonio Quartulli [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=20131120153858.GC311@neomailbox.net \
    --to=antonio@meshcoding.com \
    --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