Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: pi-hole-core 6.0.6-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/pi-hole-core.git (read-only, click to copy)
Package Base:	pi-hole-core
Description:	The Pi-hole is an advertising-aware DNS/Web server. Arch adaptation for lan wide DNS server.
Upstream URL:	https://github.com/pi-hole/pi-hole
Licenses:	EUPL-1.2
Conflicts:	pi-hole-server, pi-hole-standalone
Provides:	pi-hole-server, pi-hole-standalone
Submitter:	max.bra
Maintainer:	max.bra (graysky)
Last Packager:	max.bra
Votes:	120
Popularity:	2.05
First Submitted:	2025-02-21 17:31 (UTC)
Last Updated:	2025-03-30 17:07 (UTC)

Dependencies (11)

bind (bind-git^AUR)
git (git-git^AUR, git-gl^AUR)
inetutils (inetutils-git^AUR)
iproute2 (iproute2-git^AUR, iproute2-selinux^AUR)
jq (jq-git^AUR, jaq-bin^AUR)
logrotate (logrotate-git^AUR, logrotate-selinux^AUR)
lsof (lsof-git^AUR)
netcat (nmap-netcat^AUR, openbsd-netcat-git^AUR, gnu-netcat-svn^AUR, gnu-netcat, openbsd-netcat)
pi-hole-ftl^AUR
procps-ng (procps-ng-git^AUR)
sudo (fake-sudo^AUR, polkit-fakesudo^AUR, sudo-git^AUR, doas-sudo-shim^AUR, sudo-hg^AUR, fudo-git^AUR, sudo-selinux^AUR, sudo-rs-symlink^AUR)

Required by (3)

padd-git (requires pi-hole-server)
pi-hole-whitelist-git (requires pi-hole-server) (optional)
pi-hole-whitelist-git (requires pi-hole-standalone) (optional)

Sources (10)

Pinned Comments

max.bra commented on 2025-02-21 21:44 (UTC)

ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.

First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.

max.bra commented on 2025-02-21 17:56 (UTC)

to update to pi-hole 6, please use pi-hole-core pi-hole-ftl and pi-hole-web packages.

Latest Comments

« First ‹ Previous 1 .. 52 53 54 55 56 57 58 59 60 61 62 .. 87 Next › Last »

ChuckHL commented on 2018-08-27 15:48 (UTC) (edited on 2018-08-27 15:54 (UTC) by ChuckHL)

If I leave gravity.list in the new format (per se) without the host ip in front of each domain and I try to go to those websites, the browser does not know where to go and returns an error that could not resolve the name (ERR_NAME_NOT_RESOLVED). If I add the host in front of each line I now can see "website blocked" pi-hole page.

max.bra commented on 2018-08-27 15:44 (UTC)

it's intentional since dnsmasq integration: https://github.com/pi-hole/pi-hole/commit/bac9e005aed0ac10ea9dfa63123ef1b5a9b7c72d#diff-9e53ae7c3c4f9235e5908d902fb93c8a

only local.list is leaved in hosts format

if you browse, for example, zzhomes.com you will receive tipical pihole blocking notification.

ChuckHL commented on 2018-08-27 15:37 (UTC) (edited on 2018-08-27 15:39 (UTC) by ChuckHL)

As a temp solution I am running "sed -i -e 's/^/10.0.0.10 /' gravity.list" and "sed -i -e 's/^/10.0.0.10 /' black.list" after pihole -g to fix the issue for now.

(of course 10.0.0.10 is the ip of my pihole (for other people reading this) and needs to point to your own pihole)

max.bra commented on 2018-08-27 15:24 (UTC)

yes variable names are the same as before...

still looking...

ChuckHL commented on 2018-08-27 15:18 (UTC)

Checked SetupVars.conf and its the same as it was when I was running pihole v3. Not sure if IPV6 needs to be setup (I didnt have it on v3 either).

PIHOLE_INTERFACE=eth1 IPV4_ADDRESS=10.0.0.10/24 IPV6_ADDRESS= PIHOLE_DNS_1=10.0.0.1 DNS_FQDN_REQUIRED=false DNS_BOGUS_PRIV=false DNSSEC=false WEBPASSWORD=XXX TEMPERATUREUNIT=C WEBUIBOXEDLAYOUT=boxed API_EXCLUDE_DOMAINS=ArchPC,Alarm API_QUERY_LOG_SHOW=all API_PRIVACY_MODE=false

max.bra commented on 2018-08-27 15:15 (UTC)

@ChuckHL

same format for me. blocked traffic is so redirected to localhost. i don't know yet where the problem is. guessing it is on our SetupVars.conf...

looking into it...

ChuckHL commented on 2018-08-27 15:08 (UTC) (edited on 2018-08-27 15:09 (UTC) by ChuckHL)

Need help. Just updated from version 3 to 4 and now blocked sites are no longer redirecting to pihole server.

I noticed that my gravity.list (and also black.list) on version 3 showed results like this: 10.0.0.10 zzztube.com 10.0.0.10 zzzz2233.cn 10.0.0.10 zzzzz4.52896368.com 10.0.0.10 zzzzzz.com

where as on version 4 is only like this: zzztube.com zzzz2233.cn zzzzz4.52896368.com zzzzzz.com

I assume that is where the problem now starts since it no longer knows to redirect to pi-hole server's IP.

max.bra commented on 2018-08-27 08:33 (UTC)

hi jonandermb, "zero domain on blocklist" should be a problem about /etc/dnsmasq.conf: follow the arch pihole wiki.

DNS resolution not available should be this? https://github.com/pi-hole/pi-hole/issues/1800

sounds strange you have this only on after update...

jonandermb commented on 2018-08-27 03:07 (UTC)

Just updated from 3.x to 4.0 and this is what I get if I want to update the lists: "[✗] DNS resolution is currently unavailable". I also have the "zero domains on blocklist" issue, although i see there's certainly blocking on my network.

phixion commented on 2018-08-26 16:11 (UTC) (edited on 2018-08-26 16:21 (UTC) by phixion)

I ran into another issue, it seems in the default config pihole is unable to write the sqlite databse file which means on every restart of the pi or the service your statistics are being reset. It's no showstopper but not nice either.

https://phx.ms/s/S8gX.txt

Dirty way to fix it is to change the permissions of the file/directory so the process can write to it.

https://phx.ms/s/BI84.txt

I guess the elegant way is to have a dedicated serviceaccount for this and the right permissions.

edit: this probably belongs more to pi-hole-ftl than this package

« First ‹ Previous 1 .. 52 53 54 55 56 57 58 59 60 61 62 .. 87 Next › Last »