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

    [Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products

    I believe it's initiated by mesh system. Here's a sample log entry from my aimesh setup. Jan 30 06:54:35 roamast: discover candidate node [D8:50:E6:CF:84:E8](rssi: -55dbm) for weak signal strength client [2C:33:61:AE:7C:5A](rssi: -73dbm) Jan 30 06:54:35 roamast: eth2: disconnect weak signal...
  2. J

    [Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products

    LOL....that not really a static IP assignment. That’s a DHCP reservation but I gotcha! [emoji1360] I had hoped to avoid using a reservation, I won’t bore you with the details. Being able to statically assign an IP is a nice to have but certainly not a deal breaker. Thanks for the feedback...
  3. J

    [Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products

    Actually now that I think about it....i did have to reset the node once. So actual steps on the node where: -Reset to factory using the reset button, typical hold until power light is blinking. -Rejoined node to mesh. Went offline at this point. -Manual reboot to bring it online. -Upgraded to...
  4. J

    [Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products

    I had the same experience after I rejoined the node. Power cycled it manually once and I haven’t had issues since. Aside the firmware update progress bar and having to rejoin and restart the node for me this is looking positive. Luckily for me I haven’t had too many problems since the release...
  5. J

    [Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products

    I had the same issue. Reboot of the router cleared it. In my situation any firmware update checks post reboot did not trigger another occurrence. In my case this was originally triggered after updating my node to new update from 10007. Also it looks like the upgrade status bar is triggered but...
  6. J

    AiMesh for Tri-band routers: RT-AC5300, GT-AC5300

    I wouldn’t reset twice, personally I would only perform it once after updating the firmware. Sent from my iPhone using Tapatalk
  7. J

    AiMesh for Tri-band routers: RT-AC5300, GT-AC5300

    Because of how significant this update, yes I would recommend a hard reset after updating the firmware. Hard reset should be performed using the reset button on the device itself. Press and hold until you see the power LED flashing. Hope that helps. Sent from my iPhone using Tapatalk
  8. J

    [Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products

    I would recommend submitting feature request using the feedback feature within the web GUI. I recently submitted one specifically for the node. -manual reboot -scheduled reboot -cpu/memory stats -enable SSH (turns out this already is inherited but it took a while to take affect) -USB device...
  9. J

    [Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products

    New to forum but figured i would provide feedback on my experience with aimesh RT-AC5300 configured as router w/12/16 beta firmware 9.0.0.4.382_19612 RT-AC68R configured as a aimesh node with aimesh release 3.0.0.4.384_10007. Note this is not using wired backhaul....all wireless. During setup...
Top