What's new

[Beta 384/NG] Asuswrt-merlin 384.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.
My RT-AC3200 has an issue where every time I change a wifi related setting, the wifi never turns back on until I remove & reapply power. I did accomplish a factory reset on it.


Code:
Mar  2 20:54:08 miniupnpd[620]: No allowed eport for NAT-PMP 37370 udp->192.168.1.4:9
Mar  2 20:56:21 rc_service: httpd 325:notify_rc restart_wireless
Mar  2 20:56:22 kernel: br0: port 2(eth2) entering forwarding state
Mar  2 20:56:22 kernel: device eth2 left promiscuous mode
Mar  2 20:56:22 kernel: br0: port 2(eth2) entering disabled state
Mar  2 20:56:22 kernel: br0: port 3(eth1) entering forwarding state
Mar  2 20:56:22 kernel: device eth1 left promiscuous mode
Mar  2 20:56:22 kernel: br0: port 3(eth1) entering disabled state
Mar  2 20:56:22 kernel: br0: port 4(eth3) entering forwarding state
Mar  2 20:56:22 kernel: device eth3 left promiscuous mode
Mar  2 20:56:22 kernel: br0: port 4(eth3) entering disabled state
Mar  2 20:56:22 kernel: br0: port 5(wl0.1) entering forwarding state
Mar  2 20:56:22 kernel: device wl0.1 left promiscuous mode
Mar  2 20:56:22 kernel: br0: port 5(wl0.1) entering disabled state
Mar  2 20:56:24 kernel: device eth2 entered promiscuous mode
Mar  2 20:56:24 kernel: br0: port 2(eth2) entering listening state
Mar  2 20:56:24 kernel: br0: port 2(eth2) entering listening state
Mar  2 20:56:24 kernel: device eth1 entered promiscuous mode
Mar  2 20:56:24 kernel: br0: port 3(eth1) entering listening state
Mar  2 20:56:24 kernel: br0: port 3(eth1) entering listening state
Mar  2 20:56:24 kernel: device eth3 entered promiscuous mode
Mar  2 20:56:24 kernel: br0: port 4(eth3) entering listening state
Mar  2 20:56:24 kernel: br0: port 4(eth3) entering listening state
Mar  2 20:56:24 kernel: device wl0.1 entered promiscuous mode
Mar  2 20:56:24 kernel: br0: port 5(wl0.1) entering listening state
Mar  2 20:56:24 kernel: br0: port 5(wl0.1) entering listening state
Mar  2 20:56:28 kernel: br0: port 2(eth2) entering learning state
Mar  2 20:56:28 kernel: br0: port 3(eth1) entering learning state
Mar  2 20:56:28 kernel: br0: port 4(eth3) entering learning state
Mar  2 20:56:28 kernel: br0: port 5(wl0.1) entering learning state
Mar  2 20:56:32 kernel: br0: topology change detected, sending tcn bpdu
Mar  2 20:56:32 kernel: br0: port 2(eth2) entering forwarding state
Mar  2 20:56:32 kernel: br0: topology change detected, sending tcn bpdu
Mar  2 20:56:32 kernel: br0: port 3(eth1) entering forwarding state
Mar  2 20:56:32 kernel: br0: topology change detected, sending tcn bpdu
Mar  2 20:56:32 kernel: br0: port 4(eth3) entering forwarding state
Mar  2 20:56:32 kernel: br0: topology change detected, sending tcn bpdu
Mar  2 20:56:32 kernel: br0: port 5(wl0.1) entering forwarding state
Mar  2 20:57:40 rc_service: httpd 325:notify_rc restart_wireless
Mar  2 20:57:40 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 20:57:55 rc_service: skip the event: restart_wireless.
Mar  2 20:58:46 rc_service: httpd 325:notify_rc restart_wireless
Mar  2 20:58:46 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 20:59:01 rc_service: skip the event: restart_wireless.
Mar  2 21:00:34 rc_service: httpd 325:notify_rc restart_wireless
Mar  2 21:00:34 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 21:00:49 rc_service: skip the event: restart_wireless.
Mar  2 21:01:07 dnsmasq-dhcp[315]: DHCPDISCOVER(br0) 40:e2:30:51:ab:5b
Mar  2 21:01:07 dnsmasq-dhcp[315]: DHCPOFFER(br0) 192.168.1.230 40:e2:30:51:ab:5b
Mar  2 21:01:07 dnsmasq-dhcp[315]: DHCPREQUEST(br0) 192.168.1.230 40:e2:30:51:ab:5b
Mar  2 21:01:07 dnsmasq-dhcp[315]: DHCPACK(br0) 192.168.1.230 40:e2:30:51:ab:5b Blossom-AB5B
Mar  2 21:01:40 kernel: Init chrdev /dev/detector with major 190
Mar  2 21:01:40 kernel: tdts: tcp_conn_max = 8000
Mar  2 21:01:40 kernel: tdts: tcp_conn_timeout = 300 sec
Mar  2 21:01:54 rc_service: httpd 325:notify_rc restart_wrs;restart_firewall
Mar  2 21:01:54 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 21:01:57 kernel: SHN Release Version: 2.0.1 3529123_patch
Mar  2 21:01:57 kernel: UDB Core Version: 0.2.14 r3529123
Mar  2 21:01:57 kernel: Init chrdev /dev/idpfw with major 191
Mar  2 21:01:57 kernel: IDPfw: IDPfw is ready
Mar  2 21:01:57 kernel: sizeof forward pkt param = 192
Mar  2 21:02:09 rc_service: skip the event: restart_wrs;restart_firewall.
Mar  2 21:02:13 hour_monitor: daemon is starting
Mar  2 21:03:12 rc_service: httpd 325:notify_rc restart_qos;restart_firewall
Mar  2 21:03:12 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 21:03:27 rc_service: skip the event: restart_qos;restart_firewall.
 
