@chechito
Can you elaborate?
Mkx posted an official link about the CRS310 being capable of L3HW offloading (but not fasttrack).
Are you saying that the opposite is true?
Or something else?
I am confused.
i am refering to making an hybrid config in the traditional way like you will do with a hEX-S for example (without HW L3 offload because this CRS310 does not supports it)
Only using L2 HW offload for Switching tasks
I have configured some crs326-24g-2s+rm in that way in some special situations like this working decently
one simple way to test this is ADDING on the top of firewall filter this rules
/ip firewall filter
add chain=forward action=fasttrack-connection connection-state=established,related \
comment="fasttrack established/related"
add chain=forward action=accept connection-state=established,related \
comment="accept established/related"
i emphasize this NOT do Fast-track HW offload, let’s call it CPU fast-track
Are your devices internet facing, with such sparse rules??
@chechito
Thanks, but - maybe it is one of those days I am particularly bad at understanding - you did not clear at all the matter.
Mkx posted that this switch supports L3HW offloading.
You just re-stated that it doesn’t.
One of the two must be accurate, not both.
We’re both right … I already mentioned that L3HW offload in this switch only covers routing, not firewalling. And @chechito is talking about firewalling in his latest posts.
Yeah one thing is
L3 HW offload (simple routing, without NAT, useful for example for inter VLAN routing on the LAN) which CRS310 supports
and another different thing is
Offloading Fast-track Connections which is a feature related with L3 HW offload but only available on more advanded models of CRS switches
So it is the usual case of two very different things that - in order to better distinguish them - are called in Mikrotikish with the same or a very similar name.
Sort of homonyms or homographs.
I see, thanks to both.
So it is the usual case of two very different things that - in order to better distinguish them - are called in Mikrotikish with the same or a very similar name.
Sort of homonyms or homographs.
Well not really. Routing is pure L3 function and according to that, all devices which MT says support L3HW actually do routing in hardware (if ASIC config resources are not exhausted). Statfull firewall can be L3 or L4 and fast-track is mostly L4. So L3HW doesn’t really cover that. Some devices support this L4 functionality (but it’s hidden in L3HW heap).
Too much for me. I like the on and off button. ![]()