What's new

Beta Asuswrt-Merlin 386.4 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.
There seems to be a bug on network map. Internet GUI shows disconnected. But internet is up and running for the client devices.

iv1pHR3.jpeg
Try to turn "Internet connection" button ON/OFF
 
I just downgraded back to stable 386.3_2. Both Asus and NO-IP update public ipv4 correctly (my ipv4 changes everytime I reboot router). So there must be something wrong with the latest beta.
That's one for @RMerlin to look at then possibly? Can you post which router you're using to assist the query? Still a little odd that this specific error, is a unique case - so far anyway, thus all info will be useful.
 
I can't add new AiMesh node after installing 486.4 beta using two RT-AX86U.
No matter I do router don't see any newly setup nodes.

Was running latest ASUS firmware FW_RT_AX86U_300438645934 on boith main router and node without any issues.

Upgraded to 386.4 beta and made reset in GUI. Then set up main router again without any issues.
Put AX86U mesh router 2-3 m from main router this has always worked before.

First tried reset button of and setup as new node (AX86U node still running FW_RT_AX86U_300438645934): not working Main Router could not find any AiMesh nodes.
Also tried on AiMesh node router: hard reset, Merlin 386.3-2, 386.4 beta soft and hard reset: Main Router could not find any AI mesh node.
Tried for hours no luck.

Gave up and put back FW_RT_AX86U_300438645934 on main router and restored saved setting.
Also put back FW_RT_AX86U_300438645934 on node router and made reset and setup as new node. No problem for main router to find the new AiMesh node again!

Something wrong with 386.4 beta?
Or am i missing something?
If I remember correctly I only made "full" GUI reset of main router Not hard reset after installing 386.4 beta..
Will try again making hard reset of main router when final 384.4 released.
If you can't get it working with wifi try to use ethernet cable. Should working just fine.
 
There seems to be a bug on network map. Internet GUI shows disconnected. But internet is up and running for the client devices.

iv1pHR3.jpeg
And because of the cosmetic internet status disconnected which relies with continues dns probe, Internet speed(Adaptive QOS/Internet Speed) is unuseable cause it thinks there is no connection. :( I believe "network monitoring" should be opt-in if needed and not forced to be enabled no matter what option you choose.
 
Last edited:
And even with this beta, the following messages appear in the log without interruption:

Code:
miniupnpd: PCP MAP: failed to add mapping UDP 5354->192.168.1.115:5353 'PCP MAP 2a55320bb95ecf4b029c5397'

Can it be fixed somehow and what do these entries actually mean?

:)
 
@RMerlin

Are the below messages because I am running the current beta or they exist in normal builds too ?

Dec 17 11:04:47 hostapd: eth7: STA (MAC address deleted) IEEE 802.11: disassociated
Dec 17 11:04:47 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind (MAC address deleted), status: 0, reason: Unspecified reason (1)
Dec 17 11:04:47 wlceventd: wlceventd_proc_event(534): eth7: Assoc (MAC address deleted), status: Successful (0)
Dec 17 11:04:47 hostapd: eth7: STA (MAC address deleted) IEEE 802.11: associated
Dec 17 11:04:47 hostapd: eth7: STA (MAC address deleted) RADIUS: starting accounting session E5CD0694AE224076
Dec 17 11:04:47 hostapd: eth7: STA (MAC address deleted) WPA: pairwise key handshake completed (RSN)
Dec 17 11:05:00 rc_service: service 3046:notify_rc restart_letsencrypt

Is there a way to filter the above ?
The wireless code is unchanged from upstream. I have never seen these messages before however, so I don't know if it's specific to your model, or specific to your configuration.

The Asus fix in this firmware 9.0.0.4_386_57877
They sent me patches for ddns last night, I need to review them and merge them in for beta 2.
I have recently bought an RT-AX58U v2 and have the possibility to exchange it. Do you think that in future versions it will be supported by Merlin?
There are currently no plan to support the RT-AX58U V2.
Internet GUI shows disconnected.
Make sure you don't interfere with the router trying to ping a Microsoft server to determine your connection state.
 
