Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DSA config: bat0 does not get into the bridge #958

Closed
ilario opened this issue Dec 10, 2022 · 1 comment
Closed

DSA config: bat0 does not get into the bridge #958

ilario opened this issue Dec 10, 2022 · 1 comment
Milestone

Comments

@ilario
Copy link
Member

ilario commented Dec 10, 2022

In the mailing list, Gothos reported that adding bat0 in the br-lan bridge partially fixed the issues found when using the current LibreMesh code on top of OpenWrt 21.02 and 22.03.

With swconfig (approx OpenWrt 19.07), the interfaces included in br-lan were defined like this in /etc/config/network (see full file in #951 (comment)):

config interface 'lan'
	option type 'bridge'
	option ifname 'eth0.1'
[...]

but with DSA (approx OpenWrt 21.02 and 22.03), now this section only contains the IP configuration, while the bridged interfaces list are defined in another section of the same file:

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'

This causes that, on recent OpenWrt releases, the bat0 interface gets added to the bridge in the old way by proto/lan.lua from lime-system, that does not work with DSA-style configuration:

uci:set("network", "lan", "ifname", bridgedIfs)

@ilario
Copy link
Member Author

ilario commented Apr 1, 2023

Maybe this is already fixed. To be checked.

@ilario ilario closed this as completed Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant