public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
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.] [B.A.T.M.A.N] simulate multihop
Date: Thu, 7 Apr 2016 01:58:08 +0200	[thread overview]
Message-ID: <20160406235808.GH19409@lunn.ch> (raw)
In-Reply-To: <CAAz6EDdLudcU10Uc2=u8_8zgvCuLMRoYHd3+kf77Q5_gzTkuVw@mail.gmail.com>

> Anyone have another solution or i am doing something wrong? I think
> that ebtables does not work because my interface (wireless) is not on
> bridge mode, i cannot set it for bridge mode because i need create a
> mesh network (the wireless interface have to be in ad hoc mode).

If you look on the list, there are patches to make BATMAN network
namespace aware. You can then put the instances in different
namespaces, and use veth's to connect them together in the topology
you want.

    Andrew

      reply	other threads:[~2016-04-06 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 23:47 [B.A.T.M.A.N.] [B.A.T.M.A.N] simulate multihop Fábio Carvalho
2016-04-06 23:58 ` Andrew Lunn [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=20160406235808.GH19409@lunn.ch \
    --to=andrew@lunn.ch \
    --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