@RMerlin I'm not sure if this is new to 384.6, however I did a full reset last night without restoring configuration due to my SmartThings hub refusing to connect to it's servers. I went step by step loading things manually, confirming config each part of the way.
Code:
1. LAN DHCP Manual Assignments
2. VPN Client (with Policy Routes forcing some clients to WAN) (DNS config set to Strict for AB-Solution & dnscrypt functionality)
3. amtm (install in this order: AB-Solution; pixelserv-tls *installs entware; dnscrypt [Auto select, support DNSSEC]; Skynet)
At this point the SmartThings hub was still connected and functioning through each step; No DNS leaks with dnscrypt running, but one setting that I changed last was enabling support for DNSSEC in LAN under DHCP. This has been enabled without loss of connectivity in 384.5 and earlier, but with this being the last change, I started seeing the following in log frequently:
Code:
Jul 3 08:04:39 admin1: Warning: dnscrypt-proxy is not responding
Jul 3 08:04:39 dnscrypt-proxy[17914]: Stopped.
Jul 3 08:04:39 admin1: Start dnscrypt-proxy
Within an hour of the config (at 1:44 AM), SmartThings lost connection, but all other clients appear to function fine; this morning (at 8:05 AM) I disabled DNSSEC in LAN and no longer see the service stopping for the past ~30 minutes and SmartThings connected right away.
I have AIProtection off for now as I am looking for ~12 hours stability between major function configurations, however wanted to pass along this finding and see if you were aware of a change in DNSSEC behavior.