Anyone use the WTFast game boost service? I've been testing it out the last couple of days running the 384.4 beta firmware and just noticed that my CPU load for the 2nd core on my RT-AC86U is pegged at 100%.

I'm using it on my PS4 and not playing the game at the time the 2nd core usage is max. I deleted my game profile and logged out of the service at load immediately fell back to 0%.
 
Last edited:
My RT-AC3200 has an issue where every time I change a wifi related setting, the wifi never turns back on until I remove & reapply power. I did accomplish a factory reset on it.


Code:
Mar  2 20:54:08 miniupnpd[620]: No allowed eport for NAT-PMP 37370 udp->192.168.1.4:9
Mar  2 20:56:21 rc_service: httpd 325:notify_rc restart_wireless
Mar  2 20:56:22 kernel: br0: port 2(eth2) entering forwarding state
Mar  2 20:56:22 kernel: device eth2 left promiscuous mode
Mar  2 20:56:22 kernel: br0: port 2(eth2) entering disabled state
Mar  2 20:56:22 kernel: br0: port 3(eth1) entering forwarding state
Mar  2 20:56:22 kernel: device eth1 left promiscuous mode
Mar  2 20:56:22 kernel: br0: port 3(eth1) entering disabled state
Mar  2 20:56:22 kernel: br0: port 4(eth3) entering forwarding state
Mar  2 20:56:22 kernel: device eth3 left promiscuous mode
Mar  2 20:56:22 kernel: br0: port 4(eth3) entering disabled state
Mar  2 20:56:22 kernel: br0: port 5(wl0.1) entering forwarding state
Mar  2 20:56:22 kernel: device wl0.1 left promiscuous mode
Mar  2 20:56:22 kernel: br0: port 5(wl0.1) entering disabled state
Mar  2 20:56:24 kernel: device eth2 entered promiscuous mode
Mar  2 20:56:24 kernel: br0: port 2(eth2) entering listening state
Mar  2 20:56:24 kernel: br0: port 2(eth2) entering listening state
Mar  2 20:56:24 kernel: device eth1 entered promiscuous mode
Mar  2 20:56:24 kernel: br0: port 3(eth1) entering listening state
Mar  2 20:56:24 kernel: br0: port 3(eth1) entering listening state
Mar  2 20:56:24 kernel: device eth3 entered promiscuous mode
Mar  2 20:56:24 kernel: br0: port 4(eth3) entering listening state
Mar  2 20:56:24 kernel: br0: port 4(eth3) entering listening state
Mar  2 20:56:24 kernel: device wl0.1 entered promiscuous mode
Mar  2 20:56:24 kernel: br0: port 5(wl0.1) entering listening state
Mar  2 20:56:24 kernel: br0: port 5(wl0.1) entering listening state
Mar  2 20:56:28 kernel: br0: port 2(eth2) entering learning state
Mar  2 20:56:28 kernel: br0: port 3(eth1) entering learning state
Mar  2 20:56:28 kernel: br0: port 4(eth3) entering learning state
Mar  2 20:56:28 kernel: br0: port 5(wl0.1) entering learning state
Mar  2 20:56:32 kernel: br0: topology change detected, sending tcn bpdu
Mar  2 20:56:32 kernel: br0: port 2(eth2) entering forwarding state
Mar  2 20:56:32 kernel: br0: topology change detected, sending tcn bpdu
Mar  2 20:56:32 kernel: br0: port 3(eth1) entering forwarding state
Mar  2 20:56:32 kernel: br0: topology change detected, sending tcn bpdu
Mar  2 20:56:32 kernel: br0: port 4(eth3) entering forwarding state
Mar  2 20:56:32 kernel: br0: topology change detected, sending tcn bpdu
Mar  2 20:56:32 kernel: br0: port 5(wl0.1) entering forwarding state
Mar  2 20:57:40 rc_service: httpd 325:notify_rc restart_wireless
Mar  2 20:57:40 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 20:57:55 rc_service: skip the event: restart_wireless.
Mar  2 20:58:46 rc_service: httpd 325:notify_rc restart_wireless
Mar  2 20:58:46 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 20:59:01 rc_service: skip the event: restart_wireless.
Mar  2 21:00:34 rc_service: httpd 325:notify_rc restart_wireless
Mar  2 21:00:34 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 21:00:49 rc_service: skip the event: restart_wireless.
Mar  2 21:01:07 dnsmasq-dhcp[315]: DHCPDISCOVER(br0) 40:e2:30:51:ab:5b
Mar  2 21:01:07 dnsmasq-dhcp[315]: DHCPOFFER(br0) 192.168.1.230 40:e2:30:51:ab:5b
Mar  2 21:01:07 dnsmasq-dhcp[315]: DHCPREQUEST(br0) 192.168.1.230 40:e2:30:51:ab:5b
Mar  2 21:01:07 dnsmasq-dhcp[315]: DHCPACK(br0) 192.168.1.230 40:e2:30:51:ab:5b Blossom-AB5B
Mar  2 21:01:40 kernel: Init chrdev /dev/detector with major 190
Mar  2 21:01:40 kernel: tdts: tcp_conn_max = 8000
Mar  2 21:01:40 kernel: tdts: tcp_conn_timeout = 300 sec
Mar  2 21:01:54 rc_service: httpd 325:notify_rc restart_wrs;restart_firewall
Mar  2 21:01:54 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 21:01:57 kernel: SHN Release Version: 2.0.1 3529123_patch
Mar  2 21:01:57 kernel: UDB Core Version: 0.2.14 r3529123
Mar  2 21:01:57 kernel: Init chrdev /dev/idpfw with major 191
Mar  2 21:01:57 kernel: IDPfw: IDPfw is ready
Mar  2 21:01:57 kernel: sizeof forward pkt param = 192
Mar  2 21:02:09 rc_service: skip the event: restart_wrs;restart_firewall.
Mar  2 21:02:13 hour_monitor: daemon is starting
Mar  2 21:03:12 rc_service: httpd 325:notify_rc restart_qos;restart_firewall
Mar  2 21:03:12 rc_service: waitting "restart_wireless" via httpd ...
Mar  2 21:03:27 rc_service: skip the event: restart_qos;restart_firewall.

