Recently after doing firmware update on my RT-AX3000 my 5Ghz wifi always keep disconnecting for no reasons. Already set the channel to higher and set it as auto still the same problem, not happening on my 2.4ghz though.

Any idea what’s wrong?

I rely on 5Ghz for fast connection for wfh

Hi fox_shinoda,

May I know which firmware are you using?

The latest version is 3.0.0.4.386.45898 which uploaded yesterday.

Thank you

The last firmware upgrade I did was last week or 2 weeks ago if not mistaken.

Just updated to this one

Current Version : 3.0.0.4.386_45898-gfa90458

Will see if the problem still occurs

Issue still occurs, just noticed the uptime is like 3-4 minutes as if the whole router rebooted

Oct 8 17:34:39 rc_service: ntp 2294:notify_rc restart_diskmon
Oct 8 17:34:39 disk_monitor: Finish
Oct 8 17:34:39 disk monitor: be idle
Oct 8 17:34:40 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 06:CF:8C:07:C7:B3, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:34:40 wlceventd: wlceventd_proc_event(527): eth5: Auth 06:CF:8C:07:C7:B3, status: Successful (0), rssi:0
Oct 8 17:34:41 wlceventd: wlceventd_proc_event(556): eth5: Assoc 06:CF:8C:07:C7:B3, status: Successful (0), rssi:-30
Oct 8 17:34:42 inadyn[2319]: Update forced for alias , new IP#
Oct 8 17:34:43 inadyn[2319]: Updating cache for
Oct 8 17:34:43 ddns: ddns update ok
Oct 8 17:34:48 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 06:CF:8C:07:C7:B3, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:34:48 wlceventd: wlceventd_proc_event(527): eth5: Auth 06:CF:8C:07:C7:B3, status: Successful (0), rssi:0
Oct 8 17:34:48 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 06:CF:8C:07:C7:B3, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:34:48 wlceventd: wlceventd_proc_event(527): eth5: Auth 06:CF:8C:07:C7:B3, status: Successful (0), rssi:0
Oct 8 17:34:49 wlceventd: wlceventd_proc_event(556): eth5: Assoc 06:CF:8C:07:C7:B3, status: Successful (0), rssi:-31
Oct 8 17:34:56 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 06:CF:8C:07:C7:B3, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:34:56 wlceventd: wlceventd_proc_event(527): eth5: Auth 06:CF:8C:07:C7:B3, status: Successful (0), rssi:0
Oct 8 17:34:56 wlceventd: wlceventd_proc_event(556): eth5: Assoc 06:CF:8C:07:C7:B3, status: Successful (0), rssi:-30
Oct 8 17:35:02 crond[1634]: time disparity of 1803149 minutes detected
Oct 8 17:35:07 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 06:CF:8C:07:C7:B3, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:35:07 wlceventd: wlceventd_proc_event(527): eth5: Auth 06:CF:8C:07:C7:B3, status: Successful (0), rssi:-31
Oct 8 17:35:07 wlceventd: wlceventd_proc_event(556): eth5: Assoc 06:CF:8C:07:C7:B3, status: Successful (0), rssi:-31
Oct 8 17:35:19 wlceventd: wlceventd_proc_event(527): eth6: Auth 96:24:35:A0:4F:EA, status: Successful (0), rssi:0
Oct 8 17:35:19 wlceventd: wlceventd_proc_event(556): eth6: Assoc 96:24:35:A0:4F:EA, status: Successful (0), rssi:-57
Oct 8 17:35:21 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Oct 8 17:35:21 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Unspecified reason (1), rssi:-62
Oct 8 17:35:21 wlceventd: wlceventd_proc_event(527): wl0.1: Auth AC:F1:08:20:DF:54, status: Successful (0), rssi:-62
Oct 8 17:35:21 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc AC:F1:08:20:DF:54, status: Successful (0), rssi:-62
Oct 8 17:35:29 wlceventd: wlceventd_proc_event(527): eth6: Auth 3C:6A:A7:95:8E:C2, status: Successful (0), rssi:-59
Oct 8 17:35:29 wlceventd: wlceventd_proc_event(556): eth6: Assoc 3C:6A:A7:95:8E:C2, status: Successful (0), rssi:-59
Oct 8 17:35:48 wlceventd: wlceventd_proc_event(527): eth6: Auth E0:66:78:34:09:6E, status: Successful (0), rssi:-52
Oct 8 17:35:48 wlceventd: wlceventd_proc_event(556): eth6: Assoc E0:66:78:34:09:6E, status: Successful (0), rssi:-52
Oct 8 17:35:50 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:35:50 wlceventd: wlceventd_proc_event(527): wl0.1: Auth AC:F1:08:20:DF:54, status: Successful (0), rssi:0
Oct 8 17:35:50 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc AC:F1:08:20:DF:54, status: Successful (0), rssi:-64
Oct 8 17:36:09 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7396)]periodic_check AM 2:31
Oct 8 17:36:09 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7435)]do webs_update
Oct 8 17:36:12 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7453)]retrieve firmware information
Oct 8 17:36:12 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7468)]fimrware update check first time
Oct 8 17:36:12 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7501)]no need to upgrade firmware
Oct 8 17:36:35 wlceventd: wlceventd_proc_event(527): eth6: Auth 0E:ED:AC:CC:5A:AD, status: Successful (0), rssi:-58
Oct 8 17:36:35 wlceventd: wlceventd_proc_event(556): eth6: Assoc 0E:ED:AC:CC:5A:AD, status: Successful (0), rssi:-58
Oct 8 17:36:42 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-62
Oct 8 17:36:42 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:36:42 wlceventd: wlceventd_proc_event(527): wl0.1: Auth AC:F1:08:20:DF:54, status: Successful (0), rssi:-63
Oct 8 17:36:42 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc AC:F1:08:20:DF:54, status: Successful (0), rssi:-63
Oct 8 17:37:42 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-62
Oct 8 17:37:42 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:37:42 wlceventd: wlceventd_proc_event(527): wl0.1: Auth AC:F1:08:20:DF:54, status: Successful (0), rssi:0
Oct 8 17:37:42 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc AC:F1:08:20:DF:54, status: Successful (0), rssi:-64
Oct 8 17:38:40 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-62
Oct 8 17:38:40 wlceventd: wlceventd_proc_event(491): wl0.1: Deauth_ind AC:F1:08:20:DF:54, status: 0, reason: Unspecified reason (1), rssi:0
Oct 8 17:38:40 wlceventd: wlceventd_proc_event(527): wl0.1: Auth AC:F1:08:20:DF:54, status: Successful (0), rssi:-63
Oct 8 17:38:40 wlceventd: wlceventd_proc_event(556): wl0.1: Assoc AC:F1:08:20:DF:54, status: Successful (0), rssi:-63

