Regarding the functional error related to allowing client CIDRs.

[louis5974]

I am a loyal user of your product. I am currently experiencing a functional issue with AdGuard Home (version v0.107.71). I have it set up on a VPS server with a public IP address. In the AdGuard Home web interface settings, under the "Allowed Clients" option, the following CIDR addresses are not working:

My ipv6:
240e:3b4:349b:d010:b9f4:a7a9:5a5e:3af2

240e:3b4:349b:d010::/64

240e:3b4:349b:d010::/60

240e:3b4:349b:0::/56

240e:3b4:3490:0::/52

240e:3b4:3400:0::/48

240e:3b4:0:0::/32

240e:3b0:0:0::/28

the subnet range setting only works if it ends with /64. If I set it to /56, /52, /48, or even a larger range like /28, the setting won't take effect after saving, even if it includes my IPv6 /64 address.

You can use Adguard Home to enter the corresponding suffix for your IP address, and although it covers IPv6, it only allows /64 subnets.

It's very likely that AGH is unable to recognize excessively large IPv6 subnets.

However, when I enter 240e:3ba:3491:e540::/64 and 240e:3b0:3439:6101::/64, everything works correctly, and domain names are resolved. This is a bug. The problem may be due to incorrect IP address resolution when using /48, /52, and /56 suffixes.

if I set too large an address range (such as /52, /48, or /28), AGH does not recognize it as a permitted client.

If I enter a larger IPv6 subnet mask range, the nslookup command fails to respond to domain name resolution requests. (Domain name resolution is not allowed.)

The developers of AdGuardHome (devteam@adguard.com) haven't replied to my email yet, so I'm discussing this here again, hoping to find a solution.

[louis5974]

Who can solve this problem?