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