David Stidham
New Around Here
I upgraded to 386.2.6 ... same issue. Upgraded to 386.3 ... same issue. Performed factory reset and reconfigured unit in media bridge mode with a "clean slate" and still no change. Reverting back to 384.19 resolves the issue ... still. I did think to perform a screen capture AND saved a debug version of the settings while 386.3 firmware was installed. I did notice that the upload / download activity meter on the main UI page shows no activity under 386.3 when the speedtest was being performed, however, with 384.19 firmware in place, it does.I have similar challenges. I have an RT-AC68P, running in bridge mode. I connect to an RT-AC3200 running the 384.10.0 firmware as my network host router on one of the 5Ghz bands. I have been running this setup for over a year, through various firmware updates on all of my hardware.
I have used both the 386.1.0 and 386.1.2 releases, and with both my measured upload speed using Speedtest is sub-1Mbps. My download speeds remain as expected, in the 200-ish range. My service is 200/10 ... When I downgrade back to 384.19.0, my upload speeds return to the expected levels of 10-ish Mbps.
Additionally, I noticed my link rate on the v384.19.0 firmware is over 1100 Mbps, while on the v386.x firmware it dropped to the 700-range Mbps. My equipment positioning has not changed.
Lastly, when downgrading the firmware from 386 to 384, I have to perform a factory reset because the admin account credentials are somehow corrupted and I cannot log in. I power cycled the unit, and that didn't resolve this particular issue after the downgrade. Since I upgraded to 386.1.0, downgraded to 384.19.0, and then upgraded again to 386.1.2, and downgraded again to 384.19.0, I needed to factory reset both times. Once my RT-AC68 was running the 384.19.0 firmware version, everything went back to expected performance and behavior.
Unfortunately, I didn't think to perform any screen captures ... but ... I would be willing to go through the entire exercise again to capture screenshots to share if anyone needed them for support research into the firmware.
YES ... I did read @RMerlin commenting on WiFi and AiMesh being "closed source" ... sharing these details here regardless as continuity for my original observation that the issue persists with the 386.x firmware.
NOTE: I reverted to the Asus factory 3.0.0.4.386_43129 firmware, and all works as expected. Additionally, I installed the ASUS stock firmware 385.x and all works as expected with that, as well. Upon installing the ASUS stock firmware 386.x, I confirmed that the defect is in the base firmware code. I will open a ticket with Asus (and suggest all others with similar issues to do the same) and see what they can do about this.
**UPDATE 20210726** Ticket has been opened with ASUS regarding this issue in their stock firmware.
Last edited: