I have the XT8 system, a really good looking system. But having issues with the connection between router and nod. Everything is fine for a while, GREAT connection at 5ghz.. then from nowhere it drops to 2,4ghz and a weak signal... When I check wifi with any analyzer app my dBm is -40 to -55 witch is really good. So I dont understand the drop... Now I tried the RC2 build.. it gave me hope for 2hours.. then the drop came back again and weak signal. I rip my hair off soon or my family will kill me...
Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0
- Status
OzarkEdge
Part of the Furniture
Tip: This is a beta firmware discussion. You should start your own thread to discuss your issue separately.
OE
Sorry it was just ment for feedback to the RC2 build.
I tried forcing 2nd 5GHz radio to use 80MHz only. Ironically, one of my 2.4-only clients stops working!
Can't really tell what I'm doing wrong! Even default config doesn't use 80MHz.
Hopefully my ticket to Asus will get some answer.
Yeap, I got both 5GHz radio to be again part of a single SSID, with SC. But my GT-AC5300 refuses to use 80MHz even before adding the node. Something is weird and I can't figure out what!
I tried transferring some pictures from camera's SD card. With 20MHz channels took hours! 3-4MBps! What used to be 20MBps.
Hmmm
Another PS: manually setting both 5GHz channels, I managed to have both of them on 80MHz. Back to great wi-fi speed, a consistent 610-620mbps over wi-fi.
Speed to/from router-node also great, close to 1G.
Still weird how/why they changed the automatic channel selection. It used to be great.
Last edited:
I managed to get 80 MHz working. You need to change Channel bandwidth to 80 MHz and manually pick channel as well.
sanke1
Senior Member
Wife needs internet the most when we are about to upgrade the router’s firmware.Thanks for the confirmation! That pays for my time and trouble... with my wife when I take our network down for a beta test when she needs it and I'm suppose to be doing a ton of other things... like updating my estate plan.
OE
PS: I always manually select 5Ghz channel 40 and set width to 160. These are literally the only 2 settings I choose for my RT-AX88U. Never faced wireless issues with my model.
@thiggins
Nice forum update.
Last edited:
I've ran this RC2 on my three node XT8 setup for 24 hours now. However, the router randomly reboots (8 times today..) and a crashlog is generated in systemlog. I have seen random reboots on other fw's, but never with a crashlog generated. Lots of promise, but not yet mature. I can provide the crashlog output if wanted.
SloPoke
Occasional Visitor
Running the RC2 on three XT8's also, all using Ethernet backhaul. Was that button to enable Ethernet Backhaul also in the ASUS firmwares and I just missed it? Once enabled it allows Tri-Band Smart Connect and gives all 3 radios the same SSID. I though I might be able to get the "enable 160MHz" checkbox back on the 5GHz-2 radio, but no luck. This checkbox was there in my out-of-the box firmware 3.0.0.4.386_24926, but as soon as I updated to a more recent firmware it disappeared. It also disappeared when I added the XT8 mesh node. I'm in Canada so it should be available, despite ASUS support telling me it is restricted in my country.
Another observation: WPA2/WPA3-Personal authentication is enabled, but I don't see WPA3 being offered in a survey, and my WPA3 capable devices still connect using WPA2.
Another observation: WPA2/WPA3-Personal authentication is enabled, but I don't see WPA3 being offered in a survey, and my WPA3 capable devices still connect using WPA2.
ASUSWRT_2020
Regular Contributor
@JoWa Please send the feedback in "Administration --> Feedback". It will send useful logs for debugging.
It's like a soap opera for me.
Automatic channels are selecting 20MHz. Manual channels are using 80MHz and it's all good, speed-wise.
But I have a device that needs to be online. And for some weird reasons it disconnect itself from the network like this:
Jul 20 14:59:00 wlceventd: wlceventd_proc_event(505): eth6: Auth 84:F3:EB:83:9F:B3, status: Successful (0)
Jul 20 14:59:00 wlceventd: wlceventd_proc_event(534): eth6: Assoc 84:F3:EB:83:9F:B3, status: Successful (0)
Jul 20 14:59:35 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 84:F3:EB:83:9F:B3, status: 0, reason: Disassociated due to inactivity (4)
Jul 20 14:59:35 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 84:F3:EB:83:9F:B3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul 20 15:00:06 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 84:F3:EB:83:9F:B3, status: 0, reason: Class 3 frame received from nonassociated station (7)
It makes no sense to me!
I've submitted feedback, it's my 4th. I got no automatic reply to my tickets. Hopefully somebody is looking at it.
Automatic channels are selecting 20MHz. Manual channels are using 80MHz and it's all good, speed-wise.
But I have a device that needs to be online. And for some weird reasons it disconnect itself from the network like this:
Jul 20 14:59:00 wlceventd: wlceventd_proc_event(505): eth6: Auth 84:F3:EB:83:9F:B3, status: Successful (0)
Jul 20 14:59:00 wlceventd: wlceventd_proc_event(534): eth6: Assoc 84:F3:EB:83:9F:B3, status: Successful (0)
Jul 20 14:59:35 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 84:F3:EB:83:9F:B3, status: 0, reason: Disassociated due to inactivity (4)
Jul 20 14:59:35 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 84:F3:EB:83:9F:B3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul 20 15:00:06 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind 84:F3:EB:83:9F:B3, status: 0, reason: Class 3 frame received from nonassociated station (7)
It makes no sense to me!
I've submitted feedback, it's my 4th. I got no automatic reply to my tickets. Hopefully somebody is looking at it.
Ryu Connor
Regular Contributor
This 386 firmware has the same problem as the older 385 branch on the RT-AC88U in Media Bridge mode. It causes the system to crash over and over and over again.
Your QA department is not testing Media Bridge mode. No steps are necessary to duplicate this other than simply using Media Bridge mode.
It's so unstable I can't even send this via the Feedback form in the firmware.
Your QA department is not testing Media Bridge mode. No steps are necessary to duplicate this other than simply using Media Bridge mode.
It's so unstable I can't even send this via the Feedback form in the firmware.
Code:
Jul 20 11:14:17 rc_service: psta_monitor 369:notify_rc restart_wlcmode 0
Jul 20 11:14:17 FTP Server: daemon is stoped
Jul 20 11:14:18 Samba Server: smb daemon is stoped
Jul 20 11:14:18 kernel: gro disabled
Jul 20 11:14:18 kernel: rtk port_phyEnableAll (off) ok
Jul 20 11:14:26 kernel: rtk port_phyEnableAll (on) ok
Jul 20 11:14:26 RT-AC88U: start httpd:80
Jul 20 11:14:26 rc_service: psta_monitor 369:notify_rc restart_wireless
Jul 20 11:14:28 httpd: Succeed to init SSL certificate...80
Jul 20 11:14:39 rc_service: psta_monitor 1012:notify_rc restart_wlcmode 1
Jul 20 11:14:39 FTP Server: daemon is stoped
Jul 20 11:14:39 Samba Server: smb daemon is stoped
Jul 20 11:14:39 kernel: gro disabled
Jul 20 11:14:40 kernel: rtk port_phyEnableAll (off) ok
Jul 20 11:14:48 kernel: rtk port_phyEnableAll (on) ok
Jul 20 11:14:48 RT-AC88U: start httpd:80
Jul 20 11:14:50 httpd: Succeed to init SSL certificate...80
Jul 20 11:16:59 rc_service: psta_monitor 1012:notify_rc restart_wlcmode 0
Jul 20 11:16:59 FTP Server: daemon is stoped
Jul 20 11:16:59 Samba Server: smb daemon is stoped
Jul 20 11:16:59 kernel: gro disabled
Jul 20 11:17:00 kernel: rtk port_phyEnableAll (off) ok
Jul 20 11:17:08 kernel: rtk port_phyEnableAll (on) ok
Jul 20 11:17:08 RT-AC88U: start httpd:80
Jul 20 11:17:09 rc_service: psta_monitor 1012:notify_rc restart_wireless
Jul 20 11:17:11 httpd: Succeed to init SSL certificate...80
Jul 20 11:17:22 rc_service: psta_monitor 1576:notify_rc restart_wlcmode 1
Jul 20 11:17:22 FTP Server: daemon is stoped
Jul 20 11:17:22 Samba Server: smb daemon is stoped
Jul 20 11:17:22 kernel: gro disabled
Jul 20 11:17:23 kernel: rtk port_phyEnableAll (off) ok
Jul 20 11:17:31 kernel: rtk port_phyEnableAll (on) ok
Jul 20 11:17:31 RT-AC88U: start httpd:80
Jul 20 11:17:33 httpd: Succeed to init SSL certificate...80
Jul 20 11:19:06 rc_service: psta_monitor 1576:notify_rc restart_wlcmode 0
Jul 20 11:19:06 FTP Server: daemon is stoped
Jul 20 11:19:06 Samba Server: smb daemon is stoped
Jul 20 11:19:06 kernel: gro disabled
Jul 20 11:19:06 kernel: rtk port_phyEnableAll (off) ok
Jul 20 11:19:14 kernel: rtk port_phyEnableAll (on) ok
Jul 20 11:19:15 RT-AC88U: start httpd:80
Jul 20 11:19:15 rc_service: psta_monitor 1576:notify_rc restart_wireless
Jul 20 11:19:17 httpd: Succeed to init SSL certificate...80
Jul 20 11:19:26 rc_service: psta_monitor 1983:notify_rc restart_wlcmode 1
Jul 20 11:19:26 FTP Server: daemon is stoped
Jul 20 11:19:26 Samba Server: smb daemon is stoped
Jul 20 11:19:26 kernel: gro disabled
Jul 20 11:19:28 kernel: rtk port_phyEnableAll (off) ok
Jul 20 11:19:36 kernel: rtk port_phyEnableAll (on) ok
Jul 20 11:19:36 RT-AC88U: start httpd:80
Jul 20 11:19:38 httpd: Succeed to init SSL certificate...80Yeah, I think the consensus is that if you truly need media bridge mode, just use the Tomato firmware, assuming a build is available for your router. I have done this personally, and it works perfectly (RT-N16 and RT-AC68P).
Edit: Another alternative proposed by some is to stay on Asus/Merlin firmware, and use AP mode: if you have no clients connected to that node wirelessly (think hidden or simply unused SSIDs), it effectively acts the same as media bridge mode.
Last edited:
RainGater96
Regular Contributor
I am new to this beta process and I read that the updates will not happen automatically once I am on 9.0.0.4.386_38936. Are all the beta builds posted here and have to keep an eye on it? I searched but couldn't find any official ASUS beta site?
I made a backup of the current config in case if I don't like it, I can revert back. But, so far it looks very good on RT-AC68U.
Also, reverting the firmware is to just upload the latest stable release (RT-AC68U_3.0.0.4_385_20630-ged5e4c3) and restore the config? Is that it? Thanks in advance for any and all replies.
I made a backup of the current config in case if I don't like it, I can revert back. But, so far it looks very good on RT-AC68U.
Also, reverting the firmware is to just upload the latest stable release (RT-AC68U_3.0.0.4_385_20630-ged5e4c3) and restore the config? Is that it? Thanks in advance for any and all replies.
Beta updates will be posted here on the forums. Asus has no public beta site (hence their use of these forums).
That should be it, yes. Note that it's possible that for some models, after a downgrade you might be unable to log back into your router. If that happens, do a factory default reset, reconfigure it, and then restore your saved backup. I think the RT-AC86U for instance might have switched to encrypted password storage, which would prevent you from logging in after a downgrade.
After reading the logs, I found all my 2.4GHz-only clients are seeing "Disassociated due to inactivity (4)". How this can be avoided? I don't know, hopefully Asus will read this and can explain what is happening and why it's happening.
Unfortunately one of my clients never tries to re-authenticate once it's kicked out. Clearly a bad client behavior and I'm working with the vendor.
Unfortunately one of my clients never tries to re-authenticate once it's kicked out. Clearly a bad client behavior and I'm working with the vendor.
Smokindog
Senior Member
Do you know if the ultimate goal is to have this GA for ALL routers currently supporting AiMesh?
TIA!
TIA!
I am seeing this on 385 as well on an AC68U.
I don't know what Asus' plans are.
RainGater96
Regular Contributor
I am seeing this now at various intervals since I flashed the beta this morning. Btw, I bleeped out the mac address. I setup the DHCP lease to expire in 4 hours and maybe, it's too aggressive?
Jul 20 12:36:56 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 12:51:09 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 17:03:14 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 17:56:14 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Disassociated due to inactivity (4)
Jul 20 18:12:20 syslog: wlceventd_proc_event(469): eth1: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 18:14:18 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason
Jul 20 18:53:51 syslog: wlceventd_proc_event(469): eth1: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 12:36:56 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 12:51:09 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 17:03:14 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 17:56:14 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Disassociated due to inactivity (4)
Jul 20 18:12:20 syslog: wlceventd_proc_event(469): eth1: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
Jul 20 18:14:18 syslog: wlceventd_proc_event(469): eth2: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason
Jul 20 18:53:51 syslog: wlceventd_proc_event(469): eth1: Deauth_ind xx(mac address), status: 0, reason: Unspecified reason (1)
RainGater96
Regular Contributor
In the wireless log (RT-AC68U), I see that SNR is 0 for both bands. Not sure why... Is it a bug?
5GHz:
RSSI: 0 dBm SNR: 0 dB noise: -92 dBm Channel: 149/80
2.4 GHz:
RSSI: 0 dBm SNR: 0 dB noise: -88 dBm Channel: 6l
I see RSSI is in the -30dBm to -60dBms for most of the devices and that is good.
5GHz:
RSSI: 0 dBm SNR: 0 dB noise: -92 dBm Channel: 149/80
2.4 GHz:
RSSI: 0 dBm SNR: 0 dB noise: -88 dBm Channel: 6l
I see RSSI is in the -30dBm to -60dBms for most of the devices and that is good.
Last edited:
- Status
Similar threads
- Locked
Similar threads
| Thread starter | Title | Forum | Replies | Date |
|---|---|---|---|---|
| D | ASUSWRT 4.0 - What did I get wrong (this time..) | ASUSWRT - Official | 1 | |
| M | Odd ASUSWRT handling of USB drives? | ASUSWRT - Official | 9 |
Similar threads
-
D
-
Latest threads
-
-
Kamoj Kamoj Addon 5.5 b47 for Netgear R7800/R8900/R9000 with Voxel FW- Started by kamoj
- Replies: 1
-
Release ASUS GT-BE19000 Firmware version 3.0.0.6.102_39244 (2026/02/04)
- Started by oxide
- Replies: 0
-
Trying to install DD-WRT on Asus RT-ACRH13- Started by Miaowminx
- Replies: 1
-
Support SNBForums w/ Amazon
If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!
Sign Up For SNBForums Daily Digest
Get an update of what's new every day delivered to your mailbox. Sign up here!