I can configure the vlan like the examples and the two vlans will not talk to each other.
also seeing: "mv88e6085 f1072004.mdio-mii:00: VTU member violation for vid 1, source port 3" is this the problem? This error is very easy to get just remove untagged from vlan 1.
Have also added eth0 as tagged and did not help.
Been working on this for nights, and can not make it work,
very simple vlan 1 lan 2,3,4 and vlan2 lan one all untaged.
This is not will look like when finished if can make it work.
Version OpenWrt 22.03.2 r19803-9a599fee93 / LuCI openwrt-22.03 branch git-22.288.45147-96ec0cd
root@OpenWrt:/etc/config# cat network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdc3:c5f8:1077::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
config interface 'lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
option device 'br-lan.1'
config device
option name 'wan'
option macaddr '26:f5:a2:c1:eb:08'
config interface 'wan'
option device 'wan'
option proto 'dhcp'
config interface 'wan6'
option device 'wan'
option proto 'dhcpv6'
config bridge-vlan
option device 'br-lan'
option vlan '1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
config bridge-vlan
option device 'br-lan'
option vlan '2'
list ports 'lan1:t'
config interface 'VLAN2'
option proto 'static'
option ipaddr '192.168.2.1'
option netmask '255.255.255.0'
option device 'br-lan.2'
Well the first problem here is actually a switch driver fault in 22.03 that makes the switch to a hub so all ports are the same whatever vlan setup you do.
So the first thing you should do with this kind of multi vlan setup on this device family (mvebu) is to upgrade to a master image.
https://downloads.openwrt.org/snapshots/targets/mvebu/cortexa9/
The new switch driver in kernel 5.15 in dev snapshot (master code) has a fix for the βhub like behaviorβ. Not sure it will fix the actual problem but I canβt see any big problem with your config either.
What is diff in openwrt-mvebu-cortexa9-linksys_wrt3200acm-squashfs-sysupgrade.bin v openwrt-mvebu-cortexa9-linksys_wrt3200acm-initramfs-kernel.bin? and what do a want?
now on OpenWrt SNAPSHOT r22555-cd8c698f78 / LuCI Master git-23.093.56957-2145121
still,
get kern.err kernel: [ 1582.640787] mv88e6085 f1072004.mdio-mii:00: VTU member violation for vid 1, source port 3
Initramfs is a imaginary image for development that is installed and run directly on the ram memory so a simple reboot erases it.
Initramfs is good to use if you donβt know if your new code is about to crash and burn your device. Usage of this during development and installation of new code over a couple of 100times also saves cycle life of the flash memory.
But it canβt be installed as normal installation, it is installed at boot usually with u-boot and tftp installation.
I see nothing in the OP that is not achievable; but see my first post, as you had it wrong. Maybe present what you are attempting, not with a pic but a simple matrix.