Exactly the same as me... restart WiFi seems to get stuck...


Sent from my iPad using Tapatalk
 
I have a ac3100 using 384.4 beta_1. I noticed 2 log entries that puzzle me. Last night while asleep my routers wireless service retsarted no know reason:
Code:
Mar  2 02:00:31 rc_service: rc 14254:notify_rc restart_wrs
Mar  2 02:00:48 kernel: ERR[parse_qos_conf:932] Can't set new QoS conf while QoS is started!
Mar  2 02:00:48 kernel: ERR[ioctl_iqos_op_config:3592] parse qos_conf error!!
Mar  2 02:00:48 kernel: ioctl_iqos_op_config() fail!
Mar  2 02:00:48 kernel: ERR[qos_start:3344] QoS is already started!
Mar  2 02:00:48 kernel: ioctl_iqos_op_switch(1) fail!
The second one happened earlier in the day, I have no clue:
Code:
Mar  1 17:49:50 rc_service: httpd 429:notify_rc reset_vp_db
Is this stuff closed source? Are these logs normal at this point?
EDIT: My up time is almost 3 days if that counts as good information.
My uptime is almost 4 days now. The errors above have not been seen since. Impressed with stability taking into account of the massive work it took to get here. Keep on keeping on!
 
Exactly the same as me... restart WiFi seems to get stuck...


