Asuswrt-Merlin 384.8 is now available

[wreq5]

Running this right now using WinSCP portable. Hopefully this works however I cannot see progress of it properly applying so I will give it a few minutes before rebooting.

This worked properly! Of course no graphical indication of completion so it's safe to restart in 10 minutes.

 

[telUK]

On 5ghz you need to be on 80mhz for a decent signal. Beamforming is a good idea to play with though.

Cheers, I will start with setting to 80mhz, I will stick to controlling my channel which is on 100.

Is there any downside to fixing it to 80mhz as apposed to using the Auto 20/40/80 option.

Obviously I need to try things to cure my 5ghz dropping so want to keep away from the 20/40/80 setting for the time being.

 

[hamwong]

@RMerlin Thanks for the great work,
I got few question on AC88U and wish you may clarify,

1) does IPTraffic still useful? as there is Traffic Analyzer on that page no matter IPTraffic turn on or off,
2) will busybox be upgrade to full version? I found BusyBox v1.28.1 full version with much more commands and even command have much more function build in

router
BusyBox v1.25.1 (2018-12-08 13:18:50 EST) multi-call binary.
Usage: nc [-iN] [-wN] [-f FILE|IPADDR PORT] [-e PROG]
Open a pipe to IPORT or FILE
-w SEC Connect timeout
-i SEC Delay interval for lines sent
-f FILE Use file (ala /dev/ttyS0) instead of network
-e PROG Run PROG after connect

with full version
BusyBox v1.28.1 (2018-02-15 14:34:02 CET) multi-call binary.
Usage: nc [OPTIONS] HOST PORT - connect
nc [OPTIONS] -l -p PORT [HOST] [PORT] - listen
-e PROG Run PROG after connect (must be last)
-l Listen mode, for inbound connects
-lk With -e, provides persistent server
-p PORT Local port
-s ADDR Local address
-w SEC Timeout for connects and final net reads
-i SEC Delay interval for lines sent
-n Don't do DNS resolution
-u UDP mode
-v Verbose
-o FILE Hex dump traffic
-z Zero-I/O mode (scanning)

I understand full version got 1 M size larger but I think it's kind of worth.

3) On adaptive qos page, we able to see traffic real time per IP or total, will it possibile port that info to SNMP?

Regards and Thanks

 

[DroidST]

Cheers, I will start with setting to 80mhz, I will stick to controlling my channel which is on 100.

Is there any downside to fixing it to 80mhz as apposed to using the Auto 20/40/80 option.

I'm curious too, always had mine on 20/40/80 and never tried '80 only' but I thought you need it on 20/40/80 for 802.11n 5GHz clients to connect properly. So, with 80 only, does this still apply?

802.11ac uses 80 MHz and 160 MHz bandwidths while still supporting 20 and 40 MHz channels.

EDIT: Just read this post from RMerlin - I will set to 80

Depends on the wireless radio manufacturer. Quantenna is the provider of the 5 GHz radio on the RT-AC87U, and they do not offer the same options as Broadcom.

Anyway, 80 MHz is backward compatible with 40 and 20, I never understood the point in listing a specific 20/40/80 setting.

.

 

[D_Day]

Cheers, I will start with setting to 80mhz, I will stick to controlling my channel which is on 100.

Is there any downside to fixing it to 80mhz as apposed to using the Auto 20/40/80 option.

Obviously I need to try things to cure my 5ghz dropping so want to keep away from the 20/40/80 setting for the time being.

Google it. It’s quite interesting.

 

[dugaduga]

AsusWRT RT_AC66U B1 as RT_AC68U, using the latest 8_2 and I am stuck on 100 mbps lan, should be 1 gb. Wan is 1 GPBS; Lan 1, 1 GBPS, Lan 3, 100 mbps. this happened on occasion, a reboot typically fixed this, not this time. Am seeing max 100 duplex under advanced driver properties in windows, I'm wondering if this is due to a windows update. Ok just tested in linux and the result is the same.

 

