Hello.
Is simple queue applicable for ikev2 user connections?
/queue simple
add limit-at=2M/5M max-limit=2M/5M name=queue1 target=1.194.72.115/32
2.
The remote user will be assigned 1.194.72.115 when connected.
Remote users are becoming the Internet.
4.
/ip ipsec remote-peer pr
However, the QoS packet count is 0.
qos no control.
I would really appreciate it if you could tell me what went wrong.
I can’t tell you exactly what went wrong but I can confirm the behaviour does exist. I didn’t need simple queues (nor the queue tree) anywhere yet but it was quite easy to add some to an existing IKEv2 setup just for the sake of the test.
There is a sentence in the manual which suggests that simple queues only work on interfaces, but only someone from Mikrotik support is able to say whether it is true and if so, whether it is a bug or feature:
In this case statement works right also if we indicate only one of parameters: “target=” or “interface=”, because both of these define where and for which traffic this queue will be implemented.
Even more funny is that neither 6.42.7 nor 6.43rc56 actually recognize the interface parameter when adding/modifying a /queue simple, so that manual line is not in line with the state of the art although the page states that it has been updated three weeks ago.
Thank you very much for your answer.
The answer is under “flow identifiers”:
https://wiki.mikrotik.com/wiki/Manual:Queue#Flow_Identifiers
"Note: Since RouterOS v6 these settings are combined in the option target where you can specify either of the above. Target is to be viewed from perspective of the target. If you want to limit your users’s upload capability, set “target upload”.
So, the interface parameter was present in RouterOS 5 but in ROS 6 it got merged with “target”.