Hi all,
I noticed that IPv4 Fast Path somehow is not activated but Allow Fast Path is checked in IP Settings. Where is the root cause most possibly? Thanks.
Re: IPv4 Fast Path not activated
One likely culprit, you have to disable/remove all firewall rules.
https://wiki.mikrotik.com/wiki/Manual:Fast_Path
https://wiki.mikrotik.com/wiki/Manual:Fast_Path
-
-
enigma1939
just joined
- Posts: 20
- Joined:
Re: IPv4 Fast Path not activated
Does it mean that I can only pick up one feature between Fast Track and Fast Path? I added "/ip firewall filter add chain=forward action=fasttrack-connection connection-state=established,related" and "/ip firewall filter add chain=forward action=accept connection-state=established,related" to enable Fast Track.One likely culprit, you have to disable/remove all firewall rules.
https://wiki.mikrotik.com/wiki/Manual:Fast_Path
Re: IPv4 Fast Path not activated
Well, if you're running firewall, then fastpath doesn't make much sense (if I understand its function correctly, it's a shortcut between different drivers and traffic then bypasses some of generic L2 of ROS and all of L3, for firewalling such shortcuts should not happen). Fasttract is (again according to my understanding) a shortcut which bypasses part of L3 functions in ROS.
When it comes to performance: L3 is much more resource-demanding than L2, so fasttrack makes lots of sense. If, OTOH, you need fastpath in order for device to cope with traffic, you really should reconsider things (either get yourself faster hardware or change setup). E.g. get a device capable of L3 HW offload.
BTW, if the two firewall rules you mentioned in last post are the only two rules, then you can keave firewall rule list empty. Fasttrack relies on connection tracking machinery doing its job (and connection tracking is one of most CPU-intensive tasks of an L4 firewall), so if there are no firewall rules (including NAT), then connection tracking is not needed and ROS should skip doing it. And without connections being tracked everything is (kinda) fasttracked.
When it comes to performance: L3 is much more resource-demanding than L2, so fasttrack makes lots of sense. If, OTOH, you need fastpath in order for device to cope with traffic, you really should reconsider things (either get yourself faster hardware or change setup). E.g. get a device capable of L3 HW offload.
BTW, if the two firewall rules you mentioned in last post are the only two rules, then you can keave firewall rule list empty. Fasttrack relies on connection tracking machinery doing its job (and connection tracking is one of most CPU-intensive tasks of an L4 firewall), so if there are no firewall rules (including NAT), then connection tracking is not needed and ROS should skip doing it. And without connections being tracked everything is (kinda) fasttracked.
-
-
enigma1939
just joined
- Posts: 20
- Joined:
Re: IPv4 Fast Path not activated
Yes, there are only 2 rules I mentioned on firewall list and I removed them to keep list empty. However, Fast Path still shows inactivated (Allow Fast Path is checked). BTW, Mikotik Manual:Fast Path says that FastTrack is FastPath+Connection Tracking. Does it means that FastTrack contains Fast Path？Well, if you're running firewall, then fastpath doesn't make much sense (if I understand its function correctly, it's a shortcut between different drivers and traffic then bypasses some of generic L2 of ROS and all of L3, for firewalling such shortcuts should not happen). Fasttract is (again according to my understanding) a shortcut which bypasses part of L3 functions in ROS.
When it comes to performance: L3 is much more resource-demanding than L2, so fasttrack makes lots of sense. If, OTOH, you need fastpath in order for device to cope with traffic, you really should reconsider things (either get yourself faster hardware or change setup). E.g. get a device capable of L3 HW offload.
BTW, if the two firewall rules you mentioned in last post are the only two rules, then you can keave firewall rule list empty. Fasttrack relies on connection tracking machinery doing its job (and connection tracking is one of most CPU-intensive tasks of an L4 firewall), so if there are no firewall rules (including NAT), then connection tracking is not needed and ROS should skip doing it. And without connections being tracked everything is (kinda) fasttracked.
Re: IPv4 Fast Path not activated [SOLVED]
My interpretation is that without fastpath there is no fasttrack.... Mikotik Manual:Fast Path says that FastTrack is FastPath+Connection Tracking. Does it means that FastTrack contains Fast Path？
However I have mixed feelings about the importance of fastpath ... as fastoath manual specifies, there are quite a few constraints for enabling fastpath and I'm pretty sure that not all of my installations fulfill all of them ... and yet fasttrack seems to work its magic everytime I want it.
-
-
enigma1939
just joined
- Posts: 20
- Joined:
Re: IPv4 Fast Path not activated
Thank you for your post. I have to advocate fasttrack.My interpretation is that without fastpath there is no fasttrack.... Mikotik Manual:Fast Path says that FastTrack is FastPath+Connection Tracking. Does it means that FastTrack contains Fast Path？
However I have mixed feelings about the importance of fastpath ... as fastoath manual specifies, there are quite a few constraints for enabling fastpath and I'm pretty sure that not all of my installations fulfill all of them ... and yet fasttrack seems to work its magic everytime I want it.