[RMerlin]

1) does IPTraffic still useful? as there is Traffic Analyzer on that page no matter IPTraffic turn on or off,

I find Traffic Analyzer very clunky. It gathers a lot of useful information, but the web interface to display that information is mostly unusable.

2) will busybox be upgrade to full version? I found BusyBox v1.28.1 full version with much more commands and even command have much more function build in

No. Bundling a bunch of unused applets will only increase the memory usage significantly (since every time an applet is used, the whole Busybox gets loadded and used), and it will also increase the attack surface for hackers.

AsusWRT RT_AC66U B1 as RT_AC68U, using the latest 8_2 and I am stuck on 100 mbps lan, should be 1 gb. Wan is 1 GPBS; Lan 1, 1 GBPS, Lan 3, 100 mbps. this happened on occasion, a reboot typically fixed this, not this time. Am seeing max 100 duplex under advanced driver properties in windows, I'm wondering if this is due to a windows update. Ok just tested in linux and the result is the same.

Change your Ethernet cable.

 

[telUK]

Is there anywhere in the GUI i can view uptime of 5ghz network, like a time my devices have been connected on 5ghz for?

Thanks

 

[D_Day]

Is there anywhere in the GUI i can view uptime of 5ghz network, like a time my devices have been connected on 5ghz for?

Thanks

Wireless log

 

[D_Day]

Is there anywhere in the GUI i can view uptime of 5ghz network, like a time my devices have been connected on 5ghz for?

Thanks

Wireless log is the tab next to system log, you can see how long each device has been connected.

 

[PeterDNA]

After 2 days of uptime on 384.8.2 it seems 5Ghz band drops out, it happens every two days of uptime. Here is the log when it does happen.

Dec 16 04:04:41 kernel: DUMP CONSOLE: 0x00ec8166 0x00ec8166
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00fe8166 0x00fe8166 0x00fe8166 0x00ec8166
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00fe8166 0x00fe8166 0x00fe8166 0x00ec8166
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00c98166 0x00fe8166 0x00fe8166 0x00fe8166
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 PC (psmdebug):
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00ff8028 0x00ff8046 0x00fe805b 0x00ff809c
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00ff8028 0x00ff8047 0x00ff8060 0x00ff809c
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 psmx stack_status : 0x1
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 psmx stack_entries:
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x002f
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x0141
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x0176
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x01e6
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x1ffd
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x1fdd
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x1ffd
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x07f7
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 txe_vasip_intsts 0x0
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 wl1: fatal error, reinitializing
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.528 wlc_ucode_download: wl1: Loading MU ucode
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.540 wl1: CORE INIT : nfifo 32 mu_tx_enab 1
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.541 wl1: CORE INIT : mode 2 pktclassify 1 rxsplit 0 hdr conve 0 DMA_CT Enabled
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.550 wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.550 wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.554 wlc_mutx_watchdog: PSMx wds diff = 1
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.554 wlc_mutx_watchdog: 2 PSMx wds in 5 seconds
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.555 enable 1: q0 frmcnt 0, wrdcnt 0, q1 frmcnt 0, wrdcnt 0
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.555 enable 1: q0 frmcnt 0, wrdcnt 0, q1 frmcnt 0, wrdcnt 0
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.555 wlc_ucode_download: wl1: Loading non-MU ucode
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.570 wl1: CORE INIT : nfifo 6 mu_tx_enab 0
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.570 wl1: CORE INIT : mode 2 pktclassify 1 rxsplit 0 hdr conve 0 DMA_CT Disabled
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.583 wlc_ucode_download: wl1: Loading non-MU ucode
Dec 16 04:04:41 kernel: dhdpcie_checkdied: msgtrace address : 0x00000000
Dec 16 04:04:41 kernel: console address : 0x003FFCF0
Dec 16 04:04:41 kernel: Assrt not built in dongle
Dec 16 04:04:41 kernel: TRAP type 0x4 @ epc 0x207e7c, cpsr 0x8000193, spsr 0x8000033, sp 0x2acd78, lp 0x207e5d, rpc 0x207e7c
Dec 16 04:04:41 kernel: Trap offset 0x2acd20, r0 0x83c, r1 0x0, r2 0x14, r3 0x3f8c10, r4 0x3ee820, r5 0x3f68a0, r6 0x3f017c, r7 0x3f4790
Dec 16 04:04:45 rc_service: restart_wireles 22117:notify_rc stop_amas_wlcconnect
Dec 16 04:04:45 rc_service: restart_wireles 22117:notify_rc stop_amas_bhctrl
Dec 16 04:04:45 rc_service: waitting "stop_amas_wlcconnect" via restart_wireles ...
Dec 16 04:04:46 rc_service: restart_wireles 22117:notify_rc stop_obd
Dec 16 04:04:46 rc_service: waitting "stop_amas_bhctrl" via restart_wireles ...
Dec 16 04:04:48 kernel: br0: port 2(eth1) entering forwarding state
Dec 16 04:04:48 kernel: device eth1 left promiscuous mode
Dec 16 04:04:48 kernel: br0: port 2(eth1) entering disabled state
Dec 16 04:04:52 kernel: device eth1 entered promiscuous mode
Dec 16 04:04:52 kernel: br0: topology change detected, propagating
Dec 16 04:04:52 kernel: br0: port 2(eth1) entering forwarding state
Dec 16 04:04:52 kernel: br0: port 2(eth1) entering forwarding state


