Bug in /queue tree set??

RouterOS General
1

I’m in /queue tree. An entry reads:

2 name=“inbound-std” parent=inbound-total packet-mark=PM-std limit-at=0 queue=inbound-std-rate priority=7 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s

I type: set 2 priority=6

The entry now reads

2 name=“inbound-std” parent=inbound-total limit-at=0 queue=inbound-std-rate priority=6 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s

Packet-mark has gone away! Why? It doesn’t set other values to null or zero, why packet-mark?

(I’m running 3.30.)

2

Works as expected in 4.5:

[admin@rb750g] /queue tree> pri   
Flags: X - disabled, I - invalid 
 0   name="inbound-std" parent=global-in packet-mark=PM-std limit-at=0 queue=ethernet-default priority=7 
     max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 
[admin@rb750g] /queue tree> set 0 priority=6
[adm in@rb750g] /queue tree> pri
Flags: X - disabled, I - invalid 
 0   name="inbound-std" parent=global-in packet-mark=PM-std limit-at=0 queue=ethernet-default priority=6 
     max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s
3

I just tried it on my RB411 ROS4.4
It is all ok, nothing goes wrong

4

OK. Clearly, this is a bug in the earlier release, as I duplicated your results on another router. In 3.30:

[admin@town] /queue tree> add name=foo parent=enet4 packet-mark=TESTPM
[admin@town] /queue tree> print
Flags: X - disabled, I - invalid 
 ...
 6   name="foo" parent=enet4 packet-mark=TESTPM limit-at=0 queue=default priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 
[admin@town] /queue tree> set 6 priority=7
[admin@town] /queue tree> print
Flags: X - disabled, I - invalid 
...
 6   name="foo" parent=enet4 limit-at=0 queue=default priority=7 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s

In 4.6:

[admin@local] /queue tree> add name=foo parent=testjack packet-mark=TESTPM     
[admin@local] /queue tree> print
Flags: X - disabled, I - invalid 
 0   name="foo" parent=testjack packet-mark=TESTPM limit-at=0 queue=default priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 
[admin@local] /queue tree> set 0 priority=7
[admin@local] /queue tree> print
Flags: X - disabled, I - invalid 
 0   name="foo" parent=testjack packet-mark=TESTPM limit-at=0 queue=default priority=7 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s

Thanks.

5

yes, it’s known ‘feature’ of v3.30