We have quite a few mikrotik users in the LibreQos chat server, and a burgeoning WISP community sharing insights and code. We recently switched to "zulip" chat which is highly interactive and a great deal of fun to use. It's here: https://chat.libreqos.io/join/fvu3cerayyaumo377xwvpev6/
I am having a great deal of trouble understanding the direction of mikrotik presently - I would like to see cake or fq_codel + bql become a default for egress, and it made simpler to leverage cake's bandwidth parameter without queue trees to do both ingress and egress. And that said, well, most of us have been abandoning inbound shaping entirely in favor of a LibreQos box there, and just using cake alone on egress, due to issues with "slow start". So I kind of hope someone from mikrotik can enlighten me (either here or there), and perhaps with some better interactivity from this chat server, we can get through some more basic interop issues that keep cropping up. Is the dscp bug fixed? Etc.
I am having a great deal of trouble understanding the direction of mikrotik presently - I would like to see cake or fq_codel + bql become a default for egress, and it made simpler to leverage cake's bandwidth parameter without queue trees to do both ingress and egress. And that said, well, most of us have been abandoning inbound shaping entirely in favor of a LibreQos box there, and just using cake alone on egress, due to issues with "slow start". So I kind of hope someone from mikrotik can enlighten me (either here or there), and perhaps with some better interactivity from this chat server, we can get through some more basic interop issues that keep cropping up. Is the dscp bug fixed? Etc.
Statistics: Posted by dtaht — Thu Feb 01, 2024 1:58 am