There are multiple requests on here for this feature, but apparently it's not even on their development timeline. I find this puzzling given the number of use-cases, and this being a standard in Linux for some time. Not to mention the fact that most if not all of their major competitors offer this feature.

Anyone have any insight as to why they are not pursuing it?

Well, IMO VETH covers the need for containers (aka Docker) and VXLAN is the more standard way of using L2 over IP nowadays.

Who in their right mind uses macvlan in 2023?

VXLAN/EVPN/MPLS/SR?

Who in their right mind uses macvlan in 2023?

VXLAN/EVPN/MPLS/SR?

If you search the forums, a common use case such as mine is where for some ISP's you need to present a second mac address to get a second public IP. Hence the usefulness of macvlan. There are other uses still too that are relevant. It's also worth noting that the other router OS's out there generally support it.

In the meantime you might try this vrrp hack

Btw, virtual network devices (veth) could possibly be implemented using Linux Network Namespaces in the current kernel.

FWIW, I just saw MACVLAN interfaces were added in the v7.12beta3. No docs or anything, but was in RN.

tried using the CLI yet?

tried using the CLI yet?

I'm still not sure the use cases...just read and saw in winbox/cli:

I'll check if I can find an MT box to play with at home. Our current ISP/CO can offer 4 IP addresses over the same cable using the media converter XG6846, but requires a distinct MAC addresse for each one.

Macvlan is working great! No need anymore for the VRRP hack, I can get multiple public IP's via dhcp from my ISP with this now.

Great! I haven't had time to try it yet so It would be nice if you could share a sample config using export.

What's the difference between private and bridge modes?

Has anyone gotten this to work yet using 7.12?

I have to say that macvlan is very useful, I am very happy to have this feature. But when I add another VLAN on the macvlan interface, the router restarts immediately.

Adding a macVlan onto eth1 of a hex PoE seems to work, however fastrack only seems to work in 1 direction.
From router towards upstream ok, downstream does not get fasttracked.

Could you please share an export of just the MACVLAN config?

/interface macvlan
add mac-address=CC:2D:E0:68:xx:xx name=ether1.macvlan1 parent=ether1

also

/ip dhcp-client
add add-default-route=no interface=ether1.macvlan1

Then on dhcp server I give it an alternate IP address.

add address=192.168.92.20 client-id=1:cc:2d:e0:68:xx:xx \
mac-address=CC:2D:E0:68:xx:xx server=defconf

/ip dhcp-server network
add address=192.168.92.0/24