Hi, I have recently upgraded to the firmware 386.4_beta1 on my RT-AC88U and immediatly noticed that both download and upload graph almost stopped working and only register a couple of KB on the FlexQoS (The only mod I'm using) tab and nothing at all on Classification tab (Even with FlexQoS uninstalled), I think the entire thing just stopped working. I've fully uninstalled FlexQoS, done a factory restore and the bug persists.
 

Attachments

  • .png
    .png
    32.8 KB · Views: 118
Have it running for 20h. Everything works, the only problem in the system log is this message:
Code:
Dec 17 12:41:22 kernel: potentially unexpected fatal signal 11.
Dec 17 12:41:22 kernel: CPU: 1 PID: 2419 Comm: dcd Tainted: P           O    4.1.51 #2
Dec 17 12:41:22 kernel: Hardware name: Broadcom-v8A (DT)
Dec 17 12:41:22 kernel: task: ffffffc03e8faa40 ti: ffffffc02a448000 task.ti: ffffffc02a448000
Dec 17 12:41:22 kernel: PC is at 0xf6d8039c
Dec 17 12:41:22 kernel: LR is at 0x1dd14
Dec 17 12:41:22 kernel: pc : [<00000000f6d8039c>] lr : [<000000000001dd14>] pstate: 600f0010
Dec 17 12:41:22 kernel: sp : 00000000fffafa48
Dec 17 12:41:22 kernel: x12: 00000000000a2050
Dec 17 12:41:22 kernel: x11: 00000000f60ff024 x10: 00000000000a23c4
Dec 17 12:41:22 kernel: x9 : 00000000f60ff678 x8 : 00000000000a287c
Dec 17 12:41:22 kernel: x7 : 00000000f60ff6b0 x6 : 00000000000a2876
Dec 17 12:41:22 kernel: x5 : 0000000000000000 x4 : 00000000f60ff65c
Dec 17 12:41:22 kernel: x3 : 0000000000000000 x2 : 00000000fffafa24
Dec 17 12:41:22 kernel: x1 : 000000000007d75a x0 : 0000000000000000

It appears around every 8-9 minutes. It doesn't seem to cause any issues.
 
Dirty upgrade from 386.4-alpha3 on all devices. Still have the issue with Native IPV6 if GN 1 is used with Access Intranet set to Disable. This showed up in alpha2 and I assume that it's closed source and therefore not something that RMerlin can fix:( The only other nit-noid issue I've observed is that DFS cannot be disabled on the 5GHz-2 band. I can uncheck the "Auto select channel including DFS channels" box but as soon as I hit apply the checkmark comes back.
Thank You RMerlin :)
 
Dirty upgrade from 386.3-2 on AX86U router and AX86U AP. No problems.
 
@RMerlin started with connectivity issues and found this on my syslog:
Code:
Dec 17 14:53:27 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Dec 17 14:53:29 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 10 mbps full duplex
Dec 17 14:53:44 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Dec 17 14:53:47 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Dec 17 14:53:52 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Dec 17 14:53:55 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
 
I have the same issue as the OP above.

