public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.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: Any suggestions about configuring batman-adv gateways + modems
Date: Sat, 09 Nov 2019 21:50:57 +0800	[thread overview]
Message-ID: <17293366.m7Fd2njPPT@rousseau> (raw)
In-Reply-To: <4aaa0e89-d428-a7c9-ef47-67dfef8e1411@gmail.com>

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

Hi,

On Friday, 8 November 2019 18:51:14 HKT Xuebing Wang wrote:
> We have been building openwrt 15.05 + batman-adv mesh network for over 2
> years, they work great.

hopefully, the batman-adv version you are using is newer than 15.05 ...


> 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).

Why not ? What should prevent nodes or clients to choose another batman-adv 
gateway ?


> 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.

Can you elaborate ? Are you comparing bridging vs routing ? What's the main 
difference between 1.1 and 2. which makes you think it works better ?


> 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?

You can always ping or transfer any IPv4/IPv6 payload over batman-adv 
regardless of your WAN setup. In fact, you could operate batman-adv without 
any WAN uplink at all.

Cheers,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-11-09 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 10:51 Any suggestions about configuring batman-adv gateways + modems Xuebing Wang
2019-11-09 13:50 ` Marek Lindner [this message]
     [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=17293366.m7Fd2njPPT@rousseau \
    --to=mareklindner@neomailbox.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