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

Recent content by Michael Cherry

  1. M

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    John, thank you for your continued support of our aged equipment. Stay safe during these trying times!
  2. M

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    Thanks for replying John. Channel 11 with with "WMM APSD" enabled was my starting point where the (2) devices wouldn't reconnect. Just changing to Channel 1 let them reconnect. I tried channel 1 with that setting disabled, that worked too. Channel 11 disabled worked. I then re-enabled the...
  3. M

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    I try to find out if I can change the port. Thanks for the input!
  4. M

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    Sorry about the screenshot size. Here is a snipped version. I did some more digging and reading and found an old thread talking about using channel 1 on 2.4 Ghz is sometimes helpful. I changed my Channel from 11 to 1 and the scale and my watch are both working again. Go figure. Anyway, can...
  5. M

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    Just before it shows up in the log, the Gear S3 was stuck at "connecting...", I rebooted it, then forgot the network and signed in. I don't see anything before it joined then. On an unrelated note, the device @ .103 is my Obi 202 voip adapter, it seems very busy. The phone is sitting idle, is...
  6. M

    [Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

    Hello John, I'm running 36EA on my AC68R. I'm having a wierd problem with (2) 2.4 ghz devices - a Samsung Gear S3 Frontier and Under Armour scale made by HTC. Both devices refuse to auto-reconnect to the network. The scale worked previous versions of your firmware, this problem may have...
Back
Top