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

    2.5gb aimesh Ethernet backhaul

    I concur with @L&LD. It really is about sharing the access of central resources on the internal network equally well via any of the access points to which the consuming devices are connected, like to Plex for streaming for multiple people at once. But as you say, if the thing you're interested...
  2. dbell

    New AX86U node and IOT devices

    As far as I know only the ring doorbell pro is AC compliant. The others are G, N I think. Are you saying they don't associate with the router or that they cannot connect to the internet even if they look connected to the router ?
  3. dbell

    New AX86U node and IOT devices

    I don't know that a firmware flash replaces or updates existing rules if you don't accompany it with a factory reset. If they got corrupted while using a previous version of the firmware you might try factory reset and allow the default set of rules to be put back in place. My devices were...
  4. dbell

    AX86U nest thermostats not connecting - common problem

    My nest is working fine on AX86U with 386.2 beta 3 - it is on guest network 1 but there was an issue around 386.2 alpha 2 (I think) with corrupt firewall rules. None of my nest or ring devices could connect to internet if I prevented local network access, but they had dhcp leases and showed in...
  5. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    My second AX86U arrived so now I replaced the AC5300 and 386.2 beta 1 works fine and does not exhibit the same issue as on the AC5300.
  6. dbell

    New AX86U node and IOT devices

    @OzarkEdge Looks like the fix for corrupted firewall rules in 386.2_beta2-g1e6831e65a has solved this problem. My IoT devices remained connected overnight with allow intranet access disabled.
  7. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    @brummygit @john9527 Looks like the fix for corrupted firewall rules in 386.2_beta2-g1e6831e65a has solved this problem. My IoT devices remained connected overnight with allow intranet access disabled
  8. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    AC5300 router (2.4g / 5g-2 enabled) <-- ethernet backhaul --> AX86U node (2.4g / 5g enabled) - the AX86U is the node because it serves the larger area and more devices, but the Internet ingress is near the AC5300. It's definitely a disadvantage to have the admin UI be tied to the AC5300 rather...
  9. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Do I need to also do nvram set wl0.2_ap_isolate=0 on the node since wl0.2 is the equivalent interface there ? Mixing tri- and dual-band routers is not the best I think. Maybe I should just buy another AX86U.
  10. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Ok so now I see lanaccess off and ap isolate 1, and vice versa for the wl0.1 interface. They were lanaccess=off and ap_isolate=1 back in 386.1_2 on 16 feb too. Thanks for the education.
  11. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Depends on your definition of "fixed" I suppose. Now that you mention it I do recall reading some debate about disable intranet access causing ap isolation as well. But I would have expected to have tripped over it before now unless the thing that was fixed was unique to AC5300 that others...
  12. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Hey John thanks for joining in. I had this setup in place before 386 came along and did not experience the issue (and did not have to make any changes) while using the various 386.1 builds - only became an issue with 386.2 alpha 2. If I go back to 386.2_alpha1-ga84fed8777 the issue goes away -...
  13. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Hey thanks for the info. Seems like my devices are getting dhcp responses as they show associated with the .101. address but just can't reach the internet to register their state with the nest or ring services.
  14. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    One of the reasons for moving IoT devices to guest was isolation from intranet and have always run with that disabled until 386.2 alpha 2 came along.
  15. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    OK everyone went out soooooo........ Factory reset with 386.2 beta 1 and devices on 2.4 guest slot 1 to share with mesh node; all ring / nest devices disconnected. Moved guest SSID to slot 2 and all remained disconnected until I allowed access to Intranet and then they reconnected. Moved the...
  16. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Interesting and thanks for the post. Mine were all fine with dhcp until this recent alpha2 build. Once everyone has gone to bed tonight I will have to do a factory reset and try again since that is one thing that I haven't done since before alpha2.
  17. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    No I have not done factory reset since 386.1_2
  18. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Soon as I went back to 386.2 alpha 1 they can rejoin. Suppose the good news is that it is not the new ax86u node or WiFi 6 since the firmware on my AC5300 router seems to be the important factor.
  19. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Are your devices on the guest or regular 2.4 ssid ? Put 386.2 beta 1 on the router and the nest / ring stuff fell off again. Wondering if it is an issue with dhcp responses on guest network.
  20. dbell

    Issue with 2.4Ghz and nest / ring devices in 386.2 alpha 2

    Downloading - will try later once work / school calls are over
Top