L3 HW Offloading CRS 326

Hi

I have a Mikrotik CRS326-24s+2q+rm cloud router switch that i setup with multiple VLANS 100-110
My client test PC on any vlans except for vLAN 109 (which is the vlan of the port connected to the modem) experience a cpu bottle neck due to inter-vlan routing and i am trying to fix that by enabling L3 HW offloading to leverage the switch chip 98DX8332 following the steps in this video https://www.youtube.com/watch?v=c2sAA6jMjCY&t=1439s

Problem

When i enable L3 HW Offloading i can no longer ping google.com from the test pc but i still can from the switch terminal .
I have 1 bridge with all the ports added to it, a vlan tables of all the vlans defined on the bridge interface and corresponding vlan interfaces, vlan filtering enabled

Topology

ISP Modem ( Not in Bridge Mode with DHCP Server)

Connects to CRS326 on its port 4
|
|
CRS326

sfp-sfpplus24 is connected to modem with DHCP Client and static route configured on vlan 109
|
|
PC Client

connected on vlan 100 on sfp-sfpplus18
cant ping google.com when i enable L3 HW offloading and i can when i disable it
can ping from switch terminal when L3 hw offloading is enabled or disabled.

any help is appreciated

thank you

Just an update

Removing the bridge interface from the tagged ports on each VLAN, especially VLAN 100, allowed the client test PC to connect to the internet now that L3 HW Offloading is enabled and active

[admin@crs326-vcf-core-sw] > /ip/route/print detail
Flags: D - dynamic; X - disabled, I - inactive, A - active; 
c - connect, s - static, r - rip, b - bgp, o - ospf, i - is-is, d - dhcp,>
H - hw-offloaded; + - ecmp 
   DAdH  dst-address=0.0.0.0/0 routing-table=main gateway=10.0.0.1 
         immediate-gw=10.0.0.1%INTERNET-VLAN distance=1 scope=30 
         target-scope=10 vrf-interface=INTERNET-VLAN 

   DAcH  dst-address=10.0.0.0/24 routing-table=main gateway=INTERNET-VLAN 
         immediate-gw=INTERNET-VLAN distance=0 scope=10 target-scope=5 
         local-address=10.0.0.147%INTERNET-VLAN 

   DIc   dst-address=192.168.88.0/24 routing-table=main gateway=ether1 
         distance=0 scope=10 target-scope=5 
         local-address=192.168.88.1%ether1 

   DAcH  dst-address=192.168.100.0/24 routing-table=main gateway=MGMT-VLA>
         local-address=192.168.100.1%MGMT-VLAN 

   DAcH  dst-address=192.168.101.0/24 routing-table=main 
         gateway=VMOTION-VLAN immediate-gw=VMOTION-VLAN distance=0 
         scope=10 target-scope=5 
         local-address=192.168.101.1%VMOTION-VLAN 

   DAcH  dst-address=192.168.102.0/24 routing-table=main gateway=VSAN-VLA>
         immediate-gw=VSAN-VLAN distance=0 scope=10 target-scope=5 
         local-address=192.168.102.1%VSAN-VLAN 

   DAcH  dst-address=192.168.103.0/24 routing-table=main 
         gateway=HOST-OVERLAY-VLAN immediate-gw=HOST-OVERLAY-VLAN 
         distance=0 scope=10 target-scope=5 
         local-address=192.168.103.1%HOST-OVERLAY-VLAN 

   DAcH  dst-address=192.168.104.0/24 routing-table=main 

   DAcH  dst-address=192.168.105.0/24 routing-table=main 
         gateway=EDGE-UPLINK-A-VLAN immediate-gw=EDGE-UPLINK-A-VLAN 
         distance=0 scope=10 target-scope=5 
         local-address=192.168.105.1%EDGE-UPLINK-A-VLAN 

   DAcH  dst-address=192.168.106.0/24 routing-table=main 
         gateway=EDGE-UPLINK-B-VLAN immediate-gw=EDGE-UPLINK-B-VLAN 
         distance=0 scope=10 target-scope=5 
         local-address=192.168.106.1%EDGE-UPLINK-B-VLAN 

   DAcH  dst-address=192.168.107.0/24 routing-table=main 
         gateway=ISCSI-VLAN immediate-gw=ISCSI-VLAN distance=0 scope=10 
         target-scope=5 local-address=192.168.107.1%ISCSI-VLAN 

   DAcH  dst-address=192.168.108.0/24 routing-table=main 
         gateway=iDRAC-VLAN immediate-gw=iDRAC-VLAN distance=0 scope=10 
         target-scope=5 local-address=192.168.108.1%iDRAC-VLAN 

   DAcH  dst-address=192.168.109.0/24 routing-table=main 
   DAcH  dst-address=192.168.110.0/24 routing-table=main 
         gateway=WLD-VM-VLAN immediate-gw=WLD-VM-VLAN distance=0 
         scope=10 target-scope=5 local-address=192.168.110.1%WLD-VM-VLAN

However, I’m still seeing an inter-VLAN routing bottleneck, where the CPU reaches 100% when performing an internet speed test from the Test PC.

looks like a duplicate of the topic you already created

http://forum.mikrotik.com/t/likely-hitting-software-based-routing-limits/183202/20

please continue there, do not create multiple topic about the same