Menu
What's new
By:
Filters Better Search

Beta Asuswrt-Merlin 386.1 Beta (stage 2) is now available

  • 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.
Compile warning from the latest commit id.

[rc] CC tcpcheck.o
sysdeps/init-broadcom.c:40:17: fatal error: d11.h: No such file or directory
compilation terminated.
make[7]: *** [Makefile:1751: init-broadcom.o] Error 1
make[7]: *** Waiting for unfinished jobs....
sysdeps/wps-broadcom.c:62:13: warning: 'hapd_wps_cleanup' declared 'static' but never defined [-Wunused-function]
static void hapd_wps_cleanup();
^
make[7]: Leaving directory '/home/admin/amng.ax88/release/src/router/rc'
make[6]: *** [Makefile:3102: rc] Error 2
make[6]: Leaving directory '/home/admin/amng.ax88/release/src/router'
make[5]: *** [Makefile:30: router_all] Error 2
make[5]: Leaving directory '/home/admin/amng.ax88/release/src-rt-5.02axhnd/userspace'
make[4]: *** [make.hndrt:329: userspace] Error 2
make[4]: Leaving directory '/home/admin/amng.ax88/release/src-rt-5.02axhnd'
make[3]: *** [make.hndrt:115: parallel_targets] Error 2
make[3]: Leaving directory '/home/admin/amng.ax88/release/src-rt-5.02axhnd'
make[2]: *** [Makefile:601: all] Error 2
make[2]: Leaving directory '/home/admin/amng.ax88/release/src-rt-5.02axhnd'
make[1]: *** [Makefile:5151: bin] Error 2
make[1]: Leaving directory '/home/admin/amng.ax88/release/src-rt-5.02axhnd'
make: *** [Makefile:5333: rt-ax88u] Error 2
 
Expell666 said:
I thought I was the only one had the problem. My AX88U kicked my phone out of the internet repeatedly. I ended up recovery with ASUS recovery and re-flashed Beta 3 again. Now I'm happy
Click to expand...

No need to downgrade to beta 3.... Try to use beta 4B or Beta4-gb9.
Those versions should have flashing issues resolved. If your already on the original beta4 which was pulled, this was a known issue which is why RMerlin pulled/removed the build.
Even he had the issues. Just because Beta4B has resolved flashing issues does not magically make it solve the current issues you might have if you flashed the original beta4, you use Rescue tool to get to beta4b and you should be good from there.
 
Last edited:
Hey guys. Crashed again today RT-AX86U Beta 4. Here's the log just before and just after. I'm really at a loss as to what is causing this and would love some input to how I can better log what's going on so I can get down to the issue.

