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.
When you say there may be a problem in the Wi-Fi setup, what exactly should I be looking for?

Sent from my SM-G955F using Tapatalk
You need to understand your scenario. Hard to help. But keep watching and configuring as the FW update. Remember, this is an FW beta, nothing can be expected for stability. Another, even if it has the stable version, will never have the same scenario as the previous FW. There is the possibility of adding new features.
 
Broadcom drivers like Singapore. :D
 
Great thanks for that info. There is a field under it also, titled rt-Ac 86u domain name, I leave that blank, should I be inserting something into that field?

It can be kept empty, but personally I recommend entering something like myhome.lan. If you were to connect remotely back home, you'd be able to easily resolve LAN hostnames by specifying the domain name (which will instruct your client it should use the VPN's DNS for resolving that hostname).
 
RT-AC86U, beta 2, my PC suddenly disconnected Etherhet port, have seen this happen for the first time:

Nov 27 16:29:41 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.

After manual plugging connector out/in it is running again:

Nov 27 16:29:43 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
 
RT-AC86U, beta 2, my PC suddenly disconnected Etherhet port, have seen this happen for the first time:

Nov 27 16:29:41 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.

After manual plugging connector out/in it is running again:

Nov 27 16:29:43 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
I see that almost daily, thanks to my Sony Vizio TV connected via ethernet. It checks for updates on its own schedule now, previously I had to check manually.

And recently my main desktop Linux PC (ethernet) has had numerous kernel updates for vulnerabilities, so I need to reboot that machine for a new kernel.

I had it happen very often due to a bad ethernet cable as well, with connectors that suddenly would fail and connect. Replacing the cable solved it.
Code:
Nov 24 19:51:36 RT-AC86U-4608 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Nov 24 19:51:36 RT-AC86U-4608 kernel: br0: port 4(eth4) entered disabled state
Nov 24 19:51:39 RT-AC86U-4608 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 10 mbps full duplex
Nov 24 19:51:39 RT-AC86U-4608 kernel: br0: port 4(eth4) entered listening state
Nov 24 19:51:39 RT-AC86U-4608 kernel: br0: port 4(eth4) entered listening state
Nov 24 19:51:41 RT-AC86U-4608 kernel: br0: port 4(eth4) entered learning state
Nov 24 19:51:43 RT-AC86U-4608 kernel: br0: topology change detected, propagating
Nov 24 19:51:43 RT-AC86U-4608 kernel: br0: port 4(eth4) entered forwarding state
Nov 24 19:51:49 RT-AC86U-4608 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Nov 24 19:51:49 RT-AC86U-4608 kernel: br0: port 4(eth4) entered disabled state
Nov 24 19:51:52 RT-AC86U-4608 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Nov 24 19:51:52 RT-AC86U-4608 kernel: br0: port 4(eth4) entered listening state
Nov 24 19:51:52 RT-AC86U-4608 kernel: br0: port 4(eth4) entered listening state
Nov 24 19:51:54 RT-AC86U-4608 kernel: br0: port 4(eth4) entered learning state
Nov 24 19:51:56 RT-AC86U-4608 kernel: br0: topology change detected, propagating
Nov 24 19:51:56 RT-AC86U-4608 kernel: br0: port 4(eth4) entered forwarding state
 
RT-AC86U, beta 2, my PC suddenly disconnected Etherhet port, have seen this happen for the first time:

Nov 27 16:29:41 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.

After manual plugging connector out/in it is running again:

Nov 27 16:29:43 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex

I had a similar experience a while ago with stock fw 384.6436, so I suspect it might be fw related.

https://www.snbforums.com/threads/asus-rt-ax88u-firmware-version-3-0-0-4-384-6436.59203/#post-518367

Edit:
Funny thing, since in my case this just was a testsetup, the only thing connected to the router was one win pc connected to switch port 1 on the router... So I don't even understand how the port in question was in use...

Was your pc connected to switch port 3 when it happened ?
 
Last edited:
I had used Merlinwrt with AC68U for 2 years without any problem. However since 384.14 beta 1, the internet status has been displayed as Disconnected (although it was actually fully connected to internet) and NTP time sync service neither worked. Let's Encrypt challenge is still facing an auth error even on 384.14 beta 2. Reset didn't work.

