What's new

RT-AC5300: Cannot find current or new firmware

  • 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!

Very satisfied since the first 384.18 Alpha 1, and the later Alpha versions and Beta 1 are noticeably better still (a more responsive network experience).
 
Installing 384.18 Beta is absolutely a no brainer on the RT-AC5300 as L&LD already made clear.
Make sure you follow his guidance on a nuclear and M&M configuration (see the link in his signature above) and go for it. If you follow the installation instructions you will be really impressed with what the AC5300 delivers.
 
Thanks L&LD and SheikhSheikha!

I will go through that in the evening after work, since I am currently working over a tethered hotspot of my mobile phone. Since flashing the router (I did a firmware reset before flashing) with Merlin, all of my devices get constantly dropped of the wifi, so there is no chance to work :(
But I also didn't see/notice L&LD's instructions...

Jun 22 10:32:40 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:32:41 syslog: WLCEVENTD wlceventd_proc_event(449): wl0.1: Assoc 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:32:46 syslog: WLCEVENTD wlceventd_proc_event(386): wl0.1: Deauth_ind 7C:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 22 10:32:46 syslog: WLCEVENTD wlceventd_proc_event(401): wl0.1: Disassoc 7C:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 22 10:32:48 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:32:48 syslog: WLCEVENTD wlceventd_proc_event(449): wl0.1: Assoc 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:32:57 syslog: WLCEVENTD wlceventd_proc_event(386): wl0.1: Deauth_ind 7C:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 22 10:33:03 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 90:YY:YY:YY:YY:YY, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:03 syslog: WLCEVENTD wlceventd_proc_event(449): wl0.1: Assoc 90:YY:YY:YY:YY:YY, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:09 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:09 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:09 syslog: WLCEVENTD wlceventd_proc_event(449): wl0.1: Assoc 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:12 syslog: WLCEVENTD wlceventd_proc_event(386): wl0.1: Deauth_ind 90:YY:YY:YY:YY:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 22 10:33:15 syslog: WLCEVENTD wlceventd_proc_event(386): wl0.1: Deauth_ind 7C:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 22 10:33:15 syslog: WLCEVENTD wlceventd_proc_event(401): wl0.1: Disassoc 7C:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 22 10:33:17 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:17 syslog: WLCEVENTD wlceventd_proc_event(449): wl0.1: Assoc 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:23 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 90:YY:YY:YY:YY:YY, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:23 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 90:YY:YY:YY:YY:YY, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:23 syslog: WLCEVENTD wlceventd_proc_event(449): wl0.1: Assoc 90:YY:YY:YY:YY:YY, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:26 syslog: WLCEVENTD wlceventd_proc_event(386): wl0.1: Deauth_ind 7C:XX:XX:XX:XX:XX, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 22 10:33:33 syslog: WLCEVENTD wlceventd_proc_event(386): wl0.1: Deauth_ind 90:YY:YY:YY:YY:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jun 22 10:33:33 syslog: WLCEVENTD wlceventd_proc_event(401): wl0.1: Disassoc 90:YY:YY:YY:YY:YY, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 22 10:33:38 syslog: WLCEVENTD wlceventd_proc_event(420): wl0.1: Auth 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)
Jun 22 10:33:38 syslog: WLCEVENTD wlceventd_proc_event(449): wl0.1: Assoc 7C:XX:XX:XX:XX:XX, status: 0, reason: d11 RC reserved (0)


And that's just a few lines of the whole 2.5k log :(
 
don't worry about your log. this is normal and is not an issue. Make sure that you reset network settings on apple devices and have them register with your latest firmware. Apple stores some unclear "goodies" with a wifi that change when you change the firmware.
 
don't worry about your log. this is normal and is not an issue. Make sure that you reset network settings on apple devices and have them register with your latest firmware. Apple stores some unclear "goodies" with a wifi that change when you change the firmware.

What the...thanks Apple :D

But seriously, thanks SheikhSheikha! Wasn't aware of that :)
 
@rolfi a full firmware reset to factory defaults is needed after flashing the firmware you want to use (not before). :)
 
@rolfi a full firmware reset to factory defaults is needed after flashing the firmware you want to use (not before). :)

Haha, right. It's obvious after you tell me :D

So I went through the nuclear reset and the M&M list of settings- the only one I didn't do is the "new SSID" names, but I disabled UPnP from the Internet. Everything else I did as stated.

Now I am going to set up the 5GHz bands and the guest networks and hope that the Internet will be more stable than today (that's a pun, because I use the beta firmware now, instead of stable :D ).
After that is running for some days, I will set up the wireless scheduler for turning the wifi off during the night.

Thanks for the super decent guides L&LD. That helped a lot :)
 
Where did get this version from?
My router offered 3.0.0.4.384_81974 and I've upgrade to it. Clearly a bad release, both 5GHz radios are stuck on 20MHz. I'm not going to reset it yet. I'm waiting couple of day for a new release.

Update, I'm talking about new firmware GT-AC5300. Topic is for RT-AC5400
 
Last edited:
Can be install RT-AC5300_384.19_0 on rtac5300? without issues because the last time i installed merlin firmware i couldnt enter with last login on the router menu.
 

Sign Up For SNBForums Daily Digest

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