![simulador mikrotik routeros simulador mikrotik routeros](http://www.unitedplexus.com/2016/images/joomlart/Mikrotik/FP_Mikrotik_Winbox3.jpg)
interface HTB (Hierarchical Token Bucket) - interface queue.local in - the last point of a packet destined to router itself.logical in-interface - the starting point of the decapsulated packet (from tunnels, IPsec, etc).physical in-interface - the starting point of the packet received by the router.After the packet is processed ICMP (ping) reply is generated inside the router (local-out processing) and will be sent out over the out-interface.Ī simple explanation of each box before we go further with examples: For example, the in-interface receives ICMP (ping) packet, its destination is the router itself, so the packet will go for local-in processing. Let's take a look at another example that will illustrate what happens if the packet's destination is a router.
![simulador mikrotik routeros simulador mikrotik routeros](https://image.slidesharecdn.com/mumpresentationmaterial2013rofiqfauzi-131201081201-phpapp01/95/mikrotik-network-simulator-mum-presentation-material-2013-12-638.jpg)
Without looking deeper into each facility, the packet enters in-interface, the router determines that it is IP traffic and needs to be routed, the packet goes through all routing processes and exits out-interface. So for example, if the packet needs to be routed over the router, a packet will flow as illustrated in the image below. There are 4 boxes in the center of the diagram: Bridging, Routing, Mpls decisions, and local router processes. It looks complicated at first, but after we go through the diagram with examples it will become much clearer. a diagram that shows what facilities and in what order is included in prerouting, input, forward, output, and postrouting.detailed bridging, routing, and MPLS flow diagram.It would be very complicated to represent what is going on with the packet in one diagram, therefore a packet flow diagram is divided into three parts: RouterOS packet flow diagram and flow examples will try to answers these questions. More advanced firewall setups, or complicated tasks, such as traffic prioritization, routing policies, where it is necessary to utilize more than one RouterOS facility, require knowledge: How these facilities work together? What happens when and why?