Recent content by Oniiz86

@Tech9 That is true but I was very surprised when I reported an issue with Custom Icons functionality that they broke before this model was deemed EoL & last November they released a firmware update within 2 weeks with this singular fix for the Custom Icons issue after I had reported it, I can't...

@wouterv I was wondering if you could confirm if your Media Bridge instability & AiMesh issues have been fixed with this 386_52062 firmware?

@fruitcornbread I was just wondering is that simply a typo as that "G1" is not present in the firmware notes?

@wouterv Do you feel it is best to avoid this firmware update due to the Media Bridge instability issues & UPnP no longer working properly?

Sure I understand that it's a completely different hardware platform 802.11n vs 802.11ac, I forgot to mention the RT-N66U shares the same firmware revision number 3.0.0.4.382_52745 as the RT-AC66U.

So it appears this firmware 3.0.0.4.382_52745 was released by accident or has proved to be unstable on the RT-N66U's hardware & will not be re-released? ASUS have advised on their website that firmware 3.0.0.4.382_52734 would be the last, the RT-AC66U shares the same firmware revision number as...

@wouterv Yes you are right, I just figured that since I just did a dirty upgrade to 386_51729 there could be some remnants from the previous 386_51722 firmware & as @Tech9 mentioned his RT-AC66U B1 with the latest 386_51729 firmware broke Custom Icons functionality.

@wouterv I was just curious if you could confirm that Custom Icons still works on your RT-AC68U with the latest 386_51729 firmware, I know you said you're not overly concerned by it but was wondering if another owner has no such issues?

@Tech9 Are you absolutely sure the Custom Devices Icon functionality is broken again as I got them to fix it in the previous November 26th 386_51722 firmware? Edit: I've just done a dirty upgrade to the 386_51729 firmware & can confirm that my Custom Icons are still present after a manual...

@banger I can confirm that the physical WPS button did factory reset with 386_51722 firmware, so it does appear that Asus fixed it at some point after Merlin's 386.14 firmware.

@banger Those are the release notes for 386.14 from July 2024 not the 386.14_2 release notes from November 2024. 386.14_2 (17-Nov-2024) - UPDATED: OpenVPN to 2.6.12. - CHANGED: Enabled Netfilter queue support for SDK6/SDK7 devices (patch by HiHat) - FIXED: Security issues in...

@banger Are you suggesting that WPS Reset via the GUI is broken for 386.14_2 or stock 386_51722 firmware or both?

@banger I'm not sure if you've seen @wouterv latest post regarding pinging requests successfully with stock 386_51722 firmware, he's seemingly confirmed that there aren't any issues with the latest stock 386_51722 firmware concerning ping requests.

@wouterv So it seems the 386_51772 firmware is not at fault, it appears to be a configuration issue for some strange reason but Merlin's 386.14_2 firmware has no such issues for @banger, @wouterv would you be able to test your W10 laptop if it pings ok after unblocking the firewall?

@banger So Asus broke the ability to ping with this 386_51722 firmware, that's disappointing, did you perform a hard factory reset before you went to Merlin's 386.14_2 firmware?