Very helpful! Can see the difference between the fasttrack rule being enabled/disabled both when using NAT and between internal networks. I still don't like the dummy rule, and being unable to log fasttracked traffic is kind of annoying, but at least it works.Switch off the fasttrack and load the router by natted traffic till it reaches 100% cpu. Then enable the fasttrack and check the difference in cpu utilisation and throughput.
Would you really want to log every single packet that goes through the router?and being unable to log fasttracked traffic is kind of annoying, but at least it works.
Only on a temporary basis for diagnostic purposes. I want to be able to make sure that traffic I intend to fasttrack is actually being processed as such.
Would you really want to log every single packet that goes through the router?
If you're trying to log each connection that's made, then you can very easily add logging rules after this.
Fasttrack rule only applies to the second packet and beyond in any given connection. This is becuase when the first packet arrives in a connection, the connection state is "new" and not "established" or "related" - so the fasttrack rule doesn't apply to these new connections - just put a logging rule right after the accept established,connected rule, and you'll log every single new connection.
That presentation is awesome! Gave me a much better understanding of how packets flow through ROS...and helped me diagnose why a few connections weren't working right! Thanks!I would suggest to look into this brilliant presentation,
http://mum.mikrotik.com/presentations/E ... 413105.pdf
video,
https://www.youtube.com/watch?v=8bl7V5iFVOc