Network configuration migration
In OpenWrt 21.02 RC2, there is offered forced option to do migration in LuCI for network stack related to:
- Network bridge configuration migration
- Network ifname configuration migration
Basically, it is clear for me from these release notes for 21.02 RC2 on their forum, so copy&pasted here:
New network configuration syntax
There have been several changes to the network configuration syntax in /etc/config/network:
- in config interface, option ifname has been renamed to device (since it refers to a device section)
- in config device of type bridge, ifname has been renamed to ports
for new installs, the generated configuration now creates separate sections for layer 2 (config device) and layer 3 (config interface) configuration
The old syntax is still supported to facilitate transition, and there is no automated migration when upgrading.
However, the LuCI web interface detects old-style configuration and will propose to migrate it to the new syntax. This is necessary to be able to edit network configuration through LuCI.
It helps to offer more settings related to VLAN in LuCI.
Basically, it means that we need to do changes related to:
-
migrate users to new configuration (@kkoci) -
Fix firewall zone name limit (packages@3c4ffcbe) -
Split network interfaces definitions to interfaces
anddevices
(packages!956 (merged)) -
auto-apply these fixes on upgrade (updater-lists!43 (merged))
-
-
foris-controller (@mmatejek / @fhron ) -
VLANs for bridges lan & guestDifferent networks on different bridges (lan & guest) should still work fine without VLANs. -
TurrisHWTurrisHW is doesn't need changes as it does not read uci config at all❓
I would say that we don't need to support old configuration, just a new one once we forced it to users.
Before we can start work to work on VLAN integration in reForis