Sent from my iPad using Tapatalk

I'm assuming something causes the router to fail to fully go back up after changes are made. A power cycle stops this until the next change. I notice when I do make changes, the CPU goes up to 100% as opposed to being around 10%.
 
Updated my AC88U today (from 380.69.2):
  1. Hard reset before upgrading (red button)
  2. Upgrade
  3. Hard reset after upgrading (red button)
The routeur has been working flawlessly (except for bugs that have been here for ages; see below).
Note however that my use case covers only the WiFi and IP stuff:
  • I don't use and disabled all the ASUS *ware (from the UI and using killall; see below)
  • I perform most iptables/ebtables/robocfg stuff manually
  • I use only Static Routes function in the UI
Wireless *IP* bandwidth (iperf) using a MIMO-2x2 802.11n 5GHz client (Intel N6235) is ~180-200Mb/s, once AMPDU TX Optimization enabled on both AP and client.

BEWARE! The BCM5301x switch topology has changed between 380.69.2 and 384.4 versions!
Physical (labels) <-> RoboCfg ports
  • 380.69: 1:3 2:2 3:1 4:0 5-8:5 ?:7 WAN:4 CPU:8
  • 384.4: 1:3 2:2 3:1 4:0 5-8:5 WAN:4 CPU:7
Physical ports 5-8 (RoboCfg 5) are "offloaded" to a separate Realtek switch and can NOT be configured individually.

As for BUGS:
  • HTTPS interface is still extremely sluggish (close to unusable)
  • Traditional QoS is still broken: ingress traffic default to 'lowest' (egress) queue
  • QoS always assumes a /24 LAN

