Simple queues not working and possible reason

This isn’t the first time that I have post about this problem.

Making torch to this user, I can found “ghost” packets, with no source or destination ports defined. These packets seems to be ignored by the queue and makes 100kbps upload rates (no matter the minimun rate defined).

But it isn’t logical. Should be a bug or firewall fault?

what ROS version do you use?

2.9.48 in a RB532A board

I’m sorry images are not displayed. Could you show them once more please ?

I can see 'em! =) Reposting on forum:
queue.gif
torch.gif

Thanks.

P: IMO this is a critical problem…

Here we go again:

Queues in a bridged AP:

Torch:

Queues in a routed AP:

Torch in user A:

Torch in user B:

Anybody is worried about it? This issue don’t affect exclusively to queues, because with no source/destination ports: can’t be mangled, filtered by firewall or policy routed.

These are only a few examples.

I can imagine, that this traffic could be with state=invalid.
However, there might be issues with torch.
The best way to clarify, where the problem and solve your problem, I suggest you to contact support (support@mikrotik.com).

Include the same description, attach support output file (make sure the router is running the latest version).

I have used Wireshark to capture some packets and discover more about this problem.

Here you can see torch, with the address marked with the arrow:

And now let’s see wireshark:

So I have an answer… and many questions :open_mouth:

Does queues count fragmented IP frames?