It checks out. Thanks though.Verify it downloaded correctly using the md5 key. I installed it on mine without issues
It checks out. Thanks though.Verify it downloaded correctly using the md5 key. I installed it on mine without issues
Make sure you aren't confusing the GT-AX11000 with the GT-AXE11000.It checks out. Thanks though.
Doh! TIL there's a GT-AXE11000 and it's supported by Merlin. Thanks for saving me a factory reset , and of course for all the hard work you do.Make sure you aren't confusing the GT-AX11000 with the GT-AXE11000.
I can’t (ISP specific firmware does not offer that option).Did you remember to set the Fiber modem in "Bridge Mode"?
Feb 22 08:32:35 acsd: eth6: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Feb 22 08:33:45 wlceventd: wlceventd_proc_event(505): eth7: Auth 88:D0:39:C0:60:A6, status: Successful (0)
Feb 22 08:33:45 wlceventd: wlceventd_proc_event(534): eth7: Assoc 88:D0:39:C0:60:A6, status: Successful (0)
Feb 22 08:33:45 hostapd: eth7: STA 88:d0:39:c0:60:a6 IEEE 802.11: associated
Feb 22 08:33:50 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 88:D0:39:C0:60:A6, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Feb 22 08:33:50 hostapd: eth7: STA 88:d0:39:c0:60:a6 IEEE 802.11: disassociated
Feb 22 08:33:50 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 88:D0:39:C0:60:A6, status: 0, reason: Previous authentication no longer valid (2)
Feb 22 08:33:50 hostapd: eth7: STA 88:d0:39:c0:60:a6 IEEE 802.11: disassociated
Adaptive QoS on AX86U running 386.5 alpha2 works improperly.Dirty, filthy, stinking upgrade from previous alpha2 on 3 AX86U and looking good so far in terms of stability and connections.
QOS adaptive dials look wrong though. On a speed test, the UPLOAD part of it was registering movement on the DOWNLOAD dial and when downloading nothing was registered on either dial?
The traffic rate was also completely incorrect and a few KB. No change from alpha1?
Disable 11b
option on the 2.4 GHz WiFi when Wireless Mode
is set to Auto
still makes the clients disconnect a few seconds after connecting, but, unlike 386.4_0, the option can be disabled by the WebUI, no need to use the terminal.I think that this line,Installed like 8 hours ago and noticing my log is filled with below messages, not sure what they mean.
Eth6 says something about 'channel 6' wich i dont use, i have 1 for the 2.4ghz set.
The mac that is shown on the eth7 messages is also something im unable to find in my house.
Code:Feb 22 08:32:35 acsd: eth6: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs Feb 22 08:33:45 wlceventd: wlceventd_proc_event(505): eth7: Auth 88:D0:39:C0:60:A6, status: Successful (0) Feb 22 08:33:45 wlceventd: wlceventd_proc_event(534): eth7: Assoc 88:D0:39:C0:60:A6, status: Successful (0) Feb 22 08:33:45 hostapd: eth7: STA 88:d0:39:c0:60:a6 IEEE 802.11: associated Feb 22 08:33:50 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 88:D0:39:C0:60:A6, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3) Feb 22 08:33:50 hostapd: eth7: STA 88:d0:39:c0:60:a6 IEEE 802.11: disassociated Feb 22 08:33:50 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 88:D0:39:C0:60:A6, status: 0, reason: Previous authentication no longer valid (2) Feb 22 08:33:50 hostapd: eth7: STA 88:d0:39:c0:60:a6 IEEE 802.11: disassociated
Feb 22 08:32:35 acsd: eth6: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
, refers to the fact that your 2.4 GHz Channel bandwidth
is not set to 20 MHz
and when the router detects another wireless network using a channel overlapping with its own, it correctly falls back the bandwidth to 20 MHz and informs you by that line. Check this soon to be 10 years old article from this very website for more information.Channel bandwidth
to 20 MHz
, also set the Control channel
to 1
, 6
or 11
, depending on which is the most unused.Tonly Technology Co. Ltd
, formerly TCL Technoly Electronics(Huizhou).,Ltd
, which unfortunatelly means nothing to me.Where did you find this stated? Would be nice to know. Personally, my AX88U (location 1) seem to handle LAN clients with CakeQos fine. Very disappointing if the my AC86U doesn't, as CakeQos was a key reason for me to upgrade to AC86U at a different location (2), and I've seen no announcement about this.I know the AC86U and AX68U doesn't throttle LAN transfers with Cake, I wonder if the AX88U does, maybe its the CPU architecture.
The other models received an updated official firmware based on the 386.46** branch back in January '22, but AC86U still hasn't received it yet (as you can see from the post I linked above, it usually receives its update only a few days after AC68U).Thanks for the links and for setting me straight. So while other router models have received updated wi-fi drivers from ASUS/Broadcom, the AC86U has not?
If you look at the post I linked above, these problems go way back, far past the 386.4 release, including both official Asus firmware as well as Merlin.There were a fair number that reported problems in the 386.4 release forum as well as on TPLINK site. Not sure if its AX only but could be.
#define DRV_NAME "brcmnand"
#define CMD_PAGE_READ 0x01
#define CMD_PROGRAM_PAGE 0x04
Did you have to clone the modem's MAC to your router?I have AT&T Fiber modem in front of my Router and put the AT&T modem/router into passthrough mode and now get the external IP address on my Asus. You might check if you have similar option.
I think that's how they lock you to their QoS so you can't test the limits of your linkI can’t (ISP specific firmware does not offer that option).
Sound like a hardware issue to me.When doing a robocopy (or large files) from a local drive to a network share on the RTAC86U, the copy will pause, then fail/timeout. This coincides with a NAND error in syslog.
Its working fine until i turn on DNS over TLS and many IoT devices switching off-line including Arlo doorbell, Bryant thermostats and so on and this issue force me to turn on DNS filters.I have 39 IoT devices and have never had an issue with my two AC86U or my 1900P I used to use.
Getting the same error when attempting to upgrade two of my RT-AC5300 routers to 386.5 beta1 from 386.4 which they've been running solid on for 48+ days.First "invalid firmware" on my AX11000. Out of curiosity, I successfully installed the lastest stock firmware, then successfully went back and re-installed 386.4, but still no on 386.5 from there... Guess I'll factory reset tomorrow. Feck
Thanks, that was my thought as well. Understood about the /jffs partition. I have entware and scribe installed, so a lot of the normal /jffs IO (syslog-ng) is going to a separate USB drive.Sound like a hardware issue to me.
Keep in mind that in addition to the firmware files, the NAND also contains the jffs partition, with all of its content (syslog copy, various settings, etc...).
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!