As for Traditional QoS:
The default root qdisc class/queue (tc qdisc show dev eth0) defaults to 40, iow. the class/queue used for the 'lowest' priority traffic. Since this default class is also used for 'ingress' traffic, bandwidth allocation between 'Upload' (egress) and 'Download' (ingress) is mixed up. Unfortunately, attempting to fix the ASUS-implemented QoS with a 'tc qdisc change ...' does not work.
The hardcoded /24 LAN can be fixed thanks to the following script (in 'firewall-start' script):
rnum="$(iptables --line-numbers -t mangle -nvL QOSO | grep 'CONNMARK .* 172.16.0.0/24' | cut -d' ' -f1)"
[ -n "${rnum}" ] && iptables -t mangle -R QOSO ${rnum} -d 172.16.0.0/12 -j CONNMARK --set-xmark 0x6/0x7
rnum="$(iptables --line-numbers -t mangle -nvL QOSO | grep 'RETURN .* 172.16.0.0/24' | cut -d' ' -f1)"
[ -n "${rnum}" ] && iptables -t mangle -R QOSO ${rnum} -d 172.16.0.0/12 -j RETURN
The CONNMARK restore/RETURN entries in the QOSO chain also appears wrong and can be fixed with:
rnum="$(iptables --line-numbers -t mangle -nvL QOSO | grep 'connmark match' | cut -d' ' -f1)"
[ -n "${rnum}" ] && iptables -t mangle -R QOSO ${rnum} -m connmark ! --mark 0x0/0x7 -j RETURN

As for services I killed (in 'services-start') without affecting the WiFi/IP part of the router:
  • killall infosvr # InfoSvr (ASUS Wireless Router Device Discovery)
  • killall ots # OTS (ASUS One-Touch Setup)
  • killall lpd # LPD (Line Printer Daemon)
  • killall u2ec # U2EC (USB-over-Ethernet printing daemon)
  • killall nt_monitor # Notifications Center (ASUS AiProtection ?)
  • killall nt_center
  • killall nt_actMail
  • killall lldpd # LLDP (Link Layer Discovery Protocol)
  • killall lld2d # LLTP (Link Layer Topology Discovery)
  • killall avahi-daemon # mDNS (Avahi)
  • killall protect_srv # ? (TrendMicro stuff ?)
  • killall wpsaide # WPS Helper
After trying (and miserably failing with) the 382.x branch, the 384.4 is fresh air!

Thanks @RMerlin

EDITED: Corrected Traditional QoS status
 
Last edited:
I'm assuming something causes the router to fail to fully go back up after changes are made. A power cycle stops this until the next change. I notice when I do make changes, the CPU goes up to 100% as opposed to being around 10%.

Can you see with "top" which process is using the CPU?
 
The SMB changes would not have any effect on network connected devices would they eg ubuntu accessing a windows share? I think no but just want to rule it out of an issue I have just been having, well an absolute clusterfuc* to be honest.

Some devices stopped connecting to windows 10 shares eg ubuntu then when I rebooted windows I got a inaccessible boot device blue screen I could not recover from, rebuild it was.

I actually think it was a lovely windows update that caused this, disabling smb1 which I have re-enabled in windows after updating to the latest version again and now all is okay, strange though that Ubuntu oh and the shield dont use smb2 no?
 
Hey guys quick question for everyone.. I played with 308/379 official few times when it came out and was impressed with the performance/stability but was missing merlins touch and features.. Hows the beta coming along from a features perspective? I've been following very closely and not sure I can hold out much longer! It appears very stable for the most part but am curious what features are left to be implemented of merlins such as wireless log, site survey etc?
 
Hey guys quick question for everyone.. I played with 308/379 official few times when it came out and was impressed with the performance/stability but was missing merlins touch and features.. Hows the beta coming along from a features perspective? I've been following very closely and not sure I can hold out much longer! It appears very stable for the most part but am curious what features are left to be implemented of merlins such as wireless log, site survey etc?
Wireless log and site survey are working real well. Beta 1 is very solid. I installed it right over 384.3 and didn’t miss a beat. I’m sure future betas will tweak any remaining issues, that Merlin mentioned in the first post of this thread. Go for it. :)
 
Can you see with "top" which process is using the CPU?

I'll have to figure how how to do that, & I should be able to reproduce the issue once I figure out top
Edit: that was easy, ssh & type "top"...I'll reproduce it again after the family goes to sleep.

Naturally, after a day of running fine, I can't reproduce the issue :/
 