Both being displayed as disconnected and NTP bugs are fixed with rollback to 384.13 build or earlier.

And I found these bugs are reproduced on ASUS's latest stock firmware. Soo I guess it's came from asus' codes..

I also have 2 RT-AC68U that on any 384.14 alpha or beta build, the internet status shows as disconnected even though it's connected but on 384.13, it displays correctly. Funny part is that my RT-AC66U B1s don't have that issue.

Also I noticed that on 384.14, when applying changes any change to the admin\system page, if SSH is on, it complains that "This port is for: SSH" and you have to change the SSH port before you can apply the changes. Weird part is that on the next save, it doesn't complain but if you do another save, it complains again.
 
FW 384.14_b2 running solid for 36 hours already. Almost ready for release IMHO.
 
@RMerlin, Asus has recently released new GPL for RT-AX88U, would consider or merge this version before release of 384.14 or it would be for next release.
 
@RMerlin, Asus has recently released new GPL for RT-AX88U, would consider or merge this version before release of 384.14 or it would be for next release.
Too early to tell, I started analyzing it yesterday morning.

Sent from my SM-T720 using Tapatalk
 
RT-AC86U, beta 2, my PC suddenly disconnected Etherhet port, have seen this happen for the first time:

Nov 27 16:29:41 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.

After manual plugging connector out/in it is running again:

Nov 27 16:29:43 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
In my experience this could be a unlucky coincidence. Its probably is a bad or marginal cable. Depending on how the 'other side' chooses to respond, it can fall back to 100B-TX or some other non functional condition. Most common with old drivers (speaking about Windows) I would see linkup/link down conditions every time it would flip flop between 1000B-TX and 100B-TX.
 
Dirty upgrade from 14B1. Updated both routers (as in signature) via the WebUI, first the 88U then the 86U. Left the USB plugged in. Both upgraded without issue. LED light (on/off) still functions as on B1. LE cert updated as advertised. Log nice and clean and all seems to be normal thus far. >1 hour on B2.

Thanks!
 
I uploaded a very early test builds with the new AX SDK merged in. This has only received some basic testing (i.e. my two wifi devices over the past two hours).

https://www.asuswrt-merlin.net/test-builds

I haven't decided yet if I will go with it for 384.14 or not. It will depend how much extended testing it requires, since the 384.14 dev cycle has already been pretty long, and was getting closer to its end.
 
It can be kept empty, but personally I recommend entering something like myhome.lan. If you were to connect remotely back home, you'd be able to easily resolve LAN hostnames by specifying the domain name (which will instruct your client it should use the VPN's DNS for resolving that hostname).
Thanks again, for the advice and explanation, its a sound tip.
 
I uploaded a very early test builds with the new AX SDK merged in. This has only received some basic testing (i.e. my two wifi devices over the past two hours).

https://www.asuswrt-merlin.net/test-builds

I haven't decided yet if I will go with it for 384.14 or not. It will depend how much extended testing it requires, since the 384.14 dev cycle has already been pretty long, and was getting closer to its end.

On it boss, will update if something unexpected happens.

Eric, my bootloader was upgraded to 1010 from 1009, did it happen in your case?
 
Last edited:
I uploaded a very early test builds with the new AX SDK merged in. This has only received some basic testing (i.e. my two wifi devices over the past two hours).

https://www.asuswrt-merlin.net/test-builds

I haven't decided yet if I will go with it for 384.14 or not. It will depend how much extended testing it requires, since the 384.14 dev cycle has already been pretty long, and was getting closer to its end.
Initial start working with diversion/skynet, so far good except for a kernel error.
Code:
 Nov 27 22:57:39 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
 
On it boss, will update if something unexpected happens.

Eric, my bootloader was upgraded to 1010 from 1009, did it happen in your case?

I don't remember what mine was before, but it's currently on 1.0.1.0.
 
I don't remember what mine was before, but it's currently on 1.0.1.0.

i'm on 1009 on 384.13 so hawk looks to be correct.
 
Initial start working with diversion/skynet, so far good except for a kernel error.
Code:
 Nov 27 22:57:39 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set

Don't pay too much attention to the system log content, the new hostapd is very verbose.
 
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