Recent content by kaktus

Sorry, I missed that part.. Did you set backhaul priority from auto to Ethernet?

I have the latest Asus stock on my mesh-node and gnuton Merlin on my main router. I have a rock solid (wireless) backhaul connection, even better then using stock on my main router. As mentioned (in this topic) you should disable the roaming assistant on the backhaul radio, I left the other...

I agree on that. My backhaul is almost as stable as it was with the 386 branch, with the main plus that it uses the full 160mhz bandwith.

I applied the the update this morning, but I also cannot find any release notes....

As long as the OpenVPN, WireGuard or local NAS (via USB) functionality exists I don’t see any reason to support AiCloud.

This release is stable for 3 days now on both nodes (with wireless backhaul). However the RX rate of the wireless backhaul is not as steady as with Merlin 3.0.0.4.388.8_2-gnuton1 (TX rate level is the same). But better safe than sorry in regards of the current AiCloud malware issues.

Me too, I reverted back from the latest Merlin to the latest stock. I do not use any of the AiCloud features, and also disabled the Wireguard server just to be sure and minimize external exposure. I hope Asus will provide the updated AiCloud and other closed source components soon, so I can...

I do not agree with you on the point of not being safer with the latest stock firmware. Asus has released new firmwares since the 4th of November in regards of this vulnerability. This vulnerability also affects the Merlin firmwares, since the vulnerability is likely to be part of the (closed...

Can CrashXRu confirm that this vulnerability only excists when you activate AiCloud or DDNS? To be on the safe side I switched from the latest Merlin to the latest stock Asus firmware (Nov 4, 2024).

That’s a pretty f***ed-up situation :-(. I hope there somebody can develop a method to restore bricked devices via serial connection.

Flashed this version on my (secondary) AiMesh node and until now it is working fine with my primary router (with latest Merlin).

I'm very curious if the Merlin releases are also affected with this security issue, because I cannot find anything on the Merlin github website.

Thanks for sharing this. After 13 days of uptime (with Merlin) I ran in to backhaul issues. When I r Thanks for the advise, I was not aware of the recommendation to leave the node on stock firmware.

I switched to the latest Merlin firmware and this works better, but still not as stable as the (386) 48706 version.

My xt8 also reports this message (at ~ 2:00am) were after the wireless backhaul fails and drops to 2,4GHz. I need to reboot the node to solve this issue for another 24 hours.