What's new

[Official Release] AiMesh Firmware v3.0.0.4.384.20308 for All Supported Products

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

arthurlien

Very Senior Member
Version 3.0.0.4.384.203082018/02/0145.7 MBytes

ASUS Firmware version 3.0.0.4.384.20308
Bug fix
- Fixed GUI error on firmware update page.
The progress bar may always appear on firmware upgrade page after installed 3.0.0.4.384.20287.
If your router had this issue, you can manually reboot the router to solve this issue and enter the firmware upgrade page to install the latest firmware. Riden of NCC Group)
 
No AiMesh here yet, but firmware is running great. I used the check for upgrade in router and install was smooth. Thanks @arthurlien for being so active here. Much appreciated.
 
I will do the upgrade when I get back home. But seems this version only fixed the upgrade UI, still waiting for MAC address filtering and unexpected disconnection of STA fixes.
 
What is the Ai-Protection Signature Version?
After I re-initialize my main router, it's now 1.008, and it was 2054 before I reinitialize the router (if i remember correctly, I this merlin's had this issue due to the change of update channel? or typo? on the closed source ai-protection module).

Untitled.png
and these 2 message flood the logs
Feb 2 01:16:35 kernel: ERR[qos_start:3363] qos_wan or qos_lan is NULL, plz fix it!!!
Feb 2 01:16:35 kernel: ioctl_iqos_op_switch(1) fail!

solved by power cycle it and reset, maybe reinitialize button was the issue?

Also, I still encounter the firmware update page, but it might or might not happen on next firmware update.

here was the steps that I update my router, was done this way because I had to reboot my router due to other reason.

1. update 3100 via the auto update page after reboot. at this point, 3100 was the only one available.

2. after update, both 3100 and my 68u was both available @ firmware update page. 3100 was 20308 while 68u was still 10007. I then use the check firmware page, and did it couple time. Everything seem to be normal at this point. I no longer encounter the issue.

3. I then proceed to use the fireware update button to test the aimesh ability to push the firmware to the node.
it works as expected.

Then I encounter the firmware updating page, I did a reboot and it no longer have the problem.

I decided to still make note on this because it might still happening after updating firmware.

that's when I decided to reinitialize my router.
 
Last edited:
Small Bug on WPS Setting

My AiMesh Devices is as below on my Signature.

Using Wireless Explorer on Mac, I observed the following behaviour for WPS Settings

(1) AiMesh Router: RT-AC5300
  • WPS On / Off works as expected for All 3 Channels 2.4 GHz, 5.0 GHz (low), 5.0 GHz (high)
(2) AiMesh Nodes: RT-AC86U
  • WPS On / Off has no effect
  • WPS on 2.4GHz Channel is always ON
  • WPS on 5.0GHz Channel is always OFF
PS: I am aware that WPS has to be turn on when searching of AiMesh Node, I am turning off only after searching. It was reported in earlier firmware.
 
Anyone else having problems accessing NAS devices with this new update? I have two NAS devices I can access via their IP address to get to the admin pages, but can access the shared folders. This is a new issue with the latest firmware. I've tries rebooting my router and various PCs but no luck...

I'm running 3.0.0.4.384_20308 on a RT-AC88U in AIMesh mode with a RT-AC66UB1 runnibg 3.0.0.4.384_20308 as a node...

Really odd.
 
Anyone else having problems accessing NAS devices with this new update? I have two NAS devices I can access via their IP address to get to the admin pages, but can access the shared folders. This is a new issue with the latest firmware. I've tries rebooting my router and various PCs but no luck...

I'm running 3.0.0.4.384_20308 on a RT-AC88U in AIMesh mode with a RT-AC66UB1 runnibg 3.0.0.4.384_20308 as a node...

Really odd.
No issues here also using AC88U mesh and AC66U node have Netgear NAS working fine . presume you meant to say you couldn't access shared folders?
 
Bones, I had this - my Kaspersky AV for some reason saw the network as a new network (after firmware fiddling), and set the network to public without telling me. No NAS drives.

Went into Kaspersky, Settings, Protection, Firewall, Networks: ensure the network is "Local".
 
Bones, I had this - my Kaspersky AV for some reason saw the network as a new network (after firmware fiddling), and set the network to public without telling me. No NAS drives.

Went into Kaspersky, Settings, Protection, Firewall, Networks: ensure the network is "Local".

Thanks apotts

BitDefender was the culprit. They came out with a new version that includes VPN and it installed a loopback network adapter that was causing the problem.
 
I reset my AC66U B1 to factory defaults with the WPS button. Set the WiFi and log in info and was into the web gui. Changed the time server clicked ok and the log in screen came up but would not let me log back in with the user and password i had entered. Tried the above three more times with the same results. Finally was able to use a saved settings file which allowed me to log back in!

Sent from my P01M using Tapatalk
 
Generally running well on my AC86U and AC66U-B1 with the latter accepted as an AiMesh Node for the first time.

The only bug I've spotted is one I had in 10007 where if you edit a device in the device list sidebar (to modify the device icon etc), about 50% of the time it crashes the console session and I have to log back in to continue.
 
3 RT-AC68U update by firmware update button, but only the main and one of the node finish update, when I check firmware again it say that node which is on 20287 is latest firmware, reboot didn't fix it, at last I need to manually install the firmware for that node.
 
I've upgraded my 3x RT-AC68U setup via the single upgrade button (20287 -> 20308) in the web GUI. I had to reboot the 2 nodes manually because after the upgrade they wouldn't let any other wireless clients to authenticate. Both nodes are connected via ethernet cable and priority is set to wired.
 
Last edited:
Hey guys quick question.

I just setup AIMESH should I turn off Roaming assist that I had on and set at -70 for the base and AP mode I had before?

Thanks
Dan
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top