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

    Beta ASUSWRT 386 RC3-3 public beta for IPv6 DDNS and IPv6 VPN server

    It's been so long since we've had an update. Anyone downgraded to the official release? 3.0.0.4.386.48706 (2022/05/03) I don't want to be behind on bug fixes, however I don't want to lose the client vpn traffic mapping.
  2. A

    Beta ASUSWRT 386 RC3-3 public beta for IPv6 DDNS and IPv6 VPN server

    There is a default setting in the VPN config itself if you want all traffic flowing through the vpn.
  3. A

    Beta ASUSWRT 386 RC3-3 public beta for IPv6 DDNS and IPv6 VPN server

    @ASUSWRT_2020 you still around? any update?
  4. A

    ASUS ZenWiFi XT8 Firmware version 9.0.0.4.386.46980 (2022/02/22)

    Bummer, this firmware version is still less than the rc3 version.
  5. A

    Beta ASUSWRT 386 RC3-3 public beta for IPv6 DDNS and IPv6 VPN server

    At least for the xt8, only bugs/security issues were fixed
  6. A

    Beta ASUSWRT 386 RC3-2 public beta

    I have to double check, but with vpn if connection goes out, there isn't any connections that can go out
  7. A

    Release Asus ZenWiFi XT8 - New Firmware: 3.0.0.4.386_45898

    Check out: https://www.asus.com/support/FAQ/1042475 and see if it helps
  8. A

    Beta ASUSWRT 386 RC3-2 public beta

    I setup the VPN again and it is working as expected on this beta. But it seems something gets messed up after the beta upgrade to the latest
  9. A

    Beta ASUSWRT 386 RC3-2 public beta

    I have no problems with pihole. Please check your configuration
  10. A

    Beta ASUSWRT 386 RC3-2 public beta

    Looks like vpn isn't working right (after a reboot). Even though I configured it for a few devices, all my traffic is going through the vpn. I might try reconfiguring the vpn to see if that helps. Speedtest still broken
  11. A

    Beta ASUSWRT 386 RC3-2 public beta

    Speedtest isn't working too well. My configured VPN connections don't seem to be working right either, but I will need to dig in a bit. However, it looks like speeds have bumped up a bit for me so thats a plus
  12. A

    Beta ASUSWRT 386 RC3-2 public beta

    so it turns out my 2nd node didn't update correctly and required a manual update. I also found the speed test in the android app wasn't working correctly (inflated my speeds by 4x)
  13. A

    Beta ASUSWRT 386 RC3-2 public beta

    Just updated both my xt8 nodes through the Android app. So far so good
  14. A

    Beta ASUSWRT 386 RC3-1 public beta

    So the xt8 just released new official firmware yesterday. I'm just wondering if that new official firmware contains any of these beta features. official: 386_45898 and beta is: 386_55919
  15. A

    Beta ASUSWRT 386 RC3-1 public beta

    @ASUSWRT_2020 looks like the 'DNS Server' setting isn't working Just more context, I'm using pi hole for this. It's working for as domains but not my custom dns. Sorry about that. I'll look into why my custom configured domains are not working.
  16. A

    New XT8 setup

    welcome to the club :)
  17. A

    Beta ASUSWRT 386 RC3-1 public beta

    You try these recommendations? https://www.asus.com/support/FAQ/1042475 And thanks to OE: https://www.snbforums.com/threads/official-release-aimesh-firmware-v3-0-0-4-384-20308-for-all-supported-products.44375/page-14#post-381537
  18. A

    Beta ASUSWRT 386 RC3-1 public beta

    So far using the new vpn client with certain devices configured is working great
  19. A

    Beta ASUSWRT 386 RC3-1 public beta

    I have updated my xt8 on both nodes and it's been running fine. I haven't checked the logs if I see anything funny, but so far so good
  20. A

    Release Asus XT8 - 3.0.0.4.386.43181 - 2021/06/17

    I also had no big problems on 181 with wireless backhaul. I didn't notice some wireless instability after over 2 weeks of up time. A restart fixed it
Top