This post has been edited by fox_shinoda: Oct 8 2021, 05:45 PM

Hi fox_shinoda,

You you send a feedback using the router GUI at the Administration->Feedback. PM me your email address used once done.

Thank you

Just monitor it again this morning, looks like the router still reboot itself every 2-3 hours 😅 I hope there is a better firmware suitable for my case. Didn’t really look into this before, but now it really affects my work from home productivity, dc while zoom meeting and dc while working on remote server

Try to perform a hard reset. Most of the time it's due to some settings issues.

https://www.asus.com/support/FAQ/1039078

Just reveived called from digi today said public IP only applicable to business fibre, so unable to get public IP for home fibre. Is it I can't access the VPN or ddns if I don't get public IP address? Any alternative way, can anyone advice?

you can't use ddns so cannot solution why you did change digi see you disappointed

you can't bypass due private ip very bad

mine unifi home fibre i still have public ip no problem i wont change other isp its waste and trouble and unstable

Digi provide a very good package therefore I switch from maxis to digi, speed and stability wise its OK just no public IP only.

lol Digi Provide a very good package look very bad package due no give public IP so you loss access public ip

good luck for Private IP for very bad Digi Package very bad

hi guys. i have issue about maximum speed.

im using asus mesh router xt8, 2unit.

one router (main) i put at lower ground, one router at 2nd floor. connecting each other using ethernet backhaul. Im using unifi 800mbps.

At LG floor i can get max wifi speed using phone as 700++mbps, but at the 2nd floor i only can get 300++mbps.

How and what i can do so i can get the same speed as LG floor maximum wifi speed?

Hi axce.lan,

Can you use the ASUS router APP to check which XT8 are you connect to when you do the speedtest?

And make sure the node show connected through ethernet backhaul.

If you have a laptop or PC near the router, can you plug a LAN cable to the XT8 LAN port and do a speedtest to see how much Mbps you are getting.

Thank you

Just had extra fan so stick it on at the back... make it cooler, maybe not necessary.

But AC86U seems better with fan thou

Thanks

FYI, Unifi has started migrating those with 100Mbps plan and below to private IPv4. Only those with 300Mbps and above will remain on Public IPv4.

ASUSmy, does asus DDNS and the VPN service support IPV6?

If no, is there any plan to implement it since unifi stops offering public IPV4 to 100mbps and below users



This post has been edited by yongtjunkit: Oct 13 2021, 09:07 PM

yes i know but i am on 100Mbps plan i still on Public IP i checked my router confirm its WAN IP is 175.13x.xx.xx

hi, may I know what are the steps needed if I want to upgrade my current unifi router to RT-AX3000? do i need to update to the latest firmware from the box first then only swap with the old router? tq

Hi yongtjunkit,

We are still testing the DDNS with IPv6, as for the VPN, not at the moment.

Thank you