From: Sven Eckelmann <sven@narfation.org>
To: Emilie Meyer <emiliemeyer1016@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: Issue with bridging LAN and mesh network
Date: Sat, 22 Feb 2020 08:18:09 +0100 [thread overview]
Message-ID: <121721768.aRRP5j3uff@sven-edge> (raw)
In-Reply-To: <CAFF9uhqaC0HOhiYxVaHAvU++enbO2STjupsoCiNauaeRTynu8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
On Friday, 21 February 2020 23:41:28 CET Emilie Meyer wrote:
[...]
> Each time the router is restarted, all
> previous configurations are lost.
> I guess one way to solve this is by using UCI configurations, but I am
> not certain how to translate all the steps above to UCI.
You should read first some instructions how to configure the wireless and
wired components in OpenWrt. And when you understood this, continue with the
instructions how to configure batman-adv on top of this.
* OpenWrt network configuration
- https://openwrt.org/docs/guide-user/base-system/uci
- https://openwrt.org/docs/guide-user/base-system/basic-networking
- https://openwrt.org/docs/guide-user/network/wifi/basic
- https://openwrt.org/docs/guide-user/network/wifi/bridgedap
- https://openwrt.org/docs/guide-user/network/wifi/dumbap
- https://forum.openwrt.org/
* batman-adv:
- on OpenWrt 18.06:
https://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config#Batman-adv-201300-till-20190-2
- on OpenWrt 19.07:
https://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config#Batman-adv-20190-3-and-newer
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-02-22 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 18:20 Issue with bridging LAN and mesh network Emilie Meyer
2020-02-16 18:39 ` Sven Eckelmann
2020-02-21 22:41 ` Emilie Meyer
2020-02-22 7:18 ` Sven Eckelmann [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=121721768.aRRP5j3uff@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=emiliemeyer1016@gmail.com \
/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