No issues with IGMP Snooping here using RB4011 and a couple of HAP AC2 devicesIGMP Snooping not work correct with this release.
4x rb2011, 1x CRS106 and 1x HeX
After some minutes the MDB-table is empthy and the multicast flood to all ports :(
Try different settings, not help.
Don't expect rc in for long time, they first need to include all functionality and have that tested for some time.Lets hope to see 7.1 b3 or porbably 7.1 rc tomorrow xD
Is this high on the todo list?There is no multicast package, it is now part of system package, however IGMP-Proxy is not available in ROSv7 at the moment.
There is no v7This is already done in v7Please add IEEE 802.1AE AKA MACSEC to Router & SwitchOS.
There is as you can see at the top of this page:
BETA Testing and Feature Suggestions for the next RouterOS release (ROS v7)
Why not, holds the same informational value: nothingIn that case, please do not say V7 but instead say: Some version we might release in the (probably distant) future
Exactly my point. The beta with iPhone fixes is not public yet. Please wait a little bit. it's being released today
Will the new driver appear in version 6.X or do we need to wait for the legendary version 7?You are right, that MikroTik made wireless driver doesn't have Wave2 support, so new chipset benefits are not there. We are working on a new driver.
Strange, all works fine here after upgrading to rc64Same problem here, I updated from rc51 to rc64 and now the mikrotik does not seems to forward ipv6 packets anymore.I updated to rc64, but it seems I can not communicate with ipv6. There was no problem with at least rc56.
Then why when upgrading from version 6.42rc20 to version 6.42rc27 the router again ceased to give signs of life?No, only if older version was 6.42rc17 - 6.42rc24
No, only if older version was 6.42rc17 - 6.42rc24
6.42rc24 ....................................... 6.42rc27 how long will this last?
So not gonna happen at all since v6 seems to be te last version for this century given the speed of development.Not gonna happen before v7 due to kernel limitations.
For folks having trouble with IPsec in latest RCs, change your peer generate policy from port-strict to port-override. Support says they are working on a fix for this, but that was enough to get it working for me.