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

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    Ok, everything is still working, and I was able to remove and re-add a protect to my account. I'd still like to understand if this was a recent breakage from .17 to .18, and what the intent was of the change, and ideally why it breaks nest. For example, when I did the wireshark + hotspot test...
  2. wraithdu

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    I installed @john9527 's patched build and it seems like the protects can connect to their network with DoT enabled. I'll give it 24 hours to make sure they stay connected and report back. If I have a bit more time tomorrow I may try to remove / re-add a device as well.
  3. wraithdu

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    Got some 4th stuff going on today, but I'll reach out over PM to talk about testing your build, thanks! The problem description looks promising. Was this a recent breakage? My network was fine on .17.
  4. wraithdu

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    I tried that actually. Removed from my account, full factory reset. It fails when trying to add back. Best guess is the device can't communicate at the last stage when associating with the account (P009 0.80 error). I guessed at the root problem really. Tried it with my laptop as a hotspot and...
  5. wraithdu

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    @dave14305 yes. It has worked with DoT and Cloudflare as well as Quad9. I've kept up with every stable fw release, so I upgraded from .17. I had considered downgrading to test, but .18 has those breakages, so I can't without a full reset.
  6. wraithdu

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    I do not use DNSFilter.
  7. wraithdu

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    @fields987 , I did not have rebind or DNSSEC options enabled, and I set the Quad9/Cloudflare ipv6 servers in the list as well.
  8. wraithdu

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    I'm using Cloudflare without DoT, both ipv4 and ipv6. Should mention I'm on Xfinity cable.
  9. wraithdu

    Nest Protect cannot connect with DoT enabled - RT-AX88U 384.18

    After updating to 384.18, all 8 of my Nest Protect devices went offline, and I was unable to add any new Protect devices onto my account. I have one 2nd Gen and the rest 1st Gen. I went through all troubleshooting, and finally after totally disabling DoT, they were able to connect and I could...
  10. wraithdu

    Trouble with IPv6 custom DNS, or with DHCPv6 Server disabled

    The solution is to use the postconf custom config file to modify the generated dnsmasq.conf so that dnsmasq hands out your desired DNS servers. See here for usage: https://github.com/RMerl/asuswrt-merlin/wiki/Custom-config-files First you need to enable the custom config files: Administration...
  11. wraithdu

    Trouble with IPv6 custom DNS, or with DHCPv6 Server disabled

    Correct, the router uses dnsmasq as a proxy to your defined DNS servers, and clients get the router address for DNS. I do not think you can turn this off. You would have to use the custom config files and scripts to modify the dnsmasq configuration dynamically. I don't think you can turn dnsmasq...
  12. wraithdu

    Trouble with IPv6 custom DNS, or with DHCPv6 Server disabled

    Your active directory machines are actually the outliers. They are receiving their DHCPv6 info from somewhere else, not the router. The router will actually hand out its real IPv6 address to LAN clients. Internally, it forwards to your specified DNS server, using its link local address you...
  13. wraithdu

    Trouble with IPv6 custom DNS, or with DHCPv6 Server disabled

    So I did figure this out, though it takes a few non-intuitive settings to get it to work. One thing first, yes the IPv6 settings are lost after changing something like the IPv6 DNS until a reboot of the router. I don't know why it happens but it is consistent. Not a problem really, after setting...
  14. wraithdu

    Trouble with IPv6 custom DNS, or with DHCPv6 Server disabled

    I have a pretty basic home setup, with a Pi2 running my DHCP server and Unbound for DNS. I have Comcast and I'd like to setup the router to do one of two options : Option 1) Provide DHCPv6 and specify my internal DNS server Option 2) Provide only RA for default gateway and allow my internal...
View older results
Top