Menu
What's new
By:
Filters Better Search

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

    2.4 Client Limit

    We have lots of lights that are on smart sockets, some Nest Camera's. We have some early Chromecast that are 2.4 only as well as some speakers. It does not take long to get that number
  2. S

    2.4 Client Limit

    I understand about the number of IP's that the DHCP can assign, however I saw in another post that Asus limits the number of 2.4 clients. (see link in first post) "Asus confirmed via email that the ac3200 has a chipset limitation of 25 2.4 GHz devices" It seems that there is a point when...
  3. S

    2.4 Client Limit

    I have more then 32 clients especially if our phones jump over to 2.4.(maybe 40 or so 2.4 clients) So if I bind Some of the clients to the node, the 32 or so limit should not be a concern? Is that correct? Thanks
  4. S

    2.4 Client Limit

    I have lots of 2.4 I.O.T. Clients and I wanted to know if there is a limit on the number of clients. I found an old thread about this. http://www.snbforums.com/threads/rt-ac3200-limit-on-the-number-of-2-4gb-clients.47019/post-486215 Most of my I.O.T clients don't stream so it is not a...
  5. S

    Problem with AC5300

    I have 2 RT-AC5300's as well. I was having lots of problems including some of what you mentioned. I fought against doing a complete factory reset, however when I did a factory on both the router and the node and then reinstalled 386.2_4the issues went away. I resisted doing a factory reset...
  6. S

    fluctuating latency behavior

    I had very similar problems with my RT-AC5300. You may not want to hear this, but when I did a complete factory reset and then a new setup ( but kept the same SSID). After I did the factory reset, the latency issue went away. I would suggest using 386.2_4 firmware to troubleshoot this.
  7. S

    Release Asuswrt-Merlin 386.2_6 is now available

    Update - nothing changed.. so I did what is often mentioned here but I have not done in quite a while......Hard Factory Reset. All the issues I was seeing are gone. Lesson learned. I had done many dirty upgrades without a factory reset .. so listen to what we are being told, Factory Reset works
  8. S

    Release Asuswrt-Merlin 386.2_6 is now available

    Update after about 10 days. Started dropping 2.4 clients. CPU Showed crazy high levels.. 70 -90%. Soft reboot, hard reboot (not a factory reset) all tried with the same result. Decided to downgrade - all 2.4 Clients are back on. Only time will tell if the 2.4 drops were related to 386.2_6 (I...
  9. S

    Airmesh Node Adjusting (lowering) Power via SSH?

    I have a couple of RT-AC5300's both running the latest Merlin release. I have one location with a speaker that has similar signal from the router and the node. I shh'd into the node and I was hoping to be able to adjust the TX power like on the professional page. I do not know if this is...
  10. S

    Release Asuswrt-Merlin 386.2_6 is now available

    Upgraded two RT-AC5300's from _4 dirty flash to _6 dirty - node first then router.. all is good.... had a few 2.4 disconnects with my Nest Camera but I think it has to do with my wifi congested area
  11. S

    Release Asuswrt-Merlin 386.2 is now available

    Dirty Update to both of my RT-AC5300's from Merlin 386.2_2 to Merlin 386.2_4. Updated node first and then router. No concerns . New firmware has been up 2 days 20 hour(s) 51 minute(s) 43 seconds Thank @RMerlin
  12. S

    Release Asuswrt-Merlin 386.2 is now available

    Dirty upgrade on RT-AC5300 main router and node. Upgraded node first and then router - no issues - thanks @RMerlin
  13. S

    Something has happened to my AC5300 router...

    Wifi backhaul
  14. S

    Something has happened to my AC5300 router...

    I have 2 RT-5300's - Router and Node - and they are both running 386.2 with no issues. Dirty upgrade to both of them. Running just under 50 devices and they have been stable since 386.2 was installed.
  15. S

    CakeQOS CakeQoS-Merlin v2.0.0 alpha

  16. S

    Release Asuswrt-Merlin 386.2 is now available

    Dirty upgrade to two RT-AC5300's. Node upgraded first and then router. No Issues! Thanks @RMerlin for this excellent update.
  17. S

    Release Asuswrt-Merlin 386.1 is now available

    RT-AC5300 Router and RT-AC5300 node with 45-50 clients - up with no issues for 4 days. Just added scripts Thanks again @RMerlin
  18. S

    Release Asuswrt-Merlin 386.1 is now available

    Dirty Upgrade RT-AC5300 node and RT-AC5300 router - no issues at all. Updated Node first - Thanks @RMerlin for all your work on this!
  19. S

    Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0 (continued)

    Yes @ASUSWRT_2020 please do not forget about us with RT-AC5300's :>
  20. S

    Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

    I have been using the binding feature for a few weeks now. I did not know that the binding was only preferred node... I have not seen this message..time to play
Top