public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: wayne <plettpc@gmail.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.] batman-adv vis_data
Date: Fri, 22 Apr 2011 14:53:07 +0200	[thread overview]
Message-ID: <4DB17A33.8080002@gmail.com> (raw)
In-Reply-To: <BANLkTinqqA5AR8pjU0PSyKJxUqZsRaQdZw@mail.gmail.com>

On 21/04/2011 19:47, Gioacchino Mazzurco wrote:
>> you didn't add
>> your bridge interface to batman, did you?
>
> Yes on Marek suggestion i done
> batctl if add br-clients
>
> instead of
> batctl if add eth0
>
> br-clients = bat0 + eth0 [ + ath0 eventually ]
>

Hi All

Firstly I want to thank all the devs here for the excellent work! I have 
recently upgraded all my Nodes here in Rural S.Africa as per VT project 
to B-ADV and it just works.

To Reply on setup question.

here is mine!
interfaces: eth0, wifi0( ath0,ath1)  UBNT unit.

root@MP-20:/etc/config# brctl show
bridge name	bridge id		STP enabled	interfaces
br-lan		8000.00094557a8e5	yes		eth0
							bat0
							ath1

root@MP-20:/etc/config# batctl if
ath0: active

As bat0 is already bridged with the other interfaces, it's only required 
to run Bat-adv on the mesh interface i.e ath0.
VAP: ath1 is used as a AP also link-local,with pppoe server all 
clients,node bridge ip's all static.

Wayne A






      reply	other threads:[~2011-04-22 12:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19  7:39 [B.A.T.M.A.N.] batman-adv vis_data Gioacchino Mazzurco
2011-04-19  7:46 ` Gioacchino Mazzurco
2011-04-19 13:29   ` Linus Lüssing
2011-04-19 17:44     ` Gioacchino Mazzurco
2011-04-20 22:45       ` Gioacchino Mazzurco
2011-04-21 17:43         ` Linus Lüssing
2011-04-21 17:47           ` Gioacchino Mazzurco
2011-04-22 12:53             ` wayne [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=4DB17A33.8080002@gmail.com \
    --to=plettpc@gmail.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