What's new

Release Asuswrt-Merlin 3004.388.4 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!

Similar to mine, PMF does not appear on this 3004.388.4 firmware with the WPA2/WPA3 personal setting. At first, I did a factory reset but PMF was not still there. Then I decide to leave it for a few hours because everything ran smoothly. After observing normal networking devices, I just put that aside 😁
Thank you! Putting it aside :)
 
Hi, 2 days with out problem, and now show this, like i sayed i have ax11000 with merlin and ax82u with stock firmware with aimesh. Wont lose internet, but start to become soo slow to navegate in internet even to open the webadmin router. I must just restart the router manual for start again working fine.

Aug 26 19:32:43 kernel: SHN Release Version: 2.0.2 36f59aa
Aug 26 19:32:43 kernel: UDB Core Version: 0.2.20
Aug 26 19:32:43 kernel: sizeof forward pkt param = 280
Aug 26 19:32:43 BWDPI: fun bitmap = 3
Aug 26 19:33:09 BWDPI: force to flush flowcache entries
Aug 26 19:33:09 BWDPI: rollback fc
Aug 26 19:33:12 kernel: SHN Release Version: 2.0.2 36f59aa
Aug 26 19:33:12 kernel: UDB Core Version: 0.2.20
Aug 26 19:33:12 kernel: sizeof forward pkt param = 280
Aug 26 19:33:12 BWDPI: fun bitmap = 3

Aug 26 19:33:34 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Aug 26 19:33:35 wlceventd: wlceventd_proc_event(685): eth7: Auth A8:51:AB:0F:A6:78, status: Successful (0), rssi:0
Aug 26 19:33:35 wlceventd: wlceventd_proc_event(722): eth7: Assoc A8:51:AB:0F:A6:78, status: Successful (0), rssi:-66
Aug 26 19:33:36 wlceventd: wlceventd_proc_event(662): eth7: Disassoc A8:51:AB:0F:A6:78, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:33:36 wlceventd: wlceventd_proc_event(662): eth7: Disassoc A8:51:AB:0F:A6:78, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:33:40 wlceventd: wlceventd_proc_event(662): eth7: Disassoc 22:CE:A4:A1:A8:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:33:40 wlceventd: wlceventd_proc_event(662): eth7: Disassoc 22:CE:A4:A1:A8:72, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:33:41 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Aug 26 19:33:43 wlceventd: wlceventd_proc_event(685): eth7: Auth 22:CE:A4:A1:A8:72, status: Successful (0), rssi:0
Aug 26 19:33:43 wlceventd: wlceventd_proc_event(722): eth7: Assoc 22:CE:A4:A1:A8:72, status: Successful (0), rssi:-67
Aug 26 19:33:45 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 3C:7C:3F:55:B5:39, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 26 19:33:45 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 3C:7C:3F:55:B5:39, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-45
Aug 26 19:33:46 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 3C:7C:3F:55:B5:39, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:33:46 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Aug 26 19:33:49 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind 3C:7C:3F:55:B5:3C, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-52
Aug 26 19:33:49 wlceventd: wlceventd_proc_event(645): eth8: Deauth_ind 3C:7C:3F:55:B5:3C, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-52
Aug 26 19:33:50 wlceventd: wlceventd_proc_event(662): eth8: Disassoc 3C:7C:3F:55:B5:3C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:33:50 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Aug 26 19:33:55 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Aug 26 19:34:07 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:08 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:08 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:08 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:09 wlceventd: wlceventd_proc_event(685): eth6: Auth 3C:7C:3F:55:B5:39, status: Successful (0), rssi:0
Aug 26 19:34:09 wlceventd: wlceventd_proc_event(722): eth6: Assoc 3C:7C:3F:55:B5:39, status: Successful (0), rssi:-46
Aug 26 19:34:10 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 3C:7C:3F:55:B5:39, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:34:10 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 3C:7C:3F:55:B5:39, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:34:13 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:13 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:13 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:13 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:13 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:14 lld2d[1272]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Aug 26 19:34:36 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind 64:BC:58:B9:30:C0, status: 0, reason: Unspecified reason (1), rssi:0
Aug 26 19:37:34 wlceventd: wlceventd_proc_event(662): eth7: Disassoc F8:B1:DD:4A:61:B4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:37:34 wlceventd: wlceventd_proc_event(662): eth7: Disassoc F8:B1:DD:4A:61:B4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:37:36 wlceventd: wlceventd_proc_event(662): eth7: Disassoc 2A:5D:F0:2C:C9:71, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:37:36 wlceventd: wlceventd_proc_event(662): eth7: Disassoc 2A:5D:F0:2C:C9:71, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 26 19:37:36 roamast: [EXAP]Deauth old sta in 1 0: 2A:5D:F0:2C:C9:71
Aug 26 19:37:36 roamast: eth7: disconnect weak signal strength station [2a:5d:f0:2c:c9:71]
Aug 26 19:37:36 roamast: eth7: remove client [2a:5d:f0:2c:c9:71] from monitor list
May 5 07:05:06 kernel: klogd started: BusyBox v1.25.1 (2023-08-21 15:35:27 EDT)
May 5 07:05:06 kernel: Linux version 4.1.51 (merlin@ubuntu-dev) (gcc version 5.5.0 (Buildroot 2017.11.1) ) #4 SMP PREEMPT Mon Aug 21 16:27:45 EDT 2023
May 5 07:05:06 kernel: CPU: AArch64 Processor [420f1000] revision 0
May 5 07:05:06 kernel: Kernel command line: coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe rootwait
 
