Search results

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

  1. Z

    potentially unexpected fatal signal 11

    The "dcd Tainted" can occur with any firmware version when using the Trend Micro feature. I concluded that it is not worth worrying about. And newer firmware will have more Trend Micro related problems. Of course, this is an official firmware issue, not Asuswrt-Merlin.
  2. Z

    With WPA3 some clients drop after exactly 12h (GT-AX6000 - do not think it is router specific)

    The same problem occurs with RT-AX86U. RT-AX86S used in media bridge reconnects 12 hours after connection. This does not occur on other devices. I have tried multiple FWs, such as setting the DHCP lease time to 2 days, fixing the IP of the RT-AX86S, but the problem was not fixed. I addressed...
  3. Z

    Release ASUS RT-AX86 Series(RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388.23285 (15-05-2023)

    I quit chasing new firmware because the Trend Micro related problems have not been fixed at all. Unfortunately, the Asuswrt-Merlin 3004.388.4 beta, based on the newer GPL 388_23588 than the official one, also reported a stack. In my environment, 386.7_2 is better than 386.5_2. With Adaptive QoS...
  4. Z

    UPnP - enable per device?

    @ColinTaylor Thanks for the explanation. When I compared the example script and /tmp/etc/upnp/config, I was a bit curious about the different lines inserting "allow", but now the mystery is solved.
  5. Z

    UPnP - enable per device?

    By tweaking the script example and adding ext_ip, I was able to allow UPnP only for certain clients in a double NAT environment. Thanks @ColinTaylor and this thread. #!/bin/sh CONFIG=$1 source /usr/sbin/helper.sh pc_delete "allow " $CONFIG # Remove existing rule first pc_delete "ext_ip="...
  6. Z

    Auto Firmware Upgrade made official - a new Note in Asus FAQ

    I remember the following problems with automatic updates in the past (the second site is not in English). In the ASUS router community in my country, the common theory is that auto-update is dangerous and should be disabled...
  7. Z

    Solved UPnP doesn't work on CGNAT/Double NAT

    The value of the ext_ip setting is used as the IP to be returned to the UPnP client in GetExternalIPAddress(). The devices and software I tested worked fine with the fake IP setting, though, I reconfigured the ext_ip with a real public IP just to be sure. My home IP rarely changes, so I just...
  8. Z

    Solved UPnP doesn't work on CGNAT/Double NAT

    @Yota I had a similar problem with RT-AX86U. Using the "Edit3" script solved the problem. Thanks for the information.
  9. Z

    Release ASUS RT-AX86 Series(RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388.23285 (15-05-2023)

    A family member informed me that he had not been able to connect to the internet for several minutes. I checked the logs and found that it had rebooted on its own again. Rolled back to past firmware that was stable.
  10. Z

    Release ASUS RT-AX86 Series(RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388.23285 (15-05-2023)

    The router was then automatically rebooted. No reboot scheduler was set. The firmware update may have caused it to reboot as a stopgap measure when the Trend Micro feature gets stuck.
  11. Z

    Release ASUS RT-AX86 Series(RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388.23285 (15-05-2023)

    Four days after the firmware update, the Web History got stuck. I won't check anymore, but I'm sure the automatic signature updates and AiProtection counts have stopped as well. The last firmware where these worked properly was 3.0.0.4.386.49599.
  12. Z

    Release ASUS RT-AX86 Series(RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388.23285 (15-05-2023)

    The update completed successfully. Unfortunately, the AiProtection alert email still does not seem to work. I will run it for a while to see if the problem of Trend Micro related functions stopping working in a few days has been fixed.
  13. Z

    Stock 386.46061 vs 386.49599?

    46061 has a bug that when IPv6 passthrough and Trend Micro features are enabled at the same time, the following logs are output in large numbers. kernel: protocol 0000 is buggy, dev eth0 This problem has been resolved in 49599. For both Official and Merlin, the Web History, Traffic Analyzer...
  14. Z

    Release Asuswrt-Merlin 388.2 is now available for select models

    I am using RT-AX86U. I expect the Trend Micro related features to work properly in 388.3. For both Official and Merlin, the Web History, Traffic Analyzer, AiProtection counts, and signature auto-updates stopped working on the 388 firmware within a few days of startup. In addition to that, with...
  15. Z

    RT-AX86U on Merlin 388.1 Web UI hangs when accessing the Web History tab

    When I reverted from Merlin 388.2 alpha2 to the official 3.0.0.4.386.49599, it simply uploaded and worked. However, it seems that in some cases a reset and reconfiguration may be necessary.
  16. Z

    RT-AX86U on Merlin 388.1 Web UI hangs when accessing the Web History tab

    This is a bug in the official 388 firmware. The problem with WebUI becoming unresponsive was fixed in 388.2 by merging 22525 GPL, but there is still a problem with web history recording stopping after a few days. Using 386 firmware is the solution.
  17. Z

    [ 388.2 alpha Build(s) ] Testing available build(s)

    Four days after updating from 388.1 to 388.2 alpha2, web history updates and AiProtection counts stopped. This is not a problem with Asuswrt-Merlin, as it also occurred with the official 388 firmware. Unfortunately, it does not seem to be fixed in 22525 either. * The phenomenon of AiProtection...
  18. Z

    [ 388.2 alpha Build(s) ] Testing available build(s)

    The delay on the AiMesh page is fixed in this commit. It is html, so you may be able to connect via SSH and edit it with vi. /www/aimesh/aimesh_topology.html
  19. Z

    [ 388.2 alpha Build(s) ] Testing available build(s)

    After updating RT-AX86U from 388.1 to 388.2 alpha2, I noticed that the AiProtection alert emails (Google) were no longer being sent. After resetting and reconfiguring, I received the "Notify Mail Verify" email, but when I accessed the test site, I did not receive the alert email. In the...
  20. Z

    Release ASUS RT-AX86 Series(RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388.21709

    QoS and AiProtection bugs fixed. Response time has improved. Good firmware. :)
Top