adguardhome: use correct capabilities#28431
Closed
graysky2 wants to merge 1 commit into
Closed
Conversation
The previous json file incorrectly granted CAP_NET_RAW, which AdGuardHome does not use for either DNS or DHCP AFAIK. CAP_NET_BIND_SERVICE is needed for binding privileged DNS and HTTPS ports and CAP_NET_ADMIN for DHCP functionality, matching guidance in the Linux capability documentation (man 7 capabilities, man 7 packet) and consistent with AdGuardHome’s DHCP implementation, which relies on packet sockets and interface operations rather than raw ICMP. If users are only using adguard for DNS, CAP_NET_ADMIN is not needed at all. Signed-off-by: John Audia <therealgraysky@proton.me>
Member
|
This is how it's documented:
Isn't Did you test the DHCP part? |
Contributor
Author
|
Well shit. I read it backwards. After reviewing the docs, and the man pages, I believe you had it right. Sorry for the noise. FYI - I tested with just |
|
@graysky2 On which port is your instance listening? |
Contributor
Author
|
Default port |
|
Thx. Intereseting. Do you mind sharing your OpenWRT config?
I build it myself. Maybe I missed something.
…On 4/29/26 8:35 PM, graysky wrote:
*graysky2* left a comment (openwrt/packages#28431) <https://github.com/
openwrt/packages#28431#issuecomment-4346490782>
Default port
—
Reply to this email directly, view it on GitHub <https://github.com/
openwrt/packages#28431#issuecomment-4346490782>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/
AAIEJESPSBRYWTZZF2KQNTT4YJDQZAVCNFSM6AAAAACS6N5XQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNBWGQ4TANZYGI>.
Triage notifications on the go with GitHub Mobile for iOS <https://
apps.apple.com/app/apple-store/id1477376905?ct=notification-
email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/
details?id=com.github.android&referrer=utm_campaign%3Dnotification-
email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: <openwrt/
***@***.***>
--
Alexander Krause (né Lochmann) PGP key: 0xBC3EF6FD
Bergerhofweg 3b phone: +49.231.28053964
D-58239 Schwerte mobile: +49.151.15738323
|
Contributor
Author
|
Which config? |
Nvm. I figured it out. It is missing dependency on my end: #29277 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📦 Package Details
Maintainer: @GeorgeSapkin @dobo90
(You can find this by checking the history of the package
Makefile.)Description:
The previous json file incorrectly granted
CAP_NET_RAW, which AdGuardHome does not use for either DNS or DHCP AFAIK.CAP_NET_BIND_SERVICEis needed for binding privileged DNS and HTTPS ports andCAP_NET_ADMINfor DHCP functionality, matching guidance in the Linux capability documentation (man 7 capabilities, man 7 packet) and consistent with AdGuardHome’s DHCP implementation, which relies on packet sockets and interface operations rather than raw ICMP.If users are only using adguard for DNS,
CAP_NET_ADMINis not needed at all.🧪 Run Testing Details
✅ Formalities
If your PR contains a patch:
git am(e.g., subject line, commit description, etc.)
We must try to upstream patches to reduce maintenance burden.