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

FS#4104 - netifd: new bridge vlan ports are not applied correctly, if bridge was empty before #9089

Open
openwrt-bot opened this issue Oct 22, 2021 · 0 comments
Labels

Comments

@openwrt-bot
Copy link

fblaese:

If a bridge is created without any members, and vlan members are added later on, a reload of netifd does not properly create the bridge. A second reload of netifd is required for the bridge to appear.

The following network configuration can be used to reproduce the issue:

config device 'switch0'
option name 'switch0'
option type 'bridge'

config bridge-vlan 'switch0_4'
option device 'switch0'
option vlan '4'

config bridge-vlan 'switch0_5'
option device 'switch0'
option vlan '5'

Restart netifd. Add ports to bridge-vlans:

uci set network.switch0_4.ports='eth0:t eth1:* eth2:* eth4:'
uci set network.switch0_5.ports='eth0:
eth2:t'

Reload netifd. The bridge configuration seems to be applied correctly, but the bridge is not created. A second reload of netifd is required. Starting the bridge manually (ifup switch0) also works.

Adding additional ports to an already existing and started bridge works as expected. Therefore, the bridge option option bridge_empty '1' can be used to work around this problem.

Restarting netifd instead of reloading also works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant