I have bought a second hand ac2 and I just installed it to test. To make sure, I need to use the old wireless package instead of wifi-qcom-ac? Using the the qcom I can’t see the multicast-helper option, only the enhance one like in ax2.
Thanks. I will try first with wifi-qcom-ac to see if the issue is related to ax devices. If cuts occurs using it, I will install the old wireless and see.
Received the second hand ac2 on Friday. Did a Netinstall of 7.18.2, along with wifi-qcom-ac, and loaded the same config that I use in my ax2 for my ISP, only changing the wifi bands from ax to ac/n to adapt to ac2.
No cuts! No pixelations! All is perfect, like using the Asus or the ISP router.
So…it seems that it should be a bug that affects devices with arm64 or wifi ax. Will report it to the opened ticket with support.
Glad to hear that! Some people in this forum seem to want ARM devices with 16MB flash, like the ac2, to “fade away” - despite the fact that these devices perform pretty well with the new wifi-qcom-ac driver.
After the results with ac2 test, I just did another test.
Installed back the ax2 with the same config as always for my ISP, BUT configured the wifi to use the AC/N bands in 5Ghz and 2,4Ghz respectively.
Again, NO CUTS, NO PIXELATION. Perfect!
So, the problem is clearly caused by the use of ax band. Something like multicast to unicast conversion, or igmp-proxy….do not work good when ax is active.
Could you elaborate?
I’m guessing you mean you set the Band setting to 5GHz AC and 2GHz N?
The Multicast conversion I would be able to try to test on an AX3.
I’m not running IGMP Proxy. I’m only running IGMP Snooping and none of the Wi-Fi interfaces are actually member ports of any group
Support want me to make some more tests. One of them is set the master wifi to ax and the slave (IPTV) one to ac.
I’ve created a test config to set the vAP in AC band, while the master uses ax config. But in Winbox I see in current channel that both master and virtual shows as ax. In Netspot app for Mac, I can see that both shows ac/ax (When only ax is set, they show as ax only).
It is possible to have ax on master and ac on slave?
Today support messaged me back about this issue and on 7.19rc1 i wasnt able to reproduce the Multicast issue.
I dont get any multicast frames on the wifi with multicast helper enabled.
Havent rechecked 7.18.1.
Will do in a few days on an ax2.
I was in contact with support too and they discovered that the cuts were due to an incompatibility with Mikrotik wifi and decoder wifi. They found some similarities in Chromecast. They even tried to get a similar decoder from a local ISP. Support is top at Mikrotik.
I have the decoder through ethernet now, and zero issues. Finally achieved to install an ethernet cable from first floor to ground. Now I have an ax3 as main router and the ax2 as a cap and switch on ground floor.
I just retested 7.18.1 with default config on an ax2.
I just enabled multicast enhance and nothing else and it was working perfectly!
On my sniffer i was seeing a lot of Mcast without Multicast Enhance.
And Literally 2 Multicast Packets from the ax2 with Multicast enhance turned on
They’re from neighbor discovery as its CDP and LLDP originating from the AX2 itself. But im not sure if you’re even “allowed” to unicast those frames or if that would break the protocol.
While as my ax3 still rocks the same config and its definitely working flawlessly now with rc1.
Theres a couple multicast related fixes in 7.19 so it might be related but cant really tell if i cant reproduce it now ^^
I am probably missing something and/or do not understand what an encoder is in this context but didn’t you say early in the topic, that connecting your TV box by ethernet cable did cause microcuts as well?
I have the same buffer issue with hAP AX3 connected on LAN cable. Still after enabling tons of options gets randomly buffering o my IPTV (Not operator, but Aliexpress one that worked perfectly on previous operator).
In the past, there were some users in Spain with same ISP having pixelation issues through ethernet. But now, all is fine with box connected through ethernet port. I think they fixed that issues with igmp-proxy refactored code introduced in 7.17?