Last edited:
Here is something I saw very frequently in my syslog with 384.3 on my AC86U. I saw over 50 kernel: eth_ DOWN/UP in about 24 hours. I just got the AC86U two days ago and installed AsusWRT Merlin before I ever put the router online, and configured from scratch using screen captures from my AC68U for refernce.

I updated to 384.4 beta 1 about three hours ago and have not see that kernel: eth_ DOWN/UP entry even a single time.

I did not see what solved this in the changelog, but very happy to see these gone. Thank you for the fix.

Code:
Mar  3 07:46:23 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Mar  3 07:46:26 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 10 mbps full duplex
Mar  3 07:47:06 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Mar  3 07:47:09 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex


Mar  3 11:57:45 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
Mar  3 12:02:21 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 100 mbps full duplex
Mar  3 12:02:26 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
Mar  3 12:02:29 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 100 mbps full duplex
Mar  3 12:19:59 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
Mar  3 12:20:04 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 100 mbps full duplex
Mar  3 12:20:09 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
Mar  3 12:20:12 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 100 mbps full duplex
 
I did not see what solved this in the changelog, but very happy to see these gone. Thank you for the fix.

This is a hardware issue, not a firmware issue. Whatever connected on that port is constantly flapping. Try replacing that Ethernet cable.
 
This is a hardware issue, not a firmware issue. Whatever connected on that port is constantly flapping. Try replacing that Ethernet cable.
Interesting, all three cables in use arrived two days ago with the router. I have nothing on port 4 and that is where most errors were, but I saw this on ports 3 and 4 in the syslog. I did move cables between computer, tv and chromecast before those errors disappeared - i'll keep an eye on it. I have more long cables on order to arrive in a few days. Thank you.
 
FYI, prebuild file of letsencrypt on GT-AC5300 is compatible with RT-AC86U.

https://github.com/blackfuel/asuswr...ter/libletsencrypt/prebuild/libletsencrypt.so

I simply replaced it with your repo's one and turned on letsencrypt for RT-AC86U.
no problem at all.

Have you noticed any issues after enabling this on the RT-AC86U?

noob- Is there a place to download the complied version? I only use smartphones and don't have a computer. If not I will wait for Merlin to approve and update his builds. Thanks
 
Installed 384.4 beta 1 on my RT-AC68U. Full factory reset, memory wipe. Tried my normal VLAN script that makes LAN port 4 a VLAN port with a separate subnet and DHCP server. It works just fine in RT-AC68U_380.69_2.trx. Unfortunately on this build, this doesn't work.
#!/bin/sh
# lan ports 1-3 assigned to vlan1, 3 tagged and untagged traffic supported
robocfg vlan 1 ports "1 2 3t 5t"
# port 4 to vlan20 - will tag untagged packets with VLAN20, port 3 can ingest pre-tagged traffic
robocfg vlan 20 ports "3t 4 5t"
# add vlan 20 to eth0
vconfig add eth0 20
# give VLAN 20 an IP address to act as gateway for subnet
ifconfig vlan20 192.168.85.1 netmask 255.255.255.0 up
...

After putting those lines in, normally I can setup a static IP on a PC of 192.168.85.2 and ping 85.1 on LAN 4. The commands are accepted ok, but the port doesn't respond to anything. Anyone know of a change in the new code that makes robocfg behave different?
 
The SMB changes would not have any effect on network connected devices would they eg ubuntu accessing a windows share?

No, unless you were relying on your router to act as your master browser. I'm not sure how that functionality will behave if everything is SMB2-only on the LAN.
 
Hi,

after a long time I upgraded my ac68u from 380.69 to this (beta)release. No issues so far :)

Unfortunately still missing IPSEC :-( Any chance to see it on this old but solid machine ?

cheers
 
Have you noticed any issues after enabling this on the RT-AC86U?

noob- Is there a place to download the complied version? I only use smartphones and don't have a computer. If not I will wait for Merlin to approve and update his builds. Thanks
just wait next beta.
 
  • Like
Reactions: f2s
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

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