Hi Karl, All looks to be in order. In response to your question - yes, I am. I have a guest network which is limited to 2M/256k per user, with an aggregate of 8M/1M This gets switched to 512k/128k per user and 2M/512k aggregate once a pre-set download threshold is met. (A script does this, by disabling one simple queue, and enabling another) Below is my config. The per connection queueing is handled by the individual queue types, which are then bound in the simple queue which handles the aggregate. This is running on a CRS109-8G-1S-2HnD - with guest networks bring a pridge interface, containiung 5x tagged ethernet ports to various APs, and an SSID on the CRS itself. RouterOS version is 6.37.3 /queue type add kind=pcq name=Guest-2M-Downstream pcq-burst-time=1s pcq-classifier=dst-address pcq-dst-address6-mask=64 pcq-rate=2M pcq-src-address6-mask=64 add kind=pcq name=Guest-256k-Upstream pcq-burst-time=1s pcq-classifier=dst-address pcq-dst-address6-mask=64 pcq-rate=256k pcq-src-address6-mask=64 add kind=pcq name=Guest-128k-Upstream pcq-burst-time=1s pcq-classifier=dst-address pcq-dst-address6-mask=64 pcq-rate=128k pcq-src-address6-mask=64 add kind=pcq name=Guest-512k-Downstream pcq-burst-time=1s pcq-classifier=dst-address pcq-dst-address6-mask=64 pcq-rate=512k pcq-src-address6-mask=64 /queue simple add max-limit=1M/8M name=Guest-Normal-Speed queue=Guest-256k-Upstream/Guest-2M-Downstream target=172.19.124.128/26 add disabled=yes max-limit=512k/2M name=Guest-Limit-Speed queue=Guest-128k-Upstream/Guest-512k-Downstream target=172.19.124.128/26 I just went through the rest of the config on that device and I cant see anything else that would trigger the queue to work, other than the above. There is a Queue Tree associated to the NBN facing interface, but that's just to prioritorise the sending of packets from specific VLANs. M. ________________________________________ From: Public <public-bounces@talk.mikrotik.com.au> on behalf of Karl Auer <kauer@nullarbor.com.au> Sent: Saturday, 3 February 2018 16:21 To: public@talk.mikrotik.com.au Subject: Re: [MT-AU Public] queue noob On Sat, 2018-02-03 at 04:14 +0000, Michael Junek wrote:
If you're using a bridge, the IP should be assigned to the bridge interface, not to one of the members. That might be your issue.
Thanks. The IP address 192.168.100.1/24 is in fact assigned to the bridge. Sorry, my wording was poor. Is anyone on this list actually using a queue to limit bandwidth? Things are not helped by the Mikrotik documentation being out of date. It refers to several attributes of a simple queue that do not exist on my router (like "interface", "direction" and "dst-address"). The description in the doco is very clear (if apparently out of date): "Add a simple queue rule, which will limit the download traffic to 512kbps and upload to 256kbps for the network 10.1.1.0/24, served by the interface Ether2: [admin@MikroTik] /queue simple> add name=private \ target=10.1.1.0/24 \ max-limit=256K/512K \ interface=ether2 "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." But my queue simply does not do what the doco says it should. Though it does have some effect. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer@nullarbor.com.au) work +61 2 64957435 http://www.nullarbor.com.au mobile +61 428 957160 GPG fingerprint: 8454 EE43 6215 B6DD 1B4D 9D8D 984D 7BA1 7378 A38D Old fingerprint: 58F8 09D4 97E4 D74A 0940 44BC 8D6D C28C 3BC9 B0CB _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au