public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Xuebing Wang <xbing6@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.org,
	Simon Wunderlich <sw@simonwunderlich.de>,
	Sven Eckelmann <sven@narfation.org>
Subject: Any suggestions about configuring batman-adv gateways + modems
Date: Fri, 8 Nov 2019 18:51:14 +0800	[thread overview]
Message-ID: <4aaa0e89-d428-a7c9-ef47-67dfef8e1411@gmail.com> (raw)

Hi batman-adv community,

We have been building openwrt 15.05 + batman-adv mesh network for over 2 
years, they work great.

We are planning to use batman-adv gateways + 4G modems. For an example: 
our mesh network is with 20 nodes, 3 nodes have 4G modems connected.

1) My first thought is to use batman-adv gateway (with 4G modem 
connected) as dhcp server, and forward batman-adv interface to wan 
interface (modem).
1.1)  But, there is an issue with this setup. Once a modem is down, 
nodes that are connected to this batman-adv gateway (with modem) can not 
automatically "roam" to another batman-adv gateway (with good modem 
connection).
1.2)  This behavior is expected, right?

2) My second thought is to bridge batman-adv interface and wan interface 
(modem). This works great, I do not see issue (1.1) above.
-  By this setup, all batman-adv clients get ip via dhcp and via modem.
2.1)  Is this the suggested setup to use batman-adv gateways?

3) When I bridge batman-adv interface with other interface (as in step 2 
above), can I use batman-adv interface via *ipv6* to ping other 
batman-adv nodes?

Thanks.
Xuebing Wang


             reply	other threads:[~2019-11-08 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 10:51 Xuebing Wang [this message]
2019-11-09 13:50 ` Any suggestions about configuring batman-adv gateways + modems Marek Lindner
     [not found] <CAG5qQ7jY2YqyUdx6=Mw=OWbLF0avwibJVQn5YHFqGC-+nPCkXQ@mail.gmail.com>
2019-11-11  0:46 ` Marek Lindner
  -- strict thread matches above, loose matches on Subject: below --
2019-11-11  0:52 Xuebing Wang
2019-11-11  1:32 Xuebing Wang
2019-11-11  1:37 ` 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=4aaa0e89-d428-a7c9-ef47-67dfef8e1411@gmail.com \
    --to=xbing6@gmail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    /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