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

    In some dire need of assistance (AX86U)

    Unfortunately, it seems on Beta2 of merlin firmware, they're really unhappy - Google's disconnect every day, if not a couple times - not sure if that helps anyone @RMerlin No response from ASUS other than they're looking into it.
  2. S

    Beta Asuswrt-Merlin 386.1 Beta is now available

    AX86U on Beta2 (Dirty from Beta1), still have the "authorizing" bug on Lets Encrypt - same logs as those before me.
  3. S

    In some dire need of assistance (AX86U)

    Hey Colin, Thanks for reviewing. I did try the mode to N only - it did not change the outcome. I have submitted the information to Asus - and have been trying to work with them for the past month or two - but no outcome just yet.
  4. S

    In some dire need of assistance (AX86U)

    couldn't paste the crash (10k limit)
  5. S

    In some dire need of assistance (AX86U)

    They Disconnect from the router it seems - and think they cannot get an address.
  6. S

    In some dire need of assistance (AX86U)

    Unfortunate news. All the googles broke at some point today. Logs indicate around 7-8pm. I have saved the log and will upload to pastebin... @ColinTaylor: Would you be willing to review... Perhaps even @RMerlin ? Thanks.
  7. S

    Google Home (Nest Mini) fails to stay connected after being inactive (AX86U)

    Hi @tommybare : If you are having problems with your minis now Go to Advanced -> LAN -> DHCP Server (Tab) Create IP reservations with MAC addresses for each of your Google devices and set the optional host name for each. For example, I would set mine to GHM-MasterBath (for a mini in the...
  8. S

    In some dire need of assistance (AX86U)

    Ah yes, My initial thinking was that there were factory resets on both official 384 and official beta 386 with the same results - but yes, in this case, Merlins 386 beta and factory reset was used. Alpha 4 was also a full reset with no change - but the hostnames were not present there.
  9. S

    Google Home (Nest Mini) fails to stay connected after being inactive (AX86U)

    For those not following my other thread - we seem to be having positive results so far by setting a hostname on the DHCP reservation of the device - (change from Google-Home-Mini). Could someone else please test that in their environment and report back?
  10. S

    In some dire need of assistance (AX86U)

    104 Hour Update - Longest run so far - no disconnects or issues with the environment. Puzzling results - as the only change from the last change was hostnames on DHCP. Interesting. Still getting random watchdog crashes - they don't seem to affect anything noticeable. For people following -...
  11. S

    Google Home (Nest Mini) fails to stay connected after being inactive (AX86U)

    I started my process on 384 firmware (stock), and had issues on the 86u. Only thing I can say is the 370 firmware on the 66u was fine (significantly older)
  12. S

    Google Home (Nest Mini) fails to stay connected after being inactive (AX86U)

    They @tommybare and @bestgio : If you haven't already, please open a ticket with ASUS with your information. They will have you send feedback if you are using the official firmware. From their perspective it may help with more reports. Reference the threads here and I would think they can put...
  13. S

    In some dire need of assistance (AX86U)

    So, a bit over 36 hours into the test, - changes being the beta1 firmware, and setting host names initially - no drops (yet). The logs are largely unexciting however I did notice the crashes you were speaking about of the radio. Those seem to be persisting and random. Code below. Longest run...
  14. S

    Google Home (Nest Mini) fails to stay connected after being inactive (AX86U)

    Well hello there. Seems you have the same issue I have been battling on my AX86U as well. While I don't have a resolution yet, we've been troubleshooting and attempting to find more information in my thread here: https://www.snbforums.com/threads/in-some-dire-need-of-assistance-ax86u.67944...
  15. S

    Beta Asuswrt-Merlin 386.1 Beta is now available

    AX86U, can confirm what some others are saying on the Lets Encrypt "Authorizing" issue. Wiped configuration completely, formatted JFFS, sitting at authorizing. Not much in logs. Happy to look deeper if needed. Thank you
  16. S

    In some dire need of assistance (AX86U)

    Hi Colin. Upgraded to Beta1 - wiped config per merlin and did everything over again. Set the HostName off the bat for logs. Everything is working at the moment. Will report back as things progress. Thank you for your interest and persistence in helping.
  17. S

    In some dire need of assistance (AX86U)

    Hey there, Got it - all of them now have the name reflected from the left. I can do a full reset this evening and then get a new log when they drop off again?
  18. S

    In some dire need of assistance (AX86U)

    That 2nd screenshot is the LAN -> DHCP Server area. Here's a bigger one.
  19. S

    In some dire need of assistance (AX86U)

    Hey there, Also noticed that, and often confused by the names, those names aren't coming from me. Here is a screenshot of what I have attempted to set in the UI. You'll notice in the 2nd screenshot of the client list only 2 are showing up - those are the two i power cycled this morning. Not...
  20. S

    In some dire need of assistance (AX86U)

    Hey Colin, here is the paste https://pastebin.com/4rXNxXmR I will DM you the pw.
Top