You’ve assigned a /32 address to the VLAN interface, so no route to 10.0.0.0/24 via the VLAN interface has been created. As a consequence, packets for anything in 10.0.0.0/24 took the default route.
If an Ethernet interface is a member port of a bridge, the VLAN interface must be attached to the bridge, not to the Ethernet interface. It may partially work but it causes problems.
Nice, I would have missed this reading quickly… Although I would have stated it differently, its not that he assigned anything specifically /32, its more like he simply forget some syntax and that is to add /24
add address=10.0.0.1 ??? interface=VLAN-BYTY network=10.0.0.0
I do have some questions…
What is the purpose of this rule??
The forward chain in its current configuration does not block traffic from the vlan to the internet or to your main LAN subnet so not sure why its there??
The only traffic being blocked is invalid traffic AND unsolicited WAN to LAN traffic (traffic heading to the LAN originated on the WAN).
My other question is that you have created a vlan for ether3 specifically but then have a general LAN subnet for the rest of the ports BUT INCLUDE ether 3.
What device is at the other end of ether 3, that can read both the LAN subnet traffic and the vlan (assuming a smart device??)