unclebuk
Senior Member
How can I check, confirm existence of malware? Any advice? What would be the most obvious and usual symptoms, other than I am using old f/w?I don't know. You may have malware running already, I don't know.
How can I check, confirm existence of malware? Any advice? What would be the most obvious and usual symptoms, other than I am using old f/w?I don't know. You may have malware running already, I don't know.
I have never used AiProtection. Does it work...
How can I check, confirm existence of malware?
Oh, sounds like a big fat nothing-burger....LOL. I see the last merlin f/w security update was in 386.10 in March 2023 and prior to that was 386.5_2 in March 2022. 12 months separating any security updates, and not terribly impactful security issues. But please indicate otherwise as you see fit.Both conversations are unrelated to this firmware release thread. There was a malware infecting 384 firmware and it was never discovered how it gets in. It was discussed >3 years ago. AiProtection is discussed on a regular basis. What firmware you are going to run is entirely your choice. If you don't want to upgrade - don't upgrade.
But thanks for chiming in.
The better response would be to address a recently discovered vulnerability in Sept 2023 affecting 3 Asus routers including AC86U described as CVE-2023-39238, CVE-2023-39239, and CVE-2023-39240 with a very high potential for remote code execution and if in fact this know security breach and applicable patch has been added to recent merlin f/w updates? The dates of this [ASUS released patches that address the three flaws in early August 2023 for RT-AX55, in May 2023 for AX56U_V2, and in July 2023 for RT-AC86U] and the merlin changelog for 386.xx may infer this may not be the case and thus Merlin f/w for AC86U are susceptible to this securtiy flaw.As I said - on your router and your network you are free to do whatever you find is best. You can even disable the firewall if you want to. This doesn't affect me in any way. You asked for an opinion - you got my opinion. You're very welcome. For other unrelated to this firmware release questions - open separate threads and we may discuss.
The better response would be to address a recently discovered vulnerability
Is that your best advice?
Note that this topic is discussing the 386.12_6 firmware and issues with it. It appears you are asking about updating from a almost four year old firmware (384.19) to a firmware version released last year (386.10). Since your question doesn't appear to be specifically about 386.12_6, perhaps you should start a separate thread discussion since your question isn't really relevant to this firmware being discussed. Or review, if you haven't done so already, the 386.10 firmware discussion thread to see if there are any issues with the 386.10 firmware:I have two Asus routers, an AC88U (very good, stable) currently in storage and my current "ride" a 2017 model year AC86U on merlin 384.19 (refer to attached scr-shot) chugging along in a hot, under-ventilated non air conditioned room in hot and humid SE Asia and performance and reliability has been stellar.
The plastc housing has virtually disintegrated likely due to thermal stress's. I am pondering f/w upgrade to 386.10 despite very stable operation with current 384.19 with moderate use from 2 or 3 iPads, iPhones, a few laptops, TV's, android devices galore, guest network initiated along with OpenVPN Client and OpenVPN server operational. All is good, so I ask why I need to update the Merlin f/w?
After reading the reports of faulty and failing 86U's I question if I should leave well enough alone and motor on under current configurations.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!