Instead of only using tagged CPU port configurations when more than one VLAN
is present on the switch, always emit tagged configurations unless a board
explicitely opts out of this behaviour by using the previously introduced
[0-9]u@netdev syntax.

Emitting default tagged configurations has the following benefits:

 - Relation of switch vlans to netdevs is easier to understand, especially
   for multi-cpu-port switches

 - Adding additional VLANs (e.g. to break out a LAN port for other purposes)
   becomes easier as users are not forced to change the existing untagged
   VLAN to tagged and the existing ifname notation from ethX to ethX.Y
   anymore, drastly reducing the likelyhood of soft-bricks.

Signed-off-by: Jo-Philipp Wich <>
 package/base-files/files/lib/functions/ | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/package/base-files/files/lib/functions/ 
index fc48a76..732201f 100755
--- a/package/base-files/files/lib/functions/
+++ b/package/base-files/files/lib/functions/
@@ -160,7 +160,7 @@ _ucidef_finish_switch_roles() {
                                        json_select ..
                                json_select ..
-                               if [ $n_vlan -gt $n_cpu -o ${need_tag:-0} -eq 1 
]; then
+                               if [ ${need_tag:-0} -eq 1 -o ${want_untag:-0} 
-ne 1 ]; then

Lede-dev mailing list

Reply via email to