What's new

[Beta] Asuswrt-Merlin 384.14 Beta 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.
@randomName, are you doing a full reset on b3 when testing?
 
@lilstone87, you confused me when you said 'from the other day' in your post earlier today. As that build was available yesterday. :)

Have been running that g6ed03020e2 beta 3 build without issues, btw.

Well for me he released that build on the 7th, reason I said the other day. But I understand you getting confused by what I said.

Also I seen the other user reply, saying that person used a self compiled build. Which ultimately, this thread is about Merlin's builds. Not to be rude, just pointing out. Also I appreciate the user mentioning that though, so this didn't turn into a longer, unneeded discussion. We all know the newer SDK for the AX88U is pretty broken right now. Hopefully all that stuff is corrected, and Merlin can include it with his 384.15 release build.
 
I think what might have happened is my QoS download table/speed might have got corrupted, my download speed dropped horribly from my manual input of 31mbps to 2.95mbps
 
Are your drivers and os version the latest?
Yes, using Windows 1909 fully up to date on a new OS install with the latest driver 21.50.1.1. I've tried reinstalling the driver and doing network resets in Windows.

With each drop out I must manually reconnect and I get capped at 40mb/s with poor latency until I reboot the PC (turning wifi on and off again doesn't help).

Each time the log is spammed with those "packet received from deauthed client" messages that I posted previously.

On beta 3 I can't stay connected for more than 15 minutes without it dropping out. On the previous version 384.13 I never see the issue, stable as wired Ethernet.
 
I could have sworn that in previous .13 versions, LAN ->DHCP Server -> lease time number was in minutes, but in 384.14B3, it appears to be seconds, so have just had to set lease time to 604800 - in order to get back to 7 days.

Can anyone confirm?
 
I could have sworn that in previous .13 versions, LAN ->DHCP Server -> lease time number was in minutes, but in 384.14B3, it appears to be seconds, so have just had to set lease time to 604800 - in order to get back to 7 days.

Can anyone confirm?

AFAIK it's always been in seconds. That said I havent checked it specifically in 384.13, neither can I remember reading any posts about thats been changed lately in the forum.
 
I could have sworn that in previous .13 versions, LAN ->DHCP Server -> lease time number was in minutes, but in 384.14B3, it appears to be seconds, so have just had to set lease time to 604800 - in order to get back to 7 days.

Can anyone confirm?
I’m still on .13 and my 1 day lease time is 86400. So seconds it is.
 
Have been running that g6ed03020e2 beta 3 build without issues, btw.
L&LD,
I have been running the same g6ed03020e2 beta 3 build for close to 11 hours ... :)

Edit: 1 day 20 hours
 
Last edited:
+1 Also have the beta 3 g6ed03020e2 new on my AX88U and everything for me works. Including bandwidth limiter. I'll run this a while and let you know how things go Eric.
 
If people are having VoIP issues, I recommend disabling the NAT helper for SIP (i.e. set the passthrough to Enabled instead of Enabled + NAT Helper).
 
Yes, using Windows 1909 fully up to date on a new OS install with the latest driver 21.50.1.1. I've tried reinstalling the driver and doing network resets in Windows.

