Re: Issue with bridging LAN and mesh network

[Emilie Meyer <emiliemeyer1016@gmail.com>]

Hi Sven and thanks for your kindness helping me out.

I have spent some time trying a few of your suggestions. In my case
using the brctl commands was the easiest and most successful.
However, what I've learned so far is that using brctl and other CLI
commands according to

https://www.open-mesh.org/projects/batman-adv/wiki/Quick-start-guide

is not a persistent solution. 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.

I sincerely hope for your kind advice and guidance.

Kind regards

Emilie

On Sun, Feb 16, 2020 at 10:39 AM Sven Eckelmann <sven@narfation.org> wrote:
>
> 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



-- 
Regards

Emilie