SomeWhereOverTheRainBow
Part of the Furniture
the added benefit would come in if AdGuardHome fully supported mapping ipv6 to ipv4What I am doing so far is not to install ca.crt to any of the devices; it was something that I sort of "dreaded" in having to repeat for all the devices. Some devices, especially smart TV does not support installation of the certificate anyway.
In terms of browsing experience, have not noticed any significant differences. As for performance, this would be hard to quantify as it requires extensive testing and monitoring to a certain extent.
As an alternative, I'm just checking on the "Average processing time" stats in AGH and also "tav" and "tmx" in pixelserv servstats. This would likely be not 100% accurate
::ffff:192.168.1.4
It will let you input it in the gui for the ipv6 address, but it quickly reverts it to regular 192.168.1.4 instead of holding that value in the GUI. As far as I can tell, the query logs and the AGH server itself will map the AAAA responses to the address AA address. it appears pixelserv-tls maybe able to read the queries from mapped addressing. most of the responses were .02 to .03 ms