802.1Q VLAN 1 default tagged issue

Hello,

I added VLANs to my OpenWrt 24.10.4 (GL.iNet GL-MT6000), which works fine, but Iam confused on setting on my second switch (TL-SG108PE) using 802.1Q.

Normal approach with first switch (GS116Ev2 & 802.1Q)

OpenWRT Port 2 ( VLAN 1t*, 10t, 20t) β€”β€”- Switch Port 1 (VLAN 1t, 10t, 20t )

>This works fine.

On my second switch, I tried same setting but somehow does not communicate, until I change to untaggeg for VLAN 1 (TL-SG108PE):

OpenWRT Port 3 ( VLAN 1t*, 10t, 20t) connected to Port 8 of TL-SG108PE

Switch Port 8 (TL-SG108PE) - (VLAN 1U, 10t, 20t )

Switch Port 1-4 (TL-SG108PE) - (VLAN 1t, 10t, 20t ) (works fine for Omada AP connected)

Port 8 VLAN 1u works but is not logic for me… Should it not be :

Switch Port 8 (TL-SG108PE) - (VLAN 1t, 10t, 20t )

Let's take a look at the actual config:

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button (red circle; this works best in the 'Markdown' composer view in the blue oval):

Screenshot 2025-10-20 at 8.14.14 PM

Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network

The mental model is simple.

An access port is untagged, a link between switches or switch and router should be tagged.
"Mixed" ports you will sometimes find in data center setups.

Many switches use vlan1 for internal communication, just use any other number.

So you mean to move "normal" traffic over e.g. vlan 5. Leave Vlan 1 as untagged and put vlan 5 as tagged.... will try

Short Story: the moment you start using vlan id, you should treat id 1 as reserved.
Just forget that it exist and dont use it. Neither tagged nor untagged. At least with many enterprise gear it was nessesary to avoid id 1.

1 Like

There is nothing wrong with using vlan ids other than vlan 1, but I disagree with the sentiment that vlan 1 needs to be treated as reserved or otherwise specifically avoided.

I’ve helped setup hundreds of vlan enabled networks and I have never had an issue with vlan 1. In fact, I use vlan 1 both tagged and untagged on my own home network (which is composed of a mix of unifi and openwrt based systems).

Yes in Linux Land that is no issue. But many enterprise gear even in mid 00 had sometimes funny misbehavior when vlan id 1 was somewhere near the config....

Yes with OpenWrt default using 1 and 2 there is of course no issue at all.

Edit ps. If I would see vlan 1 in the wild I would threat it as unconfigured. I would expect ever port to have been placed in a vlan unequal 1 because that's the default...