As you can see Mikrotik didn't plan to fix it in the time frame given. Would be interesting to hear why....10/17/2019 - MikroTik acknowledges and indicates there is no plan to patch in 90 day time frame.
- this is already known.no interface queue listed in winbox but present in CLI
Winbox does not show all features, use CLI for most functionality
I think this can be achieved with RADIUS authentication.I understand that I will need a guest VLAN, but how can I have two passwords for the same SSID, where each password determines which VLAN the client connects to?
No one can possibly answer that question. Start with checking changelogs: https://mikrotik.com/download/changelogsHi 2 all! If I'll upgrade mikrotik from 6.42.1 to 6.43.11 with a lot firewall rules, caps-man and vlan created I will get problem that something will not work ?
https://mikrotik.com/download/changelog ... lease-tree*) dhcpv6-server - added DHCPv4 style user options;
filter add chain=input src-address=188.8.131.52/32 in-interface=ether1 action=drop log=yes
viewtopic.php?f=1&t=26499&hilit=Teaser& ... 00#p617477
teaser: Code: Select all What's new in 7.0 alpha *) added support for UDP OpenVPN;
But I'm not sure if this is switch based LACP support.What's new in v2.1:
*) added support for LACP in CSS326 & CRS317;
Did you add eth9-meraki... port to relevant VLANs (Vlan tab on your Image 2)?The access point is plugged in to a port on one of the 14 switches, and I have also set the egress VLAN ID's on that port too. (Image 2).
enabled: yes mode: unicast primary-ntp: 184.108.40.206 secondary-ntp: 220.127.116.11 dynamic-servers: status: synchronized
yes, without fasttrack. fasttrack was introduced after I configurer the switch and never bothered to enable it as never had to.Unoptimized, that is, without fasttrack?
Yes if you use bridges, no if you use switch chipWell, somebody posted once that some CPU resources are used for switching, so it would be good for Mikrotik to comment on this.