Recent content by NSNE

Safari uses WebKit, a different rendering engine to Chrome, which has become the standard backend for a number of browsers. Because of Chrome's ubiquity, most developers tend to optimize for it. It was the same thing with Internet Explorer back in the day ("This site is best viewed in IE"). My...

My AX86U AiMesh node has been janky ever since updating to the long-overdue AX89X firmware. But it looks like some of the issues I mentioned in that AX89X thread (e.g., node flakiness, poor mesh client distribution, binds not being respected) were resolved with this AX86U update.

I upgraded from the most recent 9.x beta firmware using the Asus iOS app. It's been interesting. Background: I'm using the AX89X in AP mode as the primary AIMesh unit for two additional wired nodes: an AX86U and an AX88U. My router is an OPNsense box. I have a good 80 wireless clients. Since...

Following up: RAM usage dropped back down to 53% and has remained there for the past couple of days. The weaker signal that I was seeing on at least one desktop has since resolved itself and is now back to full bars. So I'm not really seeing anything of concern on .33699 firmware.

I upgraded to .33699 just now. The string at the end of firmware filename makes it seem like specialized release to address a specific issue: "he20_us_bdf_minus_1.5dB_1". Not sure what to make of that. No new features immediately jump out, but I have noticed that RAM usage is a good 4-5%...

I saw something similar to this on .33673 last night. I had two WiFi devices that could see the 5GHz network and attempted to connect to it, but upon re-connection the signal was unusually weak, there was no Internet access, and within seconds they'd be booted off the network. Because I needed...

I'm not seeing this issue on the latest beta firmware (32100). My fan is running around 1900rpm. Set to auto. Start is 45/75/90. Stop is 40/70/85.

Thanks for the heads up. Unfortunately (or fortunately?), it was already unchecked.

On the 388.32099 firmware I'm seeing older wireless clients having difficulty trying to connect. As in, they can't. Specifically, they're Logitech SqueezeBox Radios, which I believe are 802.11b. Anyone else seeing this behavior with older (ancient?) wireless clients?

Status report: After 8 days since the last reboot, RAM usage has climbed from 54% to 85%. [EDIT: Now at 86%.] This is generally as high as I allow it to get before rebooting. I can't risk any malfunctions that might arise if the RAM were to fill completely and crash the router.

Yes, the usage starts out at ~54% and will climb over ~1.5 weeks to 85%, which is the highest I’ve allowed it to go before rebooting. After rebooting yesterday I’m now at 63%, up from 54% immediately after boot. So, yes, it’s a clearly a memory leak, and I was reporting my experience so that...

The graph is static because I only had the GUI loaded for a few seconds before capturing the screenshot. I wanted to show current RAM usage levels in that screenshot, not longitudinal data.

I'm still seeing RAM usage climb to concerning levels over time (days). This was rebooted one week ago: Prior to these betas, RAM usage would hover around 52–54% indefinitely. This escalating RAM usage issue might be tied to running an endpoint on a permanent VPN connection (not using VPN...

This .22237 release has been nothing but hassle for me. All seemed okay at first, but I've been suffering random "offline" node errors for the past couple of weeks. It's terrible for home automation when your wireless devices keep losing their closest access point. Am reverting to .20558, which...

I will reiterate that _31307 still appears to have a memory leak. It is less severe than the previous version, but I am still seeing RAM usage climb steadily over multiple days. Use at your own risk, keep an eye on your RAM, and if you're going to insist on running beta software for the sake of...