New Packet flow diagram

RouterOS General
21

Thanks for that, but what I do not understand is if the diagram shows Global HTB in Input chain, then it’s not supposed to get any forwarding traffic?

According to diagrams:
A) Traffic to Router(v5):
PreRouting (ConnTrack, Mangle, DstNAT**, Global HTB**)
Input (Mangle, Filter)Traffic to Router(v5):

B)Traffic forwarded(v5):
PreRouting (ConnTrack, Mangle, DstNAT, Global HTB)
Forward (Mangle, Filter)

C)Traffic to Router(v6):
PreRouting (ConnTrack, Mangle, DstNAT)
Input (Mangle, Filter, Global HTB)

D)Traffic forwarded(v6):
PreRouting (ConnTrack, Mangle, DstNAT)
Forward (Mangle, Filter,?)
…

In scenario D, there is no Global HTB in prerouting, according to diagram it is now in Input chain, but Input chain is not used if it is forwarded traffic.
I’m not suggesting ROS is broken, I’m suggesting that possibly the diagram is wrong, or does ROS6 process Input chain for forwarded traffic as well now?

Regards
Ekkas

22

It shows it not only in Input chain, but in the Postrouting chain as well.
See above the last two blocks in postrouting.

23

It shows it not only in Input chain, but in the Postrouting chain as well.

I’m talking about prerouting.
Global has always been in postrouting(before Src-NAT, now after src-NAT), but seems to moved from prerouting to input, that’s the point I’m trying to make.
V5:

V6:

24

Any kind of traffic first hits Global HTB, then Simple Tree, and it does it only once. Input traffic hits them in the Input, while Output and Forward traffic - in the Postrouting. The packet flow has changed and you will need to adopt to it.

25

Any kind of traffic first hits Global HTB, then Simple Tree, and it does it only once.

Ok, that makes sense.

The packet flow has changed and you will need to adopt to it.

I need to understand before I can adapt. :slight_smile:

Where would you want QueueTree or Simple Queues in Input chain, except for web proxy maybe? Control is outbound?
Anyways…

Let me put it this way…
For normal unbridged, routed traffic a packed would travel roughly.(#=PacketMark *=Queue)

ROS 5
1-)Prerouting
1a)Mangle Prerouting #1
1b)Dst NAT
1c)Global-In Global-Total HTB *1
2-)Forward
2a)Mangle forward #2
2b)Filter forward
3-)PostRouting
3a)Mangle Postrouting #2
3b)Global-Out Global-Total HTB *2
3c)Src-NAT
4-)Interface HTB *2

So here (if I understand it correctly), you could:
new-packet-mark @ ManglePrerouting(1a), then queue @ Global-In/Global-total(1c)
Then re-mark the packet @ MangleForward(2a) or ManglePostrouting(3a), then queue @Global-out(3b) or Interface HTB(4-)
Correct?

ROS 6:
1-)Prerouting
1a)Mangle Prerouting #1
1b)Dst NAT
2-)Forward
2a)Mangle forward
2b)Filter forward
3-)PostRouting
3a)Mangle Postrouting
3b)src-NAT
3c)Global HTB *1?
3d)Simple queues
4-)Interface HTB

Here, the first queue that you reach, is only in Global HTB(3c), after prerouting, forward, postrouting Mangles. There is no mangle opportunity after that to re-mark the packet before Interface HTB(4-)?
I guess my question is then, can a packet carry more than one mark? Otherwise, how does a packet get remarked if the sequence above is correct?

Thanks for your patience
Ekkas

26

no opportunity

it cannot

27

Thanks Chupaka,
it would seem then a big downgrade from ROS5?
How can you do double-control QoS, i.e. shape by client type and QoS by traffic type on one router?

28

you may use dynamic Simple Queues for shaping, one queue per user - they are speedy now :slight_smile:

29

That is all fine and well, but the question is how to do it twice.
1)Per user (Throttling)
2)Total outgoing (QoS)
Where to mark and queue it second time?

Regards
Ekkas

30
  1. mark by traffic type in any mangle chain… - i suggest “forward”
  2. prioritize traffic by traffic type in HTB global
  3. use simple queues to apply individual user limits (use target as individual IP, or network and PCQ queue type)
31

Can anyone chuck this in a nice, printable pdf?

32

One addon from my point of view: I would like to have colours in the picture, they make the boxes much more clearer! :slight_smile:
PDF is also a good point. Please publish a vector graphics inside the PDF so that we can enjoy a real wallpaper :smiley:

Thank you!

33

Is it possible to get this flow chart pictures in SVG or other vectorbased picture format?

34

The original is in Open Office, so no. You could re-draw it as vector and share :slight_smile:

35

Guys

Thank you very much for for the diagram. They are very useful and clear. Well done!

Questions:

  1. Could you add they to official documentation (WiKi)?
  2. Is it possible to get originals for personal use? I’d want to add comments to the diagrams and print.

Thank you.

36

Svg files for those who requested:

37

Great, thx alot!

P.S.:
This would should go into the wiki :wink:

38

It is already there. Images you see here are linked to wiki :slight_smile:

39

Yes, thanks, finally i can replace my old packet flow diagram printouts that hangs on the wall just across the workplace.

Added PDF that i will use if someone wants to do the same :slight_smile:
Packet Flow Diagram v6.pdf (204 KB)

40

Thanks for sharing this post to us. This is really nice information.
IT Network Support