Package Details: pi-hole-server 5.18.4-1

Git Clone URL: https://aur.archlinux.org/pi-hole-server.git (read-only, click to copy)
Package Base: pi-hole-server
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
Keywords: ad block pi-hole
Licenses: EUPL-1.2
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 115
Popularity: 1.68
First Submitted: 2016-01-13 12:50 (UTC)
Last Updated: 2025-01-16 11:35 (UTC)

Dependencies (18)

Required by (2)

Sources (15)

Pinned Comments

max.bra commented on 2018-02-09 16:45 (UTC) (edited on 2019-10-18 23:14 (UTC) by max.bra)

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.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 83 Next › Last »

shackra commented on 2023-03-15 17:55 (UTC) (edited on 2023-03-15 18:22 (UTC) by shackra)

@max.bra I performed one more test using dhclient with Pi-Hole having the DHCP server turned on:

 ╭─jorge@lightyear in ~/ took 1s
 ╰─❯ nc -vzu 192.168.1.2 67

 ╭─jorge@lightyear in ~/ took 5ms
 ╰─❯ echo $?
0

so, the port seems open where I'm running my Pihole, then let's run dhclient...

 ╰─❯ sudo dhclient -v enp5s0
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp5s0/04:d9:f5:7d:50:2a
Sending on   LPF/enp5s0/04:d9:f5:7d:50:2a
Sending on   Socket/fallback
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Welp.

EDIT: I'm setting a Docker compose configuration with the Docker Pi-hole offered by the Pihole project for testing something and I noticed that dhcping returns no answer where dhclient actually gets an answer from the Pihole service. I made a question to Server Fault trying to weed out that I screwed up something in the Docker compose configuration but if everything is fine, then I cannot trust dhcping and relay on dhclient to test if my network has Pihole offering a DHCP server or not, here is the question: https://serverfault.com/questions/1126280/no-answer-from-dhcping-in-alpine-container-when-using-pi-hole-as-dhcp-server-in

max.bra commented on 2023-03-13 14:32 (UTC)

@shackra sorry for the unforgivable delay, done:

sudo dhcping -s 192.168.x.x
[sudo] password di {}: 
Got answer from: 192.168.x.x

shackra commented on 2023-03-09 00:45 (UTC)

max.bra install dhcping and check? dhcping -s <your DHCP server run by Pihole>

max.bra commented on 2023-03-08 23:42 (UTC) (edited on 2023-03-08 23:43 (UTC) by max.bra)

... don't know why i was not up to date: switched to FTL 5.21 and all is operational (or at least it seems to)
Anyone else with DHCP down?

shackra commented on 2023-03-08 22:08 (UTC)

@max.bra I'm running Endeavors OS, I did a clean installation on the server machine and I haven't touch much beyond editing php-fpm systemd service (with systemctl edit as explained on the wiki) to add 04-pihole-static-dhcp.conf to the list and changing the network mask from 24 to 16 at /etc/pihole/setupVars.conf, everything post-install.

I'm not certain how to check what is my kernel Linux LTS v6.1.15 capable of, but I ran getpcaps with the PID of pihole-FTL and got the following

❯ getpcaps 53380
53380: cap_chown,cap_net_bind_service,cap_net_admin,cap_net_raw,cap_ipc_lock,cap_sys_nice=eip

max.bra commented on 2023-03-08 22:00 (UTC)

@shackra And more (important): is your kernel capable of

AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_NET_RAW CAP_NET_ADMIN CAP_SYS_NICE CAP_IPC_LOCK CAP_CHOWN

?

max.bra commented on 2023-03-08 21:55 (UTC) (edited on 2023-03-08 21:57 (UTC) by max.bra)

@shackra My home LAN is based on pihole-FTL 5.20.1 and all seems operation as usual.
Before and after edit DHCP leases (via web admin), permissions on 04-pihole-static-dhcp.conf are

-rw-r--r-- 1 root root  453 mar  8 22:41 04-pihole-static-dhcp.conf

Status of FTL service is normal

What is your system? Have you modified any config somewhere?

Are you executing FTL as user pihole?

shackra commented on 2023-03-08 21:25 (UTC) (edited on 2023-03-08 21:25 (UTC) by shackra)

I have written a sort-of report explaining that currently pi-hole has no working DHCP server for some reason unknown to me in the discussion section of Pi-hole at the Arch Wiki https://wiki.archlinux.org/title/Talk:Pi-hole#DHCP_not_working, can you please check it out and comment?

max.bra commented on 2023-02-11 11:30 (UTC)

@PS0 the lighttpd conf in this package is an example not a drop in replacement for all configurations

PS0 commented on 2023-02-11 11:17 (UTC) (edited on 2023-02-11 11:18 (UTC) by PS0)

I noticed that the lighttpd example configuration is missing a line to include the external configuration(s):

include "external*.conf"

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 83 Next › Last »