Manual:Packet Flow: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 13: Line 13:


[[Image:Bridge_final.png|Packet Flow in Layer-2|700px]]
[[Image:Bridge_final.png|Packet Flow in Layer-2|700px]]
[[Image:IP_final.png|Packet Flow in Layer-3|700px]]




Line 22: Line 27:
[[Image:mangle_output.jpg|Mangle Output|100px]]
[[Image:mangle_output.jpg|Mangle Output|100px]]
[[Image:mangle_postrouting.jpg|Mangle Postrouting|100px]]
[[Image:mangle_postrouting.jpg|Mangle Postrouting|100px]]
[[Image:IP_final.png|Packet Flow in Layer-3|700px]]


==Analysis==
==Analysis==

Revision as of 12:14, 27 November 2008

MikroTik RouterOS is designed to be easy to operate in various aspects of network configuration. Therefore creating limitation for individual IP or natting internal clients to a public address or Hotspot configuration can be done without the knowledge about how the packets are processed in the router - you just go to corresponding menu and create necessary configuration.

However more complicated tasks, such as traffic prioritization, routing policies, where it is necessary to utilize more than one RouterOS facility, requires knowledge: How these facilities work together? What happens when and why?

To address these questions we created a packet flow diagram.

Diagram

As it was impossible to get everything in one diagram, Packet flow diagram for Mikrotik RouterOS v3.x was created in 2 parts:

  • Bridging or Layer-2 (MAC) where Routing part is simplified to one "Layer-3" box
  • Routing or Layer-3 (IP) where Bridging part is simplified to one "Bridging" box


Packet Flow in Layer-2



Packet Flow in Layer-3



Mangle Prerouting Mangle Input Mangle Forward Mangle Output Mangle Postrouting

Analysis

Routed traffic

Bridged traffic

Examples

Example1: Bridging with use-ip-firewall=yes

Example2: Routing - from Ethernet to Ethernet interface

Example3: Routing from one Bridge interface to another

Example4: IPsec encryption and sending to the peer

Example5: IPsec data receiving and decryption