Repository navigation
Conversation
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
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.
What it does
Pi-hole blocks ads and trackers for the whole network by answering its DNS. This script wraps the TrueNAS stable app
pihole.How it installs
The script asks one question, the admin password, with a random default and the generate button. Its description also tells the user to point the router's DNS at the server.
Port 53 needed a different setup on HexOS:
0.0.0.0:53fails. The TrueNAS virtualization service holds10.48.24.1:53onincusbr0, so the render's conflict check refuses the install. Your remote access also holds port 53 onhexos0.app.ip_choicesoffers only0.0.0.0and::, sohost_ipscannot pick the LAN address.FTLCONF_misc_dnsmasq_linesaddsbind-dynamic,except-interface=incusbr0andexcept-interface=hexos0. Pi-hole then binds every interface address except those two.Other choices:
adlists.listas root before Pi-hole took ownership of the folder, and the folder's ACL has no everyone entry. Pi-hole's gravity run then could not read it and built an empty blocklist.FTLCONF_ntp_ipv4_active,FTLCONF_ntp_ipv6_activeandFTLCONF_ntp_sync_activeare off. TrueNAS already runs NTP on port 123, and on the host network Pi-hole could otherwise set the server's clock./admin/.Testing
bun _lib/validate.tspasses with 0 errors and 0 warnings.doubleclick.netresolved to0.0.0.0. Normal names resolved through192.168.1.65:53, and the Incus and remote access DNS listeners kept answering on their own addresses. The admin password signed in through the API and a wrong one was refused. The host clock stayed synchronized.Known limits
incusbr0andhexos0? If not, the dnsmasq lines need another approach.