RT-AC88U 384.8.2

 

[skeal]

After 2 days of uptime on 384.8.2 it seems 5Ghz band drops out, it happens every two days of uptime. Here is the log when it does happen.

Dec 16 04:04:41 kernel: DUMP CONSOLE: 0x00ec8166 0x00ec8166
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00fe8166 0x00fe8166 0x00fe8166 0x00ec8166
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00fe8166 0x00fe8166 0x00fe8166 0x00ec8166
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00c98166 0x00fe8166 0x00fe8166 0x00fe8166
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 PC (psmdebug):
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00ff8028 0x00ff8046 0x00fe805b 0x00ff809c
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x00ff8028 0x00ff8047 0x00ff8060 0x00ff809c
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 psmx stack_status : 0x1
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 psmx stack_entries:
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x002f
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x0141
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x0176
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x01e6
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x1ffd
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x1fdd
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x1ffd
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 0x07f7
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 txe_vasip_intsts 0x0
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.527 wl1: fatal error, reinitializing
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.528 wlc_ucode_download: wl1: Loading MU ucode
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.540 wl1: CORE INIT : nfifo 32 mu_tx_enab 1
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.541 wl1: CORE INIT : mode 2 pktclassify 1 rxsplit 0 hdr conve 0 DMA_CT Enabled
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.550 wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.550 wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.554 wlc_mutx_watchdog: PSMx wds diff = 1
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.554 wlc_mutx_watchdog: 2 PSMx wds in 5 seconds
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.555 enable 1: q0 frmcnt 0, wrdcnt 0, q1 frmcnt 0, wrdcnt 0
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.555 enable 1: q0 frmcnt 0, wrdcnt 0, q1 frmcnt 0, wrdcnt 0
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.555 wlc_ucode_download: wl1: Loading non-MU ucode
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.570 wl1: CORE INIT : nfifo 6 mu_tx_enab 0
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.570 wl1: CORE INIT : mode 2 pktclassify 1 rxsplit 0 hdr conve 0 DMA_CT Disabled
Dec 16 04:04:41 kernel: DUMP CONSOLE: 233586.583 wlc_ucode_download: wl1: Loading non-MU ucode
Dec 16 04:04:41 kernel: dhdpcie_checkdied: msgtrace address : 0x00000000
Dec 16 04:04:41 kernel: console address : 0x003FFCF0
Dec 16 04:04:41 kernel: Assrt not built in dongle
Dec 16 04:04:41 kernel: TRAP type 0x4 @ epc 0x207e7c, cpsr 0x8000193, spsr 0x8000033, sp 0x2acd78, lp 0x207e5d, rpc 0x207e7c
Dec 16 04:04:41 kernel: Trap offset 0x2acd20, r0 0x83c, r1 0x0, r2 0x14, r3 0x3f8c10, r4 0x3ee820, r5 0x3f68a0, r6 0x3f017c, r7 0x3f4790
Dec 16 04:04:45 rc_service: restart_wireles 22117:notify_rc stop_amas_wlcconnect
Dec 16 04:04:45 rc_service: restart_wireles 22117:notify_rc stop_amas_bhctrl
Dec 16 04:04:45 rc_service: waitting "stop_amas_wlcconnect" via restart_wireles ...
Dec 16 04:04:46 rc_service: restart_wireles 22117:notify_rc stop_obd
Dec 16 04:04:46 rc_service: waitting "stop_amas_bhctrl" via restart_wireles ...
Dec 16 04:04:48 kernel: br0: port 2(eth1) entering forwarding state
Dec 16 04:04:48 kernel: device eth1 left promiscuous mode
Dec 16 04:04:48 kernel: br0: port 2(eth1) entering disabled state
Dec 16 04:04:52 kernel: device eth1 entered promiscuous mode
Dec 16 04:04:52 kernel: br0: topology change detected, propagating
Dec 16 04:04:52 kernel: br0: port 2(eth1) entering forwarding state
Dec 16 04:04:52 kernel: br0: port 2(eth1) entering forwarding state


