Auto-connect of network-control for AdGuard Home

Good day! We would like to request auto-connect of the network-control plug for our snap, adguard-home, an ad-blocking DNS server. We’ve already asked for it in the past, but back then we thought that network-observe would be enough. Unfortunately, that doesn’t seem to be the case.

For our DHCP server functionality, we need to be able to handle raw sockets, and the output of snappy-debug seems to show that that is currently blocked by snap:

sudo snap run snappy-debug
INFO: Following '/var/log/syslog'. If have dropped messages, use:
INFO: $ sudo journalctl --output=short --follow --all | sudo snappy-debug
kernel.printk_ratelimit = 0
= AppArmor =
Time: Dec 23 21:36:57
Log: apparmor="DENIED" operation="create" profile="snap.adguard-home.adguard-home" pid=601261 comm="AdGuardHome" family="packet" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"

On the other hand, if we manually connect the network-control plug, it works with no warnings.

Can we get network-control to auto-connect? Is there a better plug for this?

Thanks.

+1 from me - this is core functionality of adguard to handle DHCP.

1 Like

+1 from me as well for auto-connect network-control to adguard-home since its required to allow raw sockets. +2 votes for, 0 votes against. Granting auto-connect of network-control to adguard-home. This is now live.

1 Like

Thank you all! This will make the lives of our clients easier.