Where such list can be found please? Looked into the docs, not being able to find any. I am just curious, if wifi-qcom-ac still does not allow 4 address (repeater mode), or if it will allow one in future?
I wouldn’t be so sure about it. I’m pretty sure the main reason for size difference is number of radio chipset drivers included and only minor size difference is due to additional functionality available in wifi-qcom.
I don’t think MT publishes extensive list of differences. But we all know that there are differences in VLAN tag handling (wifi-qcom-ac doesn’t do it at all, wifi-qcom does it to certain extent) and the newly introduced spectral-* tools. It should be enough to check all the changelogs starting with 7.13 (when wifiwave2 got split into 3 parts), I believe that changes between wifi-qcom and wifi-qcom-ac started to accumulate since then, as far as I remember there were numerous entries about wifi-qcom and only very sparse entries about wifi-qcom-ac.
Exactly, i do have CAP and roaming between them works wonderful (HAP AX3(capsman) and HAP AC3(cap)), the problem i described is roaming of devices under same AP interfaces, sometimes they even flap around 2ghz and 5ghz few times in 5mins for no apparent reason, (tv mounted on wall not moving inch and 1m from router…)
You can now see Tx/Rx byte and packet counters for each VLAN interface when using L3HW for inter-VLAN routing (on compatible switches). These counters are accessible in the Interface List section of WinBox/WebFig or by running specific CLI commands.
/interface/print stats
/interface/monitor-traffic
Mikrotik doesn’t want to touch wifi-qcom-ac for a good reason. The moment they do that complaints will start flowing because of the package size increase and lack of storage. It has been the same size for the past couple releases, but the regular wireless package gets a slimdown again. Spectral scan would be nice as well for anything that has support for wifi-qcom-ac package because that has been on the “to-do list” for almost 10 years for ac chipsets: http://forum.mikrotik.com/t/802-11ac-spectral-scan/81464/1
Cool, 10th anniversary is around the corner. 
Ammo, is that a feature that goes with MVLAN… or whatever the acronym is for automatically adding vlans on trunk ports.
As always, is this something that is inferred or do we have a statement or wiki where this is stated?
I would ask MK (whom I thank for the excellent work he is doing version after version, for once do we want to congratulate the developers? 
) if in a next version of ROS (or WinBox?) it is possible to add next to a command, a card or button a small guide or explanation.
For example, the FT option once and for all… is it ONLY useful with Capsman or does it actually work even without Capsamn but with the same SSID?
Nope. No “vlan sharing” required (MVRP).
It radically simplifies VLAN configurations IMO.
Essentially, you can tick the “vlan-filtering=yes” on fresh config and it won’t break anything (since default pvid=1 everywhere). You add a /interface/vlan vlan-id=42 (and ip address/dhcp-server) on the bridge. Then to use it on a port, just set pvid=42 in /interface/bridge/port to untag it. There is NO configuration needed in /interface/bridge/vlan - bridge is tagged on 42 automatically by using /interface/vlan & port’s pvid= will also untag. The both happen in “D” dynamic entry in /interface/bridge/vlan – that’s visible with print (and, correctly, not in export):
/interface/bridge/vlan> /interface/bridge/vlan/print where vlan-ids=42
Flags: D - DYNAMIC
Columns: BRIDGE, VLAN-IDS, CURRENT-TAGGED, CURRENT-UNTAGGED
# BRIDGE VLAN-IDS CURRENT-TAGGED CURRENT-UNTAGGED
;;; added by vlan on bridge
8 D bridge 42 bridge
;;; added by pvid
11 D bridge 42 ether10
VLAN 42 didn’t exist anywhere, and bridge has mvrp=no set, and set an active port “/interface/bridge/port set ether10 pvid=42”. Above was result. The comments in print aren’t mine - they are added by RouterOS. If you have hybrid ports or don’t want this… you can still just add “static” (normal) entries for VLAN 42 and do what you want.
Solves the whole “make sure tagged=bridge is in /interface/bridge/vlan”. If you set /interface/vlan to listen on the bridge, it does automatically in 7.16beta1. Great work Mikrotik!
*) bridge - show invalid flag for ports that fails to be added to bridge (e.g. maximum port limit of 1024 is reached);
From this line we found out that there is a limit of maximum 1024 ports per bridge!
(now we see that that limit has been added to the documentation on gen 02 2024.)
We have a CCR1072 that we use to terminate a lot of layer 2 FTTH/FTTC lines. So we have a lot of VLAN interfaces that go to a single bridge and then out on an ethernet interface.
Currently the router is working flawlessly and with veeery low CPU usage, but we are approaching this 1024 limit.
Is there any way we can overcome this limit?
Thanks.
@Valerio5000
I already gave you the answer.
But don’t believe me.
Test it for yourself.
Well, there is a YouTube video by Toms from Mikrotik. He tells us this as a fact.
http://forum.mikrotik.com/t/v7-15rc-testing-is-released/175351/148
And 802.11r is a wireless standard. Of course it would be nice when MT would describe it in detail in their docs for their ROS specialities. But basically it is a standard implemention (by Qualcomm actually; as they use the manufacturer driver)
For ip>media, any chance to add support for sending metadata to the client? miniDLNA does this using NFO files. Otherwise, using a container will still be better.
IPv6 PD over PPPoE still not working. Mixing user prefixes for a while.
Jun/08/2024 08:53:12 dhcp,debug processing client:005056bf3ea9 iapd:0x2
Jun/08/2024 08:53:12 dhcp,debug binding belongs to other server: 005056bf3ea9 xxxx:xxxx:3:3001::/64
Jun/08/2024 08:53:12 dhcp,debug binding not updated
Jun/08/2024 08:53:12 dhcp,debug,packet send → fe80::16af:edd3:0:2%2d
Running CHR on amazon ec2: 7.15 broke ipv6, but it is working again in 7.16beta1.
lte ep06-e
After the update, the modem does not see the iccid of the SIM card, writes: transmission failed and does not connect
from 7.14 to 7.15 my ssh-exec mode will not authenticate anymore. Ive tried loading a new Pub and Pri key but still no luck.
What changed and will 7.16 introduce a fix or can someone help me out with a fix on it for 7.15?
Can confirm that my devices are now stable for the first time since the ax launch, so thats good news. Ipad Air2
Would be even better if I could fully enable FT on all 4 Radios, I still have to have one Radio with FT Disabled just for the device above.
While this is partially good news it obviously means no vlan-interface-counters for layer2 traffic only?
Also will those counters be exposed via SNMP?
thx!
hk
What’s new in 7.16beta2 (2024-Jun-12 12:03):
*) arm64 - increased reserved storage space for bootloader;
*) bgp - fixed BGP sessions missing vpnv6 afi;
*) bgp - fixed cluster-list and originator-id;
*) bridge - fixed typo in filter and NAT error message;
*) chr - added support for licensing over IPv6 network;
*) dhcpv4-server - added “class-id” parameter for DHCP server leases;
*) dhcpv4-server - fixed setting and getting “next-server” property;
*) dhcpv4-server - increased lease offer timeout to 120 seconds;
*) disk - added simple test command to test device and filesystem speeds (CLI only) (additional fixes);
*) disk - improved system stability;
*) dns - added support for DoH with adlist;
*) ethernet - fixed port speed downshift functionality for CRS354 devices;
*) firewall - added message when interface belonging to VRF is added in filter rules (additional fixes);
*) health - improved voltage measurements for RB912UAG-6HPnD device;
*) iot - added an option to delete default LoRa servers and a button to recover them if needed;
*) iot - added an option to log LoRa filtered packets;
*) ip/ipv6 - added multipath hash policy settings;
*) ip/ipv6 - warn user that reboot is required in order to properly apply changes under IP/Settings and IPv6/Settings menus;
*) ipsec - changed default dpd-interval from 2 minutes to 8 seconds and dpd-maximum-failures from 5 to 4;
*) ipv6 - fixed dynamic duplicate address showing when static address is already configured;
*) ipv6 - improved LL address generation process;
*) l2tp - improved system stability;
*) lte - fixed cases where LTE interface would take long time to become ready after bootup for Chateau 5G and Chateau 5G R16 (introduced in v7.15);
*) lte - fixed MBIM modem registration on the network (introduced in v7.16beta1);
*) modem - fixed modem firmware upgrade for Chateau 5G and Chateau 5G R16 (introduced in v7.15);
*) netinstall-cli - added support for multiple device install (additional fixes);
*) poe-out - upgraded firmware for SAMD20 PSE (AF/AT) controlled boards (the update will cause brief power interruption to PoE-out interfaces);
*) ppp - fixed dynamic queue default name (introduced in v7.15);
*) qos-hw - fixed incorrect per-port packet and byte cap (introduced in v7.16beta1);
*) queue - improved system stability;
*) route - fixed memory leak (introduced in v7.15);
*) route - fixed some missing route parameters when printing (introduced in v7.15);
*) routerboot - improved boot process (“/system routerboard upgrade” required);
*) sfp - fixed missing traffic after reboot with S-RJ01 module running at 10/100 Mbps rate on CCR2004-16G-2S+ device;
*) switch - fixed limited Tx traffic on Ethernet ports for CRS354 devices (introduced in v7.15);
*) system - added support for upgrade over IPv6 network;
*) system - improved watchdog and kernel panic reporting (additional fixes);
*) system - reduced RAM usage for ARM64 devices;
*) wifi-qcom - add spectral-scan and spectral-history tools (CLI only) (additional fixes);
*) winbox - added “Switch/QoS” menu for CRS3xx, CRS5xx, CCR2116 and CCR2216 devices;
*) winbox - added “Trace” column under “System/History” menu;
*) winbox - do not show “Last Logged In” and “Expire Password” when creating new system user;
*) winbox - fixed “Authority” property under “System/Certificates/Requests” menu;
*) winbox - fixed error when changing wifi interface settings in some rare conditions (introduced in v7.16beta1);
*) winbox - moved DHCPv6 Server “Allow Dual Stack Queue” property from General to Queues tab;
*) winbox - moved Switch menu tabs to individual menus;
*) wireless - allow to unset signal-range and ssid-regext properties for capsman access-list;