What's new

[Thread-1] [ 386.1_Alpha Build(s) ] Testing available build(s)

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

Status
Not open for further replies.
AC86U dirty upgrade to 386.1 alpha 4 from 384.19 with FlexQOS and Diversion. No issues noted other than the repeating log message (protocol 0800 is buggy)
 
This is the end of the line for my 'dirty upgrades' it seems for my RT-AX88U (main) and an RT-AX58U in AiMesh (node). :(
I'm interested in the outcome of this as well. I just ordered a new RT-AX58U for $130 from Newegg this morning to add as an AiMesh node to one of my RT-AX88U.
 
RT-AX58U Router took a couple of spontaneous restarts on Alpha 4. Did not see anything of interest in the log files. Anyone else getting a spontaneous restart during normal activity?
 
RT-AX58U Router took a couple of spontaneous restarts on Alpha 4. Did not see anything of interest in the log files. Anyone else getting a spontaneous restart during normal activity?

AX58U Has been rock solid on A-4.
 
AX86U. Would appreciate some help troubleshooting a problem that *may* have been caused by trying out Alpha3/Alpha4.

I can no longer manually select 5ghz channels without breaking 5ghz connectivity. Auto seems to work. Stock firmware out of box (3.0.0.4.384.9173 in Canada) had no such problems. This behaviour now persists, even after flashing to stock and hard-resetting through both the GUI and WPS button. Flashed stock x2, hard reset again, even tried Recovery Mode flashing. Broken 5ghz behaviour persists.

I know the stock hardware/firmware had no such problems because I bought a second AX86u. Works out of box, breaks after firmware update, and I can't seem to return to the original state.

Coming back to Alpha 4, I see this in the logs when setting a 5ghz channel manually (channel 149, for example):
Nov 30 14:09:16 kernel: CONSOLE: 142207.129 wl1: link up (wl1)
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 wl1: bcn inactivity detected
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 wl1: txbcnfrm 0 prev txbcnfrm 0 txbcn inactivity 4 timeout 4 edcrs_timeout 200 macctrl 0x4160403
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 wl1: fatal error, reinitializing
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 wl1: fatal error, reinitializing, total count of reinit's[14]
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 wl1: 802.11 reinit reason[16], count[14]
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 HWA4a TxSTAT: hwa_txstat_reclaim: reinit<1> stall<0>
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 HWA3b TxFIFO: reclaim fifo 1 pkts 5
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 HWA1b RxFILL: mac_counter_status sat<0> need_post<0> aval<256>
Nov 30 14:09:20 kernel: CONSOLE: 142211.099 HWA1b RxFILL: reclaim core<0> 256 rxbuffers RD<0> WR<256>
Nov 30 14:09:20 kernel: CONSOLE: 142211.100 HWA1a RxPOST: wi_cnt<128> in hwa internal memory<RD:0 WR:0>
Nov 30 14:09:20 kernel: CONSOLE: 142211.100 wl1: wlc_bmac_wowlucode_start mctrl=0x4020402 0x4000400
Nov 30 14:09:20 kernel: CONSOLE: 142211.100 wl1: wlc_bmac_wowlucode_start (mctrl | MCTL_PSM_JMP_0)=0x4020406 0x4020406
Nov 30 14:09:20 kernel: CONSOLE: 142211.100 wl1: wlc_bmac_wowlucode_start mctrl=0x4020402 0x4020402
Nov 30 14:09:20 kernel: CONSOLE: 142211.102 wl1: CORE INIT : mode 4 pktclassify 1 rxsplit 1 hdr conversion 1 DMA_CT Enabled
Nov 30 14:09:20 kernel: CONSOLE: 142211.119 wlc_mutx_active_update vasip mu_supported_Ntx 4
Nov 30 14:09:20 kernel: CONSOLE: 142211.119 HWA1a RxPOST: H2D RxPost ring: id<1> type<0> item_type<1> max_items<1024> len_item<8>
Nov 30 14:09:20 kernel: CONSOLE: 142211.120 HWA1a RxPOST: item_size 8 CWI32 config parser<00000000> format<0> size<8>
Nov 30 14:09:20 kernel: CONSOLE: 142211.120 HWA1a RxPOST: rxpost_data_buf_len<1836>
Nov 30 14:09:20 kernel: CONSOLE: 142211.123 CSIMON: already initialized ...
Nov 30 14:09:20 kernel: CONSOLE: 142211.128 wl1: link up (wl1)

This repeats over and over again until I go back to auto-channel or channel 36 (the last channel selected by auto-algo). Any thoughts here?

Edit w/ a further note:
5ghz performance is absolutely shot, even on Auto. With stock firmware I could move 2-floors down and have an acceptable connection w/ a laptop and iPhone. Now, my phone can barely leave the room before encountering disconnects under load (speed tests, for example). Again, this persists even after flashing and hard-resetting back to stock. I have reset phone network settings as well as changed SSIDs throughout the troubleshooting process. Same 5ghz channel (36), no new sources of interference. Testing occurred back to back. Edit 2: Removed note: Auto 5ghz performance appears to be ok.
 
Last edited:
Dirty upgrade to A4 from A3. WAN lost connection when adjusting an VPN client but couldn't log in the GUI anymore A power cycle did apply changes on an VPN client. In my case i cant power cycle after every change i make with A4. Alpha 3 was a clean install. I'm on A3 again just for OVPN 2.5 and take the loss of WAN, but can restart WAN with a press on the apply button over there. maybe something in the making?
 
RT-AX58U Router took a couple of spontaneous restarts on Alpha 4. Did not see anything of interest in the log files. Anyone else getting a spontaneous restart during normal activity?

Nothing like that here, running perfectly as far as I have found. Only ongoing issue is that AdaptiveQOS doesn't seem to do anything and the classification graphs are missing. I'm just using Traditional QOS for my 75x8 Mb connection and it works just fine.
 
Try using time.nrc.ca in the first server spot and nothing in the second and test.

It works fine with the primary of 'pool.ntp.org', just the secondary doesn't seem to pick up if the primary is not working. It didn't like "uk.pool.ntp.org" as a primary either even though that is OK on Windows as an NTP source.
 
Alpha 4 - Using dual wan and AiMesh seems to be working fine, only been using an hour so far. AX68U as main node and AC68U AiMesh child/ node. The interface on the AC68U AiMesh page is empty when I was having a look around before making it into a AiMesh node, but is fine on the AX68U.

Hard reset the AC68U and did no config on it, turned on ethernet backhaul on my AX68U and did a search. Picked it up straight away. :)
 
