public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Emilie Meyer <emiliemeyer1016@gmail.com>
Subject: Re: Issue with bridging LAN and mesh network
Date: Sun, 16 Feb 2020 19:39:33 +0100	[thread overview]
Message-ID: <1873965.jgP86xNRV2@sven-edge> (raw)
In-Reply-To: <CAFF9uhp7M94yAPhWnpUkBwLzQa8rgxMGdBYU2CNQ203QtJZs9g@mail.gmail.com>

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

On Sunday, 16 February 2020 19:20:41 CET Emilie Meyer wrote:
[...]
> root@OpenWrt:~# ip link set eth0 master mesh-bridge
> ip: either "dev" is duplicate, or "master" is garbage
[...]
> OpenWrt 18.06.4, r7808-ef686b7292
[...]

The problem here is that the networking/libiproute/iplink.c from busybox in 
OpenWrt 18.04.x has the code for the "master" interface configuration 
disabled. You have various options:

* switch to the current release OpenWrt 19.07
* switch from busybox's iplink applet to the package ip-full
* use netifd to configure the interfaces [1]
* use brctl to configure the bridge slave interfaces

     brctl addif mesh-bridge eth0

Kind regards,
	Sven

[1] https://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config#Batman-adv-201300-till-20190-2

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

  reply	other threads:[~2020-02-16 18:39 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 [this message]
2020-02-21 22:41   ` Emilie Meyer
2020-02-22  7:18     ` Sven Eckelmann

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=1873965.jgP86xNRV2@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