Bug ? ver.3.16

RouterOS General
1

I was find that in simple queues total-bytes value is caculated by upload of host no like total upload+download
my queue:
target-addresses=192.168.20.4/32 dst-address=0.0.0.0/0 rate=126736/9544496 total-rate=126736
packet-rate=295/795 total-packet-rate=295 queued-bytes=0/24000 total-queued-bytes=0 queued-packets=0/16
total-queued-packets=0 bytes=2932436/229950560 total-bytes=2933204 packets=54675/153323 total-packets=54687
dropped=0/0 total-dropped=0 lends=127/4 total-lends=127 borrows=54548/153303 total-borrows=54560
pcq-queues=0/640 total-pcq-queues=0

iam using RED (shaping-method)

If i have something wrong please help me with correct…
Adrian

2

If target-address means src-address, yes, its for “upload”. Maybe one more simple queue with dst-address for “download” ?

Better yet - Queue tree.

I wouldn’t suggest using RED as I suspect but have not tested it to behave as Policing:

Which cripples network performance.

3

please check how simple queues work.

target address is an argument for upload and for download limitation for that target, hence, if you are downloading, then target is dst-address if you are uploading target is source, as simple queue “lives” in global-* queues, depending on your config.

4

to imtrulylovd

Where are you getting this? it is completely wrong

Every queue type here (PCQ,FIFO,RED and SFQ) have both aspects

  1. shaper aspect (I don’t know why it is “Policing” in your picture, but it is 100% Shaper) - if something is over the limit, it is dropped
  2. scheduler aspect ( for no reason you call it “Shaping” in your picture) - if something is over the limit it is scheduled to be send out in closest possible moment.

In RouterOS you can make queue more shaper or more scheduler by changing queue size.