With each drop out I must manually reconnect and I get capped at 40mb/s with poor latency until I reboot the PC (turning wifi on and off again doesn't help).

Each time the log is spammed with those "packet received from deauthed client" messages that I posted previously.

On beta 3 I can't stay connected for more than 15 minutes without it dropping out. On the previous version 384.13 I never see the issue, stable as wired Ethernet.
give a go at forgetting the network in your devices and re connecting them again, see if that helps at all.
 
Running self compiled 384.14_beta3-g907d21657b (7756 branch). Can confirm the DPI engine is working again and correctly identifying traffic. QOS is still broken but besides that everything else is running smooth, can't replicate any of the other issues people have been posting about the new SDK,

Switched to Merlins pre-compiled test build as it seems its on a different commit to the github repo, turns out QOS is working for downloads but not uploads.

To test this limited my connection to 10/10 with Adaptive QOS

8846146148.png
 
Code:
dnsmasq-script[25355]: connect error: No such file or directory
dnsmasq-script[25355]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
dnsmasq-script[25355]: connect error: No such file or directory
dnsmasq-script[25355]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
dnsmasq-script[25355]: connect error: No such file or directory
dnsmasq-script[25355]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
dnsmasq-script[25355]: connect error: No such file or directory
dnsmasq-script[25355]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
dnsmasq-script[25355]: connect error: No such file or directory
dnsmasq-script[25355]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
dnsmasq-script[25355]: connect error: No such file or directory
dnsmasq-script[25355]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
dnsmasq-script[25355]: connect error: No such file or directory
dnsmasq-script[25355]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
dnsmasq-script[25355]: connect error: No such file or directory
dnsmasq-script[25355]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.

the weird logs continue
Code:
 dnsmasq[4298]: failed to send packet: Operation not permitted
 dnsmasq-script[4298]: connect error: No such file or directory
 dnsmasq-script[4298]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No
dnsmasq[4298]: failed to send packet: Operation not permitted
dnsmasq[4298]: failed to send packet: Operation not permitted
dnsmasq[4298]: failed to send packet: Operation not permitted
dnsmasq[4298]: failed to send packet: Operation not permitted
dnsmasq[4298]: failed to send packet: Operation not permitted
 
Just installed 384.14_beta3 on my RT-AC86U:

- FTTH 100/50 Mb (Huawei upstream fiber modem in Automatic IP)
- DDNS disabled
- Samba share
- MiniDLNA
- AiProtection
- 12 devices connected (ethernet, WIFI 2.4 GHz and 5 GHz)
- Access point Netgear EX7700 connected

I did an update without resetting the router it went smoothly and all my settings are still here.
Now everything seems fine and I only have this in my system log:

May 5 07:05:11 kernel: nand: Could not find valid ONFI parameter page; aborting
May 5 07:05:11 kernel: brcmboard registered
May 5 07:05:11 kernel: genirq: Flags mismatch irq 36. 00000000 (brcm_36) vs. 00000000 (brcm_36)
May 5 07:05:11 kernel: pci 0000:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 07:05:11 kernel: pci 0000:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 07:05:11 kernel: pci 0001:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 07:05:11 kernel: pci 0001:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 07:05:11 kernel: gluebi (pid 1): gluebi_resized: got update notification for unknown UBI device 0 volume 0
May 5 07:05:11 kernel: broadcomThermalDrv brcm-therm: init (CPU count 2 2 2 2)
May 5 07:05:11 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
May 5 07:05:11 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
May 5 07:05:11 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex
May 5 07:05:11 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
May 5 07:05:11 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
May 5 07:05:11 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
May 5 07:05:11 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
May 5 07:05:11 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex
May 5 07:05:11 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
May 5 07:05:11 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
May 5 07:05:11 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
May 5 07:05:14 acsd: selected channel spec: 0x1004 (4)
May 5 07:05:14 acsd: Adjusted channel spec: 0x1004 (4)
May 5 07:05:14 acsd: selected channel spec: 0x1004 (4)
May 5 07:05:14 acsd: acs_set_chspec: 0x1004 (4) for reason APCS_INIT
May 5 07:05:15 Mastiff: init
May 5 07:05:15 wsdd2[1046]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
May 5 07:05:20 modprobe: module scsi_wait_scan not found in modules.dep
May 5 07:05:20 modprobe: module uas not found in modules.dep
May 5 07:05:20 modprobe: module mbcache not found in modules.dep
May 5 07:05:20 modprobe: module jbd not found in modules.dep
May 5 07:05:20 modprobe: module ext3 not found in modules.dep
May 5 07:05:20 modprobe: module ext4 not found in modules.dep
May 5 07:05:20 modprobe: module ext2 not found in modules.dep
May 5 07:05:20 modprobe: module btusbdrv not found in modules.dep
Dec 12 08:45:09 crond[964]: time disparity of 843999 minutes detected
Dec 12 08:49:53 wsdd2[1046]: Terminated received.


Great job as usual many thanks to @RMerlin !
 
Last edited:
Switched to Merlins pre-compiled test build as it seems its on a different commit to the github repo, turns out QOS is working for downloads but not uploads.

To test this limited my connection to 10/10 with Adaptive QOS

8846146148.png
Using bandwidth limiter, same firmware build, mine works fine. Set at 60/10. Tested on an active system with a multicast video stream and no pixels.

57378879.png
 
Probably dependent on your location, for me it sucks (closest server is more than 2.000 km away - Ireland!). No good for Europe...
 
If people are having VoIP issues, I recommend disabling the NAT helper for SIP (i.e. set the passthrough to Enabled instead of Enabled + NAT Helper).

BTW, what is the difference between "Enabled" and "Enabled+NAT Helper"? I've tried to look for some simple explanation, but didn't found.
 
Status
Not open for further replies.

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