I fixed a typo in 386_41035's Makefile causing the RT-AX58U 5 GHz radio firmware to be missing from the router's firmware image. Rebuilt firmware has been uploaded.
The LED radio button for under AiMesh tab, Management sub-tab (above Enable Radio buttons) is missing for the the rebuilt RT-AX58U Alpha 4 firmware.
 
Is everyone else seeing all devices only listed under Wired Interface in the Client List? ie., nothing is listed in a wireless group.
 
Is everyone else seeing all devices only listed under Wired Interface in the Client List? ie., nothing is listed in a wireless group.

No, it's looking ok on my X88U with alpha 4. Clients are correctly showing under wired/2.4GHz/5GHz.
 
Wow, the GUI is noticeably snappier with Alpha4, and I mean noticeably!
 
AX88U running Alpha 4 for around 3 hours. 2 AX58U's as AIMesh nodes running Alpha 4 as well. An old AC68U running Alpha 4 as a Media Bridge.
No instability so far, running well.
AX88U was unstable with Alpha 3. It had kept it back on Alpha 2.

Total of 42 devices on-line, 8 on one node and 4 on another.

The only minor oddball messages I see running dmesg is:

192.168.1.17 is used by someone else, can't use it

I did have an issue with some Add-on's starting up. spdMerlin needed an uninstall and re-install. I kept getting "Aborted" from the Ookla speedtest binary. Re-installed and running fine now.
 
Is everyone else seeing all devices only listed under Wired Interface in the Client List? ie., nothing is listed in a wireless group.
No, my wired and wireless devices are showing correctly in my Client List.
 
Noticed a problem since alpha4. As soon as I change some wireless setting and apply it, my wan connection goes down. Only solution is to reboot the router.
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

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