Code: 
Jan 12 16:16:18 RT-AX86U kernel: _blog_emit, blogp = 0x2280
Jan 12 16:16:31 RT-AX86U rc_service: dhcp6c 21780:notify_rc restart_ddns
Jan 12 16:16:31 RT-AX86U custom_script: Running /jffs/scripts/service-event (args: restart ddns)
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x4
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:52 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:52 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:17:08 RT-AX86U kernel: _blog_emit, blogp = 0x2300
Jan 12 16:17:08 RT-AX86U kernel: _blog_emit, blogp = 0x2300
Jan 12 16:17:08 RT-AX86U kernel: _blog_emit, blogp = 0x2300
Jan 12 16:17:15 RT-AX86U kernel: CONSOLE: 147576.347 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 12 16:17:19 RT-AX86U kernel: _blog_emit, blogp = 0x2300
Jan 12 16:17:19 RT-AX86U kernel: _blog_emit, blogp = 0x2300
May  5 13:05:07 syslogd started: BusyBox v1.25.1
May  5 13:05:07 kernel: klogd started: BusyBox v1.25.1 (2021-01-08 17:43:19 EST)
May  5 13:05:07 crashlog: LOG
May  5 13:05:07 crashlog: 000
May  5 13:05:07 kernel: max_ent = 16384 intvl_msec = 10000 num_slices = 2000 num_ent = 9 period_msec = 5
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[437]
May  5 13:05:07 kernel: NBUFF v1.0 Initialized
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[438]
May  5 13:05:07 kernel: ^[[0;36;44mTotal # of labels = 68^[[0m
May  5 13:05:07 kernel: ^[[0;36;44mInitialized fcache state^[[0m
May  5 13:05:07 crashlog: <4>[BLOCKED - INBOUND] IN=eth0 OUT= MAC=24:4b:fe:d3:95:48:00:a2:00:b2:00:c2:08:00 SRC=74.120.14.94 DST=61.245.130.77 LEN=44 TOS=0x00 PREC=0x00 TTL=34 ID=8030 PROTO=TCP SPT=3541 DPT=9912 SEQ=3025408900 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405B4) M
May  5 13:05:07 kernel:     Pkt HW acceleration is disabled/unavailable.
May  5 13:05:07 crashlog: ARK=0x8000000
May  5 13:05:07 kernel: ^[[0;36;44mBroadcom Packet Flow Cache  Char Driver v4.0 Registered<302>^[[0m
May  5 13:05:07 kernel: fc_timer_task created successfully
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[439]
May  5 13:05:07 kernel:     Pkt HW acceleration is disabled/unavailable.
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[440]
May  5 13:05:07 kernel: Created Proc FS /procfs/fcache
May  5 13:05:07 kernel: ^[[0;36;44mBroadcom Packet Flow Cache registered with netdev chain^[[0m
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[441]
May  5 13:05:07 kernel: ^[[0;36;44mBroadcom Packet Flow Cache learning via BLOG enabled.^[[0m
May  5 13:05:07 kernel: ^[[0;35m[FHW]  pktDbgLvl[0xffffffbffc481c08]=0^[[0m
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[442]
May  5 13:05:07 kernel: ^[[0;34m[FHW]  fhw_construct: ^[[0m
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[443]
May  5 13:05:07 kernel: ^[[0;36;44mInitialized Fcache HW accelerator layer state^[[0m
May  5 13:05:07 kernel: flwStatsThread created. numFlwsPerPoll 546 maxFlwIdx 16383
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[444]
May  5 13:05:07 kernel: ^[[0;36;44mFcache Pathstats created^[[0m
May  5 13:05:07 crashlog: <7>_blog_emit, blogp = 0x22e0
May  5 13:05:07 kernel: ^[[0;36;44mConstructed Broadcom Packet Flow Cache v4.0^[[0m
May  5 13:05:07 kernel: Broadcom Command List Driver v1.0
May  5 13:05:07 crashlog: <7>_blog_emit, blogp = 0x22e0
May  5 13:05:07 kernel: crossbar[0]: Allocated cb_idx=0 int_ep=0
May  5 13:05:07 crashlog: <4>[BLOCKED - INBOUND] IN=eth0 OUT= MAC=24:4b:fe:d3:95:48:00:a2:00:b2:00:c2:08:00 SRC=45.155.205.41 DST=61.245.130.77 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=65215 PROTO=TCP SPT=52374 DPT=46128 SEQ=1626720450 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000
May  5 13:05:07 kernel: crossbar[0]: Add cb_idx=0 ext_ep=0 SERDES:6
May  5 13:05:07 crashlog: 000
May  5 13:05:07 kernel: crossbar[1]: Allocated cb_idx=0 int_ep=1
May  5 13:05:07 kernel: crossbar[1]: Add cb_idx=0 ext_ep=1 GPHY:12
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[445]
May  5 13:05:07 kernel: crossbar Mux: connect cb_idx:0  int_ep 0 to ext_ep 0
May  5 13:05:07 crashlog: <7>_blog_emit, blogp = 0x2300
May  5 13:05:07 kernel: crossbar Mux: connect cb_idx:0  int_ep 1 to ext_ep 1
May  5 13:05:07 kernel: Detecting PHYs...0x40000000
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[446]
 
Thanks @RMerlin.

On my AC86U, I just noticed that my DHCP reservation max is now only 64 instead of 128.
1610448260158.png
 
SubElement said:
Hey guys. Crashed again today RT-AX86U Beta 4. Here's the log just before and just after. I'm really at a loss as to what is causing this and would love some input to how I can better log what's going on so I can get down to the issue.

Code: 
Jan 12 16:16:18 RT-AX86U kernel: _blog_emit, blogp = 0x2280
Jan 12 16:16:31 RT-AX86U rc_service: dhcp6c 21780:notify_rc restart_ddns
Jan 12 16:16:31 RT-AX86U custom_script: Running /jffs/scripts/service-event (args: restart ddns)
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x4
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:36 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:37 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:38 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:39 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:52 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:16:52 RT-AX86U kernel: _blog_emit, blogp = 0x2260
Jan 12 16:17:08 RT-AX86U kernel: _blog_emit, blogp = 0x2300
Jan 12 16:17:08 RT-AX86U kernel: _blog_emit, blogp = 0x2300
Jan 12 16:17:08 RT-AX86U kernel: _blog_emit, blogp = 0x2300
Jan 12 16:17:15 RT-AX86U kernel: CONSOLE: 147576.347 wl1: wlc_ampdu_recv_addba_resp: e0:2b:96:a6:4a:16: Failed. status 1 wsize 0 policy 0
Jan 12 16:17:19 RT-AX86U kernel: _blog_emit, blogp = 0x2300
Jan 12 16:17:19 RT-AX86U kernel: _blog_emit, blogp = 0x2300
May  5 13:05:07 syslogd started: BusyBox v1.25.1
May  5 13:05:07 kernel: klogd started: BusyBox v1.25.1 (2021-01-08 17:43:19 EST)
May  5 13:05:07 crashlog: LOG
May  5 13:05:07 crashlog: 000
May  5 13:05:07 kernel: max_ent = 16384 intvl_msec = 10000 num_slices = 2000 num_ent = 9 period_msec = 5
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[437]
May  5 13:05:07 kernel: NBUFF v1.0 Initialized
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[438]
May  5 13:05:07 kernel: ^[[0;36;44mTotal # of labels = 68^[[0m
May  5 13:05:07 kernel: ^[[0;36;44mInitialized fcache state^[[0m
May  5 13:05:07 crashlog: <4>[BLOCKED - INBOUND] IN=eth0 OUT= MAC=24:4b:fe:d3:95:48:00:a2:00:b2:00:c2:08:00 SRC=74.120.14.94 DST=61.245.130.77 LEN=44 TOS=0x00 PREC=0x00 TTL=34 ID=8030 PROTO=TCP SPT=3541 DPT=9912 SEQ=3025408900 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405B4) M
May  5 13:05:07 kernel:     Pkt HW acceleration is disabled/unavailable.
May  5 13:05:07 crashlog: ARK=0x8000000
May  5 13:05:07 kernel: ^[[0;36;44mBroadcom Packet Flow Cache  Char Driver v4.0 Registered<302>^[[0m
May  5 13:05:07 kernel: fc_timer_task created successfully
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[439]
May  5 13:05:07 kernel:     Pkt HW acceleration is disabled/unavailable.
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[440]
May  5 13:05:07 kernel: Created Proc FS /procfs/fcache
May  5 13:05:07 kernel: ^[[0;36;44mBroadcom Packet Flow Cache registered with netdev chain^[[0m
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[441]
May  5 13:05:07 kernel: ^[[0;36;44mBroadcom Packet Flow Cache learning via BLOG enabled.^[[0m
May  5 13:05:07 kernel: ^[[0;35m[FHW]  pktDbgLvl[0xffffffbffc481c08]=0^[[0m
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[442]
May  5 13:05:07 kernel: ^[[0;34m[FHW]  fhw_construct: ^[[0m
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[443]
May  5 13:05:07 kernel: ^[[0;36;44mInitialized Fcache HW accelerator layer state^[[0m
May  5 13:05:07 kernel: flwStatsThread created. numFlwsPerPoll 546 maxFlwIdx 16383
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[444]
May  5 13:05:07 kernel: ^[[0;36;44mFcache Pathstats created^[[0m
May  5 13:05:07 crashlog: <7>_blog_emit, blogp = 0x22e0
May  5 13:05:07 kernel: ^[[0;36;44mConstructed Broadcom Packet Flow Cache v4.0^[[0m
May  5 13:05:07 kernel: Broadcom Command List Driver v1.0
May  5 13:05:07 crashlog: <7>_blog_emit, blogp = 0x22e0
May  5 13:05:07 kernel: crossbar[0]: Allocated cb_idx=0 int_ep=0
May  5 13:05:07 crashlog: <4>[BLOCKED - INBOUND] IN=eth0 OUT= MAC=24:4b:fe:d3:95:48:00:a2:00:b2:00:c2:08:00 SRC=45.155.205.41 DST=61.245.130.77 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=65215 PROTO=TCP SPT=52374 DPT=46128 SEQ=1626720450 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000
May  5 13:05:07 kernel: crossbar[0]: Add cb_idx=0 ext_ep=0 SERDES:6
May  5 13:05:07 crashlog: 000
May  5 13:05:07 kernel: crossbar[1]: Allocated cb_idx=0 int_ep=1
May  5 13:05:07 kernel: crossbar[1]: Add cb_idx=0 ext_ep=1 GPHY:12
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[445]
May  5 13:05:07 kernel: crossbar Mux: connect cb_idx:0  int_ep 0 to ext_ep 0
May  5 13:05:07 crashlog: <7>_blog_emit, blogp = 0x2300
May  5 13:05:07 kernel: crossbar Mux: connect cb_idx:0  int_ep 1 to ext_ep 1
May  5 13:05:07 kernel: Detecting PHYs...0x40000000
May  5 13:05:07 crashlog: <4>wl0: fatal error, reinitializing, total count of reinit's[446]
Click to expand...

Not totally clear from logs, but that's a lot of resets. Overheating causing? If plausible, would help to log CPU and radio temps in a cron job every few minutes (I use 10 minutes).
 
Running B4b on my AC2900.

-Clients on Guest networks 1 on both 2,4 and 5Ghz still can't access internet. They obtain ip-addresses from the 192.168.101.xxx and 192.168.102.xxx range resp.. No probs on Guest networks 2 for both freqs.

-CPU temp with both "Cpu Wait" and "EEE" enabled +/- 5 degrees C higher than on 384.19 (with active cooling fan).

-Seems a little more CPU activity in general (even at rest), guess that's due to extended code.

-L2TP/PPTP connection shows a lot more CPU activity than on 384.19, easily filling up 1 core completely on a 150Mbps download.

-Rest seems to be working OK.

-All in all -despite the fact that this is still Work in Progress- i don't see any huge advantage in this build over the 384's
 
Last edited:
tdhite said:
Not totally clear from logs, but that's a lot of resets. Overheating causing? If plausible, would help to log CPU and radio temps in a cron job every few minutes (I use 10 minutes).
Click to expand...

I've been looking at temps every once in a while and they seem pretty consistent. Pretty much this all/most of the time:

Code: 
2.4 GHz: 49°C  -  5 GHz: 49°C  -  CPU: 74°C

Happy to set up monitoring the temp, unsure how, would you be able to tell me?
 
After updating from Beta 3 to Beta 4 on saturday, here is my eye opening Down Load statistics....
1610451555501.png


1610452239918.png

speed test from a gig speed connection.
 
Last edited:
vvicked said:
Thanks @RMerlin.

On my AC86U, I just noticed that my DHCP reservation max is now only 64 instead of 128.
View attachment 29413
Click to expand...

By design. It is in the changelog. The NVRAM space is precious commodity. Space has to be gained. Use dnsmasq.conf.add to add reservations. It's easier, and more portable between system resets
 
nzwayne said:
Made up a test setup with a spare laptop and AX88U directly into a cable modem. Ran the tests (three on each setup), while watching a couple matches of rugby, so a good evening all around. Only had to run the ASUS Firmware Restoration once, for ASUS 386_41535 back to 384 level.
Shows conclusively for AX88U that Beta4 and RC10 386-41535 have issues. Also Beta4b about 10% slower then Beta4-gb9. & Beta3 when all TrendMicro apps enabled.

View attachment 29400
Click to expand...

I'm really curious if the difference between Beta4-gb9 and Beta4B-gb9 is just the time that you ran the tests seeing the difference is about ~10%
You have cable internet right? Were you nearing a peak time by the time you were doing the beta4b test?

If not, the fact that version beta4-gb9 had a downgraded trendmicro engine is probably making it faster in that version, but we would need more people to validate.
(Either way, I like the idea of having the most updated 386-41535 TM engine, but working correctly/as fast as possible instead of downgrading the TM engine completely to the version Beta 3 had, it's a best of both world's scenario for me)

I only pay to get a 300/20Mbps connection, and using Beta4B with all TrendMicro functions on; I have no performance degradation at my desktop connected to AX WiFi.
(I get on average around 293-294Mbps at my desktop over WiFi on a speedtest)

We would probably need someone else with a 1gig connection or higher to try and replicate these results. (Ideally on fiber so we can rule out any cable fluctuations!)
Again my slower connection package is fine on beta 4b, so no point in me trying to replicate as I won't see any higher anyways.
 
Last edited:
@RMerlin the setting Asus added for turning off the nodes leds, is not working on your firmware after reboot. The switch is off but the leds are on. Have to toggle on and off after reboot.
 
greggy101 said:
Has anyone had any problems flashing AX88U from beta4 to beta4b? Tried number of times, redownloaded the firmware, rebooted the router - no luck
Click to expand...

go back a few pages. Yes, lots of problems leaving 4. I had luck downgrading to asus stock firmware, then moving to 4b. Otherwise, folks are using the recovery utility.
 
bbunge said:
Cooling fan came this morning. AC86U running 384.19 CPU temp settled out to 56C from 69C. Dirty flash to 396.1 beta 4b and CPU temp went to 67C with fan.
QOS Bandwidth monitor "meters" do not register correctly. Status Internet Traffic bar "meter" does. No other negative observations right now.
Click to expand...

I noticed the same issue re. the meter on my AX88U running 386.1 b4.
 
Jeffrey Young said:
By design. It is in the changelog. The NVRAM space is precious commodity. Space has to be gained. Use dnsmasq.conf.add to add reservations. It's easier, and more portable between system resets
Click to expand...
Thanks for the information and tip. Stupid question, where was this change mentioned? I could not find it in the current change logs.
 
I just wanted to throw out a couple of things that I have observed for anyone that has installed the 386.1 Beta builds that is using AiMesh:
  1. I have discovered that after installing an upgrade on the primary router, performing a System Reboot (AiMesh >> System Settings >> System Reboot from primary router GUI) often clears up any anomalies with the AiMesh nodes.
  2. I have been using the latest Asus beta builds for the AiMesh nodes with the Merlin beta build on the primary router.
 
The largest most ambitious Merlin FW to date!! Good luck Merlin and Beta testers and thanks for all the great work!!
 
Status
Not open for further replies.

Similar threads

RMerlin
  • Locked
Beta Asuswrt-Merlin 386.14 beta is now available
2
Replies
35
Views
9K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 386.14 is now available for AC models
9 10 11
Replies
209
Views
32K
KGB7
K
RMerlin
  • Locked
Beta Asuswrt-Merlin 3004.388.6 Beta is now available
12 13 14
Replies
279
Views
43K
RMerlin
RMerlin
RMerlin
  • Locked
Beta Asuswrt-Merlin 3004.388.8 beta is now available
6 7 8
Replies
155
Views
30K
RMerlin
RMerlin
RMerlin
  • Locked
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices
2 3 4
Replies
70
Views
12K
RMerlin
RMerlin
Similar threads
Thread starter Title Forum Replies Date
B Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14 Asuswrt-Merlin 1
RMerlin Release Asuswrt-Merlin 386.14 is now available for AC models Asuswrt-Merlin 209
RMerlin Beta Asuswrt-Merlin 386.14 beta is now available Asuswrt-Merlin 35
RMerlin Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models Asuswrt-Merlin 79
RMerlin Beta Asuswrt-Merlin 386.13 beta is now available for AC models Asuswrt-Merlin 32
RMerlin Release Asuswrt-Merlin 386.12_6 is now available for AC models Asuswrt-Merlin 168
RMerlin Release Asuswrt-Merlin 3004.388.8_4 is now available Asuswrt-Merlin 72
RMerlin Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices Asuswrt-Merlin 62
F Several Questions Re:Asuswrt-Merlin Feature Implementation Asuswrt-Merlin 2
Yota How to enable port randomization in Asuswrt-Merlin? Asuswrt-Merlin 4

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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

Members online

Total: 955 (members: 23, guests: 932)
Top