Archer C7 V2 no longer tagging CPU (eth1) on VLAN 1 on 25.12?

Installing and Using OpenWrt
1

Prior to 25.12[.2] my VLAN port configuration for VLAN1 looked like:

VLAN 1:
        vid: 1
        ports: 0t 1t 2 3 4

Now if I tag port 0 the network fails entirely. The router is unreachable. It seems that I have to leave port 0 untagged as in:

VLAN 1:
        vid: 1
        ports: 0 1t 2 3 4

for this device to work now, in 25.12[.2].

Is this a known change or is it a bug? I didn't see anything in the release notes about this.

What are the implications of not tagging port 0 now?

2

port 0 is likely the CPU. If it's tagged/untagged, it needs to match that of the interface (or bridge) to which it is connected.

Let's see the complete network 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
3

It looks like the reason for this is that prior to 25.12 I had this in my /etc/config/network:

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth1.1'

But on 25.12, the list ports 'eth1.1' has been changed to list ports eth1. This makes sense why port 0 is not tagged any more.

But why was the change from eth1.1 to eth1 made?

FWIW, it seems the same was done with eth0 and the wan switching it from eth0.2 to eth0.

4

Assuming that we're talking about a true set of default installs comparing 25.12 vs earlier, I don't know why the change was made.

That said, as long as it is consistent, it's not material. If the bridge uses eth1, the CPU should be untagged in the switch configuration for that VLAN. If it uses eth1.1 the CPU should be tagged in VLAN 1.

As long as you have no more than one untagged network on the CPU it should be fine.

5

There was a recent commit changing this

1 Like
6

Ah, yes. Looks like it was this one.

Thanks for the head's up!

2 Likes
7

By default, these devices will avoid the performance penalty/ overhead of tagging now - but either configuration is correct (and will continue to work).

1 Like