RT-AC88U 384.8.2

I have a AC3100 (AC88U with 4 ports) and do not have this issue. My up time is well over 7 days.

 

[Jheroen]

I just got a hint that i have to clear out nvram on the router, i want to give the new FW a try because of this.
Didn't do that earlier.

What is the procedure?
I am on 380.70 FW now
which order should i follow? (install/reboot/fact default/etc) AND
i have a cfg file from an earlier 3.8.4 build, can i use this one to restore after i install the latest FW?

 

[Sanna1967]

i have a cfg file from an earlier 3.8.4 build, can i use this one to restore after i install the latest FW?

No.
The jump is big, and be ready to do a factory restore if something goes wrong next

 

[skeal]

I just got a hint that i have to clear out nvram on the router, i want to give the new FW a try because of this.
Didn't do that earlier.

What is the procedure?
I am on 380.70 FW now
which order should i follow? (install/reboot/fact default/etc) AND
i have a cfg file from an earlier 3.8.4 build, can i use this one to restore after i install the latest FW?

I think we have talked about this before. I recommended you upgrade and reset to defaults as a must do. To many changes since that f/w. Do not import your saved 384 configuration as you did before. Take screen shots of important settings.

 

[Stevens243]

Try turning off Universal Beamforming under professional settings. Leave ac beamforming on. Set 5ghz channel to Auto and channel bandwidth to 20/40/80. I have Auto set on 5ghz only. All my devices have been connected for over 6 days, since I upgraded to 384.8_2 and factory reset. Worth a try.

Thanks, that really solved the issues that I was having. Rock solid wireless access since I made the change.

 

[RMerlin]

Oh, FFS...

Does it also need to be put in blinking text???

 

[Mutzli]

I just got a hint that i have to clear out nvram on the router, i want to give the new FW a try because of this.
Didn't do that earlier.

What is the procedure?
I am on 380.70 FW now
which order should i follow? (install/reboot/fact default/etc) AND
i have a cfg file from an earlier 3.8.4 build, can i use this one to restore after i install the latest FW?

To clean the nvram run the following command in a SSH terminal:

for line in `nvram show | grep =$ `; do var=${line%*=}; nvram unset $var; done; nvram commit

 

[Jheroen]

Is that the same as with telnet

 

[D_Day]

Is that the same as with telnet

Use Putty to SSH
Make sure you turn on access in system settings.