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

[VANT]

Firmware version 3.0.0.4.384_20467
- Release Note -

Security fixes and improvements:
- Fixed information disclosure vulnerability. Thanks to Haitian Xiang and Fang Wang.
- Supported Let's encrypt to help get free Certificate Authority (CA). To enable this feature, the router needs to obtain public IP from ISP.

New:
- Added IPSec VPN server.
- Added Stuff-Fibre IPTV profile.

Bug fixes and improvements:
- Fixed AiMesh compatibility issues.
- Fixed traffic monitor bugs.
- Fixed certificate buffer issue for OpenVPN.
- Fixed duplicated clients on the network map.

 

[VANT]

and first bug

Router not remember when i set week in DST time zone changes starts and DST time zone changes ends. I set 4th and press Apply, but after this, week value is back to default. Look at the picture:
I set my values:

after "Apply" back to default

i sent feedback to Asus

VANT

 

[RMerlin]

and first bug

Router not remember when i set week in DST time zone changes starts and DST time zone changes ends. I set 4th and press Apply, but after this, week value is back to default. Look at the picture:
I set my values:

after "Apply" back to default

i sent feedback to Asus

VANT

@arthurlien, I sent Channer a fix for this last week (it's a bug in the Javascript code of that page). Can you see if that fix made it to the webui team? If not, I can send you the required fix so you can forward it to the appropriate dev.

 

[arthurlien]

@arthurlien, I sent Channer a fix for this last week (it's a bug in the Javascript code of that page). Can you see if that fix made it to the webui team? If not, I can send you the required fix so you can forward it to the appropriate dev.

Will check with team, thanks.

我從使用 Tapatalk 的 ASUS_Z012DA 發送

 

[arthurlien]

@arthurlien, I sent Channer a fix for this last week (it's a bug in the Javascript code of that page). Can you see if that fix made it to the webui team? If not, I can send you the required fix so you can forward it to the appropriate dev.

@RMerlin, Already Fixed. it will be release in later release. (next or newer maybe)

 

[RMerlin]

@RMerlin, Already Fixed. it will be release in later release. (next or newer maybe)

Cool, I guess I sent it too late for inclusion in 20467.

 

[Richard Li]

Was just hoping/dreaming, that by, not being able to connect to the ASUS firmware update servers via the router web GUI, that maybe a new AiMesh firmware was being released and that the ASUS servers were being updated with a newer AiMesh firmware release. But my dream was wrong, expecting too much too soon from ASUS, I am now again, able to connect to the ASUS firmware updates server/s via the router web GUI and as per usual, on checking, both router and nodes, ALL are on the latest firmwares. Sad....

So, still no new AiMesh firmware available from ASUS...

ASUS are Toooooooooo, Slowwwwwwwww with a firmware upgrade for AiMesh. Why? You would think for a new marketing tool, it should take some priority.

Reading through the Aimesh Marketing info, ASUS always use the word "RELIABLE', seriously, based on what? I for one, know, it can't be based on AiMesh nodes constantly going 'offline'.

ASUS, please Help us AiMesh supporters (I am one), (new firmware), for those users that are still using AiMesh and working with AiMesh.

I think they need some more time to put up a stable new release, I am still working with them to resolve some stability issue after enabling MAC address filtering.

 

[Richard Li]

I have been managing beta-tests all my working life.
I would have been extremely happy with so many beta- testers, joined in a forum like this.

For Asus it is a golden opportunity to release beta firmware in this forum (so no official firmware) and ask testers to report any issue.
Of course only manual update is possible, but that is no issue for all of us.

I don't understand why Asus leaves this possibility untouched. So many testers,so many specialists, free of charge ...

Well, I have been helping to test out several beta version already. Ha Ha.

 

[Flying Dutchman]

Well, I have been helping to test out several beta version already. Ha Ha.

And, found a lot of bugs?

 

[Richard Li]

And, found a lot of bugs?

Mainly working on Wifi dropping and MAC address filtering problems.

 

[Quad80]

Mainly working on Wifi dropping and MAC address filtering problems.

When you say wifi drops, what exactly are you experiencing? I just last night started seeing my node randomly drop wifi for an instant, which kicks whatever clients are on it. I have a wifi cam monitor and often use Netflix when connected to my node. Both video signals will die (one is on 2.4, the other on 5GHz). I can manually reboot the client software pretty much instantly, but it's annoying to have to do it. I haven't had this issue until last night. I rebooted the node this morning and still seem to be having some issues, but am still testing it by letting Netflix run on my tablet to see if/when it will stop. I physically saw my tablet wifi icon disappear when this happened one time, which came right back, but it was enough to disrupt the stream so I had to manually reconnect Netflix. I didn't/don't seem to have this issue when connected directly to the router.

Dunno why it started doing this, but if it keeps up, I'm gonna start everything from scratch first chance I get. I was hoping the new firmware would hit and I'd just update and do a factory reset then, since that seems to have a bug fix for duplicate client listings in the network map, but I haven't seen it come for the RT-AC3100 yet. I took a look at the logs in the UI, but I'm not seeing anything that looks off. I may not be looking in the right place, though. Just wondering if what I'm seeing is the same as what you're seeing, and if so, if there's anything I can provide that might shed some light into the matter.

 

[AlphaGator]

When you say wifi drops, what exactly are you experiencing? I just last night started seeing my node randomly drop wifi for an instant, which kicks whatever clients are on it. I have a wifi cam monitor and often use Netflix when connected to my node. Both video signals will die (one is on 2.4, the other on 5GHz). I can manually reboot the client software pretty much instantly, but it's annoying to have to do it. I haven't had this issue until last night. I rebooted the node this morning and still seem to be having some issues, but am still testing it by letting Netflix run on my tablet to see if/when it will stop. I physically saw my tablet wifi icon disappear when this happened one time, which came right back, but it was enough to disrupt the stream so I had to manually reconnect Netflix. I didn't/don't seem to have this issue when connected directly to the router.

Dunno why it started doing this, but if it keeps up, I'm gonna start everything from scratch first chance I get. I was hoping the new firmware would hit and I'd just update and do a factory reset then, since that seems to have a bug fix for duplicate client listings in the network map, but I haven't seen it come for the RT-AC3100 yet. I took a look at the logs in the UI, but I'm not seeing anything that looks off. I may not be looking in the right place, though. Just wondering if what I'm seeing is the same as what you're seeing, and if so, if there's anything I can provide that might shed some light into the matter.

Same exact thing happens to me. Just randomly kicks off all clients and the log shows this:

Mar 16 21:13:46 kernel: SHN Release Version: 2.0.1 3529123_patch
Mar 16 21:13:46 kernel: UDB Core Version: 0.2.14 r3529123
Mar 16 21:13:47 kernel: sizeof forward pkt param = 192
Mar 16 21:14:02 rc_service: bwdpi_check 410:notify_rc start_firewall
Mar 16 21:14:02 miniupnpd[14308]: shutting down MiniUPnPd
Mar 16 21:14:02 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Mar 16 21:14:03 miniupnpd[15622]: version 1.9 started
Mar 16 21:14:03 miniupnpd[15622]: HTTP listening on port 43092
Mar 16 21:14:03 miniupnpd[15622]: Listening for NAT-PMP/PCP traffic on port 5351

 

[Quad80]

Same exact thing happens to me. Just randomly kicks off all clients and the log shows this:

Mar 16 21:13:46 kernel: SHN Release Version: 2.0.1 3529123_patch
Mar 16 21:13:46 kernel: UDB Core Version: 0.2.14 r3529123
Mar 16 21:13:47 kernel: sizeof forward pkt param = 192
Mar 16 21:14:02 rc_service: bwdpi_check 410:notify_rc start_firewall
Mar 16 21:14:02 miniupnpd[14308]: shutting down MiniUPnPd
Mar 16 21:14:02 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Mar 16 21:14:03 miniupnpd[15622]: version 1.9 started
Mar 16 21:14:03 miniupnpd[15622]: HTTP listening on port 43092
Mar 16 21:14:03 miniupnpd[15622]: Listening for NAT-PMP/PCP traffic on port 5351

I'm not seeing anything like that in my system log. In fact, I'm not seeing much of anything.

Mar 17 08:00:41 dnsmasq-dhcp[349]: Ignoring domain bc.local for DHCP host name BCCES31-HP

This is repeated over and over. This is definitely my work laptop, and from what I can tell, it means it's trying to do some kind of connection to their local network, but can't do it because I'm not properly joined to it, and thus this can be ignored (per this thread: https://www.snbforums.com/threads/rt-ac66r-general-log-question.10162/#post-170460).

Everything else (and there's not much else) appears to be UPnP related, or something like this:

Mar 16 12:40:07 kernel: Register interface [wds1.4] MAC: [XXXXXXXXXXXXX]

I can't see anything that would indicate a problem for connections dropping. When I had this problem over night on 14-15 March, all I see is the "ignoring domain" log entry over and over. I haven't had the dropped client issue since yesterday evening, after a reboot of the node. I had Netflix playing all night on my tablet to get a better idea of if/when it would crap out (I could just log the time of when the Netflix show stopped), but neither my wifi monitor nor Netflix dropped, and as of this morning (13+ hours since last noted drop), it's all good.

Unlikely that's of much help, but there it is.

 

[SeeSawSam]

For those who read this forum while sleepy, the latest firmware is discussed here... https://www.snbforums.com/threads/rt-ac86u-3-0-0-4-384-20467.45385/

 

[indark]

For those who read this forum while sleepy, the latest firmware is discussed here... https://www.snbforums.com/threads/rt-ac86u-3-0-0-4-384-20467.45385/

20467 only apply to ac86u; 3100/5300 are on 20379, and rest are on 20308 I believe.
just check for my 3100 and 68u, did not see any new firmware yet

 

[AlphaGator]

My AC5300 AiMesh router just went down and there is a core dump in the log. I am not sure what to make of it. Seems to be fine after a reboot.

Is there a particular line I should look for in the core dump to diagnose what happened?

 

[arthurlien]

My AC5300 AiMesh router just went down and there is a core dump in the log. I am not sure what to make of it. Seems to be fine after a reboot.

Is there a particular line I should look for in the core dump to diagnose what happened?

Please send feedback with system log, when the core dump happened.

我從使用 Tapatalk 的 ASUS_Z012DA 發送

 

[AlphaGator]

Please send feedback with system log, when the core dump happened.

我從使用 Tapatalk 的 ASUS_Z012DA 發送

Unfortunately I cannot use the Feedback feature...it fails to send suggesting my ISP blocks the port.

I did email it to them as part of Service No: N180359924

 

[Richard Li]

When you say wifi drops, what exactly are you experiencing? I just last night started seeing my node randomly drop wifi for an instant, which kicks whatever clients are on it. I have a wifi cam monitor and often use Netflix when connected to my node. Both video signals will die (one is on 2.4, the other on 5GHz). I can manually reboot the client software pretty much instantly, but it's annoying to have to do it. I haven't had this issue until last night. I rebooted the node this morning and still seem to be having some issues, but am still testing it by letting Netflix run on my tablet to see if/when it will stop. I physically saw my tablet wifi icon disappear when this happened one time, which came right back, but it was enough to disrupt the stream so I had to manually reconnect Netflix. I didn't/don't seem to have this issue when connected directly to the router.

Dunno why it started doing this, but if it keeps up, I'm gonna start everything from scratch first chance I get. I was hoping the new firmware would hit and I'd just update and do a factory reset then, since that seems to have a bug fix for duplicate client listings in the network map, but I haven't seen it come for the RT-AC3100 yet. I took a look at the logs in the UI, but I'm not seeing anything that looks off. I may not be looking in the right place, though. Just wondering if what I'm seeing is the same as what you're seeing, and if so, if there's anything I can provide that might shed some light into the matter.

I have some procedures that can help the AiMesh to operate more stable. After changing any settings, I just reboot the nodes first, then followed by rebooting the main router/ap.

 

[arthurlien]

Unfortunately I cannot use the Feedback feature...it fails to send suggesting my ISP blocks the port.

I did email it to them as part of Service No: N180359924

send email to router_feedback@asus.com with your log.