However, with v7.2rc3 I have fasttrack forward rules with hw offload working on RB5009. Did not find time for propper testing yet, but a quick ipperf run between routed VLANS on SFP+ shows >6GB/s with less than 50% total CPU load. So I understand you tested with tagged ports. I'm scared untagged po...

Once this all runs stable enough for production, this makes the RB5009 a perfect device combining router/coreswitch in one tiny box for branch sites.

Totally agree. Just lack one PoE-out port, as we have on the RB4011, to power-up a LtAP gateway for example :)

Mmmh I also did my tests using untagged ports, whereas yours are all tagged, this could be the reason.
I'll re-test all this ASAP.

OK, the only difference I see is protocol-mode you enforce to none, whereas I let it to its rstp default value.
I'll give this a try.

OK, same configuration here, I then must have an issue elsewhere...
Just to confirm, your vlan interfaces are on your bridge, and bridge set with vlan-filtering=yes and ingress-filtering=yes ?

*) bridge - added fast-path and inter-VLAN routing FastTrack support when vlan-filtering is enabled; *) l3hw - added HW offloaded FastTrack support for inter-VLAN routing; I have some difficulties to have this working. On which devices should this work ? RB4011 ? RB5009 ? Many thanks ! Works good f...

*) bridge - added fast-path and inter-VLAN routing FastTrack support when vlan-filtering is enabled; *) l3hw - added HW offloaded FastTrack support for inter-VLAN routing; I have some difficulties to have this working. On which devices should this work ? RB4011 ? RB5009 ? Many thanks ! -- (1) This ...

On my CCR1009 --- Just loaded 7.2rc2 and that went very smoothly so far everything is working as I expect ---- CPU is stable .... WireGuard is functioning and to my surprise its a bit faster now So brave, I am waiting for 7.2 stable before turning my CCR1009 into a rocking wireguard machine. (1) Th...

I have some difficulties to have this working.
On which devices should this work ?
RB4011 ? RB5009 ?
Many thanks !

Or set your RouterOS VLAN interface MTU to 1496, which also works, and makes more sense / things easier.

Faced the same issue, you have to set the MTU of the macOS Virtual Interface to 1496 or less, thanks to its Advanced / Hardware tab.