Firewall in RouterOS: Routing Processes in Action

As mentioned in previous tutorials, the five main processes of the routing flow in RouterOS are prerouting, input, forward, output, and postrouting, each of which are comprised of different smaller stages. In this session, we will be configuring all those smaller steps and seeing them in action via the Log utility for the three main types of input, forward, and output traffic.

[@jeytis72]

Very good. One question, if you don't mind. You said that when a new connection is established it doesn't need to reach, i.g, the DST_NAT of the chain because Connection tracking has registered it, resulting in saving router resources. Good, but I was wondering how packets related to an established connection are exactly recognized, and don't reach the end of the chain each time. Is there kind of an (same of all) ID number in teh packets that connection tracking reads? Thanks

[@MikroTikCanada]

Dear jeytis72,
Thanks for the comment and sorry for this late reply. We were waiting to reach the current stage of our training to answer your question. For established connections, packets do have an ID number that can be traced using Wireshark or exporting complete logs records, but if you have a look at tutorials 40-42, you'll see that once an incoming new connection with a fixed host IP/Port and destination IP/Port receives its reply, it will be registered and as long as those same IP addresses and port numbers are being used, that connection will remain registered and regarded as an established connection.

[@nimsamreth]

i would like you explain each action of them.

[@MikroTikCanada]

Dear Samreth Nim,
Thanks for the comment. If you are referring to the actions available in the Actions tab of firewall settings, we will make a video about them soon.

[@nimsamreth]

@MikroTik Cannada, Thank you.