The above message is from our Synology DS224+ NAS with the most recent OS, it is from the OS’s standard check on whether the OS is current. Packages cannot be updated and NTP servers are unavailable – although both show clean DNS requests.
Adam’s Domain Log shows no DNS blocks or errors for the NAS in day-longs 10K samples. Setting the NAS device to Unfiltered has doesn’t fix the problem. I am running the legacy Essentials with the standard pfSense rules.
When I reverted to my previous pfSense setup before adam:ONE I still had the problem with anmuscle.sh both running and stopped.
I haven’t tried reverting and uninstalling adam:ONE. The NAS worked properly before adam:ONE (and my memory says it did for a while afterwards, but I’m not sure). I will try this permutation if its results would help.
Replacing the pfSense box with a router results in the NAS functioning properly. I used the router to set it up and it continues working properly inside our network with adam:ONE in all permutations – unless it needs to communicate with the Internet; only its DNS seems to be working.
That seems like an awful lot of effort to try to prove that Adam:One is the problem. I would suggest maybe not doing all that and instead trying to find an answer on the forum or with Adam support. I can’t imagine uninstalling an entire Adam package just to get a device to work. At the end of the day you still need a firewall to protect your network and just removing it from the equation is just creating work for you that you have to undo eventually.
Please post what the logs are saying about your NAS, and post the network config of your synology box on the synology dashboard. Also let us know what your pfsense dhcp server is provisioning for a search suffix.
Hi @Fred_H
Can you check what DNS servers are assigned or configured on your NAS? My guess is that the NAT hijacking that is usually configured on the gateway is causing an issue with Synology. As you said the queries look OK, but perhaps it’s still causing an issue.
Thank you @nckrwlmn. Your first paragraph is why I didn’t uninstall.
I just have the basic logs available at present; after looking through them (they aren’t available in one of the available file types to upload), the only repeated error was: “Failed to send email. (Failed to execute request curl_easy_perform error: 6).”
The network config is below.
I couldn’t find any suffix setting for my (kea) DHCP server; I’m using only its default settings. However, under Control Panel | Network setings | General | Advanced Settings the “Apply the domain name provided by the DHCP server” is unchecked. I unchecked it to fix multiple “Erred” DNS queries (see this topic).
OK then my theory doesn’t hold up.
This might be a case where you want to enable Level 6 logging, reproduce the issue, and then run the command adamone-issue and send the resulting file to support@adamnet.works
You can reference this forum post in your email.
With help, created a pfSense rule to bypass the NAS around adam:ONE. After doing so had the same problem, so it’s not adam:ONE. When I find the reason I’ll post it here to close the loop.
It was a stupid mistake: After I had entered the new NAS MAC for static routing I, for some reason, restored an old pfSense config with the old NAS MAC. After that, things spiraled down.
The miracle is that the NAS worked at all with an incorrect MAC in the static routing.
I greatly appreciate everyone’s help and I’m sorry I wasted your time.
Fred
P.S. My pfSense backups now have the proper MAC code.