Hi, 2 days with out problem, and now show this, like i sayed i have ax11000 with merlin and ax82u with stock firmware with aimesh. Wont lose internet, but start to become soo slow to navegate in internet even to open the webadmin router. I must just restart the router manual for start again working fine.

These logs are nothing new been going on for years. Change your log level to Notice/Notice if you don't want to see them anymore.
 
These logs are nothing new been going on for years. Change your log level to Notice/Notice if you don't want to see them anymore.
So why so laggy the internet even start to load the webadmin soo slow.
 
Since 388.3 I've had an issue that after a reboot I sometimes (not always, 50/50 chance) get the message: "Your ISP's DHCP is not functioning properly" - so I don't have any internet connectivity at all after the reboot (WAN light is red).

Now after flashing to 388.4 & getting the necessary reboot, I got the same message.

Odd thing is that it can be fixed by just turning the Internet Connection slider to Off & back to On (in GUI: Network Map -> Internet Status). A reboot isn't even needed to fixed this. Because it can be fixed with just that I don't think it's an ISP issue but maybe something in the firmware that randomly causes a faulty DHCP request?

And yes, when I was on 388.3 I did a full reset & still had the issue when doing a reboot (again, not always, it occurs randomly).

Running smooth on my RT-AX88U-PRO besides this little issue.
Same here, same problem, ISP-DHCP error after reboot on my RT-AX88U with 388.4, never had that issue before on previous releases, turning off and on the internet connection slider is not a real solution, mine has scheduled reboot every week, I hope somebody can come up with a fix, maybe a script? otherwise Asus firmware is getting worse and worse :(
 
Been working great here for over 3 days now. Happy to have stable, up to date firmware. This time around rebooted the RT-AX86U media bridge just after flashing the GT-AX6000, and the Tablo is working perfectly via the media bridge. Now to decide if I want to let go of Youtube TV in favor of Sling Blue with the Tablo working so well...
 
Same here, same problem, ISP-DHCP error after reboot on my RT-AX88U with 388.4, never had that issue before on previous releases, turning off and on the internet connection slider is not a real solution, mine has scheduled reboot every week, I hope somebody can come up with a fix, maybe a script? otherwise Asus firmware is getting worse and worse :(
Did any of you try to reset ISP modem to default first...?
Or even reboot it?
 
Did any of you try to reset ISP modem to default first...?
Or even reboot it?
Most ISP modems arent user configurable? Its also not a good idea to reset it to default since itll reset whatever the installer configured. Rebooting the modem does work, but that is not a perfect solution.
 
Did any of you try to reset ISP modem to default first...?
Or even reboot it?
Yes sir! I tried reboot all, first ISP modem then the Asus router (even turned both the power off and on), the issue is still there! ISP modem default reset? this is something that can be risky if you also have phone with VoIP configured by the provider. The issue comes not from the ISP modem, is definitely something changed on the Asus firmware managing the WAN port. The last thing I will try is factory reset the Asus router, but i just did it when I updated to 388.2, is getting quite annoying.
 
Most ISP modems arent user configurable? Its also not a good idea to reset it to default since itll reset whatever the installer configured. Rebooting the modem does work, but that is not a perfect solution.
ISP modems (or HGW) usually get their config from the ISPs Network, and are thus safe to reset.
And you can check tat easily with your provider.

Because like a device can remember WiFi settings (and go bad with new WiFi drivers on the router), so can the modems...
Like "something changed on the Asus firmware managing the WAN port" from your example... 😉

I had that when changed to new router, and had to ask my ISP to reset it to default (have no way of doing it myself), all worked after that.
 
Last edited:
Did any of you try to reset ISP modem to default first...?
Or even reboot it?
To further this, has anyone checked to see what is in the syslog for errors?
 
The last thing I will try is factory reset the Asus router, but i just did it when I updated to 388.2, is getting quite annoying.
That FW has quite a bit of difference in GPL (and settings in them) from the .4 to practically mandate a factory reset if issues (and You have Them!).
 
How is the CPU in % then..?
Same from any device or just one?
hi, i dont know the cpu in % because is too slow for charge the web initial, but next time i be waiting and see. It´s the same from any device.
 
To further this, has anyone checked to see what is in the syslog for errors?
Hopefully the default settings for logging is sufficient. Default message log level: notice, Log only messages more urgent then: debug.

I do have logs during a bad and good reboot. Are there keywords to search for? My setup does have a secondary WAN (Android phone as hotspot) as a fail over and a PiHole. I did notice these in the bad log. The wanduck lines only appear in the bad log:

Code:
May  5 01:05:21 WAN(0)_Connection: WAN(0) link down.
May  5 01:06:30 rc_service: wanduck 1403:notify_rc restart_wan_if 0
May  5 01:06:34 rc_service: wanduck 1403:notify_rc restart_wan_if 1
Aug 24 03:32:53 ddns: WAN(1) IP is empty.(10)
Aug 24 03:32:55 WAN(1)_Connection: WAN was restored.
 
hi, i dont know the cpu in % because is too slow for charge the web initial, but next time i be waiting and see. It´s the same from any device.
Try top command via SSH?
 
That FW has quite a bit of difference in GPL (and settings in them) from the .4 to practically mandate a factory reset if issues (and You have Them!).
I found a workaround, I just put Static IP on the WAN connection of the router Asus, getting the IP settings from the ISP router, is the fastest en easiest way to solve temporary the issue. Factory reset takes time, i have many things to configure OpenVPN, Entware, Transmission, LAN DHCP assign, manual scripts, etc... and after that I'm not sure solves the issue.
 

Similar threads

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