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. B

    Release Asuswrt-Merlin 386.2 is now available

    I've had this on stock firmware and sent feedback about it. When the update_sta_binding happens the node wifi restarts. I think this maybe up to Asus to fix and may be closed loop so @Merlin is unable to make adjustments to Mesh 2.
  2. B

    Release Asuswrt-Merlin 386.2 is now available

    Already done that thanks for info.
  3. B

    Release Asuswrt-Merlin 386.2 is now available

    Yes I am aware of the differences between the 384 branch and 386 branches but it is a quick and dirty test of wireless stability.
  4. B

    Release Asuswrt-Merlin 386.2 is now available

    Bind option on the node has disappeared, but I suppose that is to be expected. Also if you change Firmware check to No there is no Apply button.
  5. B

    Release Asuswrt-Merlin 386.2 is now available

    Trying 384.19 on the node. Mesh seems to work ok will monitor.
  6. B

    Release Asuswrt-Merlin 386.2 is now available

    I believe 384 branch was ok but there is a lot of security fixes under the bridge since then. Unless one tried 384 on the node and 386 on the router. Not sure Mesh will work.
  7. B

    Release Asuswrt-Merlin 386.2 is now available

    Anyone got an email address for Asus to feedback the above post as stock firmware does the same after about 6 days uptime. 6 days is not bad but it would be better if AP was stable other than using the reboot scheduler.
  8. B

    Release Asuswrt-Merlin 386.2 is now available

    Sometimes when making configuration changes to wifi sections the AP will restart. Sometimes it will restart all of its own right in the middle of streaming stuff without a reboot.
  9. B

    Release Asuswrt-Merlin 386.2 is now available

    With all due respect that shows the OS Uptime not actual AP uptime which can vary.
  10. B

    Release Asuswrt-Merlin 386.2 is now available

    I used Winfi Lite on my PC which tells you AP uptime, also Wifi Analyzer from windows store is a free app which under the network tab tells you AP uptime.
  11. B

    ASUS RT-AC68U AiMesh drops (Again)

    3d21H and the 5ghz has restarted. Node is not stable.
  12. B

    Release Asuswrt-Merlin 386.2 is now available

    3d21H and the 5ghz has restarted. Node is not stable.
  13. B

    Release Asuswrt-Merlin 386.2 is now available

    Anyone having trouble with mesh nodes? My router wifi (2 and 5ghz) has an uptime of 3 days and the 5 ghz on the node also 3 days uptime but the 2.4 on the node has dropped.
  14. B

    ASUS RT-AC68U AiMesh drops (Again)

    My main router has been up 3 days and 5ghz on the node as well but the 2.4ghz dropped today on the node.
  15. B

    386.2 - wi-fi client gives error in system log

    Debug info left in by Asus, just ignore it.
  16. B

    AiMesh nodes disconnect since 386.1

    1 Day 20 is my RT-AC68U and its node which is wireless. 32 days is my two DSL-N55U in media bridge.
  17. B

    ASUS RT-AC68U AiMesh drops (Again)

    I was wondering this as well. My theory about the Mesh optimising is just that a theory. I hope @RMerlin sees this thread and may comment.
  18. B

    ASUS RT-AC68U AiMesh drops (Again)

    I've had without a drop on Merlin 386.2 but I think it is the Asus Mesh auto-optimising the connection because if you press Optimise in the Mesh tab the results are similar disconnect for 2-3 minutes. Why it is auto-optimising when the signal is "Great" is up to Asus to fix.
  19. B

    AiMesh nodes disconnect since 386.1

    No disconnects on the main router both 2.4 and 5, node has same amount of uptime on 5 band but 2.4 has dropped on Merlin 386.2
  20. B

    AiMesh nodes disconnect since 386.1

    I was having similar problems with stock firmware on 2x RT-AC68U so I have switched to Merlin 386.2 on both router and node. Still monitoring. Personally I think it is the Mesh coding from Asus.
Top