Following these instructions:
add name=VLAN2 vlan-id=2 interface=ether1 disabled=no
add address=10.10.10.3/24 interface=VLAN2
The device will pass traffic through the VLAN and to the appropriate ports… however, it will not respond to pings to that IP address from another device on the same VLAN.
It seems… in my case… the issue is that if I assign an IP address to the Ethernet interface (e.g. eth1) it does not properly propagate out on the PVID of the network. Where-as if I assign the IP to the VLAN ID of the network then it works.
In my configuration, I have a VLAN set up:
/int vlan add vlan-id=254 name=VLAN254 interface=ether8 …
and an IP on the VLAN:
/ip addr add address=192.168.16.2/24 interface=VLAN254 …
This one MikroTik itself can ping its own IP address there, but another MikroTik across a trunked connection cannot ping it. Nor vice-versa (same VLAN config on the other MikroTik, /ip addr add address=192.168.16.3/24 interface=VLAN254 on that one).
I thought that bridging is only required to make packets which arrive tagged on a VLAN be able to go out (untagged) a physical port?
This is entirely in the memory and CPU of the MikroTik.
To what would I bridge the VLAN, anyway, since there is no physical port associated with responding to a PING of an IP address on a VLAN interface if the MikroTik itself?
Thanks!