Dec 17 07:52:40 RT-AX88U-E770 kernel: x1 : 000000000007d75a x0 : 0000000000000000
Dec 17 08:44:27 RT-AX88U-E770 kernel: task: ffffffc02cac6b80 ti: ffffffc029864000 task.ti: ffffffc029864000
Dec 17 08:44:27 RT-AX88U-E770 kernel: x12: 00000000000a2050
Dec 17 09:09:56 RT-AX88U-E770 kernel: task: ffffffc02ecbf480 ti: ffffffc029864000 task.ti: ffffffc029864000
Dec 17 09:38:48 RT-AX88U-E770 kernel: potentially unexpected fatal signal 11.
Dec 17 09:38:48 RT-AX88U-E770 kernel: CPU: 1 PID: 3952 Comm: dcd Tainted: P O 4.1.51 #2
Dec 17 09:38:48 RT-AX88U-E770 kernel: Hardware name: Broadcom-v8A (DT)
Dec 17 09:38:48 RT-AX88U-E770 kernel: task: ffffffc02fef6a80 ti: ffffffc0236a8000 task.ti: ffffffc0236a8000
Dec 17 09:58:01 RT-AX88U-E770 kernel: x12: 00000000000a2050
Dec 17 10:20:13 RT-AX88U-E770 kernel: PC is at 0xf6f3639c
Dec 17 10:20:13 RT-AX88U-E770 kernel: pc : [<00000000f6f3639c>] lr : [<000000000001dd14>] pstate: 600f0010
Dec 17 10:20:13 RT-AX88U-E770 kernel: sp : 00000000ffb0a838
Dec 17 11:21:00 RT-AX88U-E770 kernel: potentially unexpected fatal signal 11.
Dec 17 11:21:00 RT-AX88U-E770 kernel: CPU: 1 PID: 21984 Comm: dcd Tainted: P O 4.1.51 #2
Dec 17 11:21:00 RT-AX88U-E770 kernel: Hardware name: Broadcom-v8A (DT)
Dec 17 11:32:53 RT-AX88U-E770 kernel: x12: 00000000000a2050
Dec 17 11:36:50 RT-AX88U-E770 kernel: pc : [<00000000f719639c>] lr : [<000000000001dd14>] pstate: 600f0010
Dec 17 12:00:54 RT-AX88U-E770 kernel: task: ffffffc032b2f4c0 ti: ffffffc025964000 task.ti: ffffffc025964000
Dec 17 12:55:17 RT-AX88U-E770 kernel: task: ffffffc0292f95c0 ti: ffffffc025964000 task.ti: ffffffc025964000
Dec 17 13:02:57 RT-AX88U-E770 kernel: LR is at 0x1dd14

Is this just Broadcom logging spam or is the "fatal signal 11" a problem? I remember the AC86U had a dcd tainted issue as well. Is this similar?
 
@RMerlin started with connectivity issues and found this on my syslog:
Code:
Dec 17 14:53:27 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Dec 17 14:53:29 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 10 mbps full duplex
Dec 17 14:53:44 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Dec 17 14:53:47 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Dec 17 14:53:52 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Dec 17 14:53:55 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Clients dropping to 10 Mbps usually indicate that client went into sleep mode and kept the link active at the lowest rate possible just so it can be available for Wake on Lan with minimal power usage. I don't see anything wrong there, whatever you have plugged in that port did that.
 
dcd crashes have been happening for years. It's proprietary Trend Micro code, I have no control over it (neither does Asus AFAIK).
 
From what I read on Asus website, Pihole's DNS can be directly added at WAN from this build onward (instead of putting them in the LAN DHCP section with DNS Filter - Router set to ON?)
 
From what I read on Asus website, Pihole's DNS can be directly added at WAN from this build onward (instead of putting them in the LAN DHCP section with DNS Filter - Router set to ON?)
Interesting. Wonder if this still presents an issue with a feed back loop with requests when Conditional Forwarding is enabled within Pi-Hole.

Link to Asus:

[Wireless Router] How to configure Router to use Pi-Hole?

Before starting the setup, please check the firmware version of your router.

If your router firmware version >= 3.0.0.4.386.45898

Please assign the pi-hole IP in the WAN DNS setting.

Step1:
Connect your PC to ASUS router via Wi-Fi or Ethernet cable.

Step2: Open a web browser and navigate to Web GUI (http://router.asus.com).

Enter your login username and password on the login page and then click [Sign In].

f7cfdad6-ff14-4f39-ab01-d9ac1f827698.png


Note: Please refer to [Wireless Router] How to enter the router's GUI to learn more.

Step3: Go to [WAN] > [Internet Connection] tab.

Step4: Set Connect to DNS Server automatically as [No]

Step5: Enter device IP address on DNS server and click [Apply] to save.

b404c938-448a-4377-a5ab-fa91383314de.png
 
Beta1. AX68U. DDNS to no-ip.com doesn't work with IPv6 enabled (I see that noted on page 1) and I can't add a freshly reset AC68U as AiMesh node.
 
Status
Not open for further replies.

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