That reminds me I have to go through my allow list and test if some entries I added to fix broken apps/services can be replaced by a rewrite to 0.0.0.0 or some other bogus IP.
The TV sends a DNS request to AdGuard once per minute, no matter what. Then if the response is a pixelserv IP, it goes crazy 20 times per second with HTTP requests to pixelserv. After one minute it talks to AdGuard again ("Are you SURE this is the IP I'm looking for?"). I don't think responses...
I may have found the culprit. An old Samsung TV goes bananas when "prov.samsungcloudsolution.com" is resolved to a pixelserv IP. It starts hammering pixelserv with ~20 HTTP requests per second and each pixelserv response makes the TV even angrier. That was enough to spawn 32 threads and send the...
Now that you mention it, I remember seeing around 8 or 10 threads on htop when the load was about 30%. After a restart it goes down to two. AdGuard Home's cache should dampen this spammy behaviour, but I will keep an eye on the threads. Thank you!
It's an AC86U. I've been running Diversion+pixelserv on it without a hitch for over two years, switched to AdGuard Home (without pixelserv) a month ago, also with no problems. Started using the 'standalone' pixelserv three days ago and noticed the high CPU usage. After a reboot or a pixelserv...
The CPU load of the pixelserv process on my AC86U is hovering around 20-30% (with peaks in the 40s) while AdGuard Home barely moves over 0%. A couple reboots apparently did nothing to calm it down. I don't recall this happening with the pixelserv paired with Diversion. Is this expected? If not...