Package Details: pi-hole-server 4.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.1
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 62
Popularity: 2.57
First Submitted: 2016-01-13 12:50
Last Updated: 2020-02-26 10:58

Pinned Comments

max.bra commented on 2019-10-16 15:28

Since switching to pihole user for pihole-FTL - long term data is not retained on my machine.

sir_randomuser said: For some reason account http has expired, which was the root cause. Seems to be due to a recent systemd change: https://bugs.archlinux.org/task/63704
Checking /etc/shadow, the user http had a trailing 1:

$ sudo cat /etc/shadow | grep http
http:!!:18174::::::1:

Removing the expiration date has resolved it:

$ sudo chage --expiredate -1 http

max.bra commented on 2018-02-09 16:45

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.

Matty_r commented on 2016-02-09 11:24

Yes, that's a typo.

Edit: It doesn't appear to be able to ping 8.8.8.8, nor my router at 10.0.0.138. However it can ping other computers on the network.

max.bra commented on 2016-02-09 10:29

> ****
> /etc/resolv.conf =
> nameserver 120.0.0.1 <----- this is a typo yes?
> nameserver 10.0.0.138
> ****

pihole machine can ping 8.8.8.8?

Matty_r commented on 2016-02-09 10:23

@max.bra:

Ok, so i'm still having the same issue.

Router was set to pri 10.0.0.12


****
/etc/resolv.conf =
nameserver 120.0.0.1
nameserver 10.0.0.138
****

Static IP is done through systemd.networkd
****
/etc/systemd/network/eth0.network =
[Network]
DHCP=no
DNS=127.0.0.1
DNS=10.0.0.138

[Address]
Address=10.0.0.12/24

[Route]
Gateway=10.0.0.138
********

/etc/dnsmasq.conf - was replaced by supplied version
/etc/lighttpd/lighttpd.conf - was replaced by supplied version



troubleshooting

# dig google.com
connection timed out; no servers could be reached

# nslookup google.com
connection timed out; no servers could be reached


Matty_r commented on 2016-02-09 07:51

@max.bra:

A couple of differences of what I had:
Router:
DNS pri 10.0.0.12 - sec 8.8.8.8

piHole:
DHCP enabled but 10.0.0.12 was reserved.

It may have been dhcpcd was messing with the config, may need to make sure it's disabled. Give me some time and i'll get back to you with the results. Thanks for your time.

max.bra commented on 2016-02-09 07:43

:: Sure i will say the obvious and you will forgive me for this ::

Router: 10.0.0.138
Static LAN already configured.
DHCP server enabled.
Relevant DHCP options:
Lease 10.0.0.1 - 10.0.0.100
DNS pri 10.0.0.12 - sec 10.0.0.138

Clients:
DHCP client enabled

Pi-Hole:
DHCP client disabled.
Static NIC configuration:
IP addr. 10.0.0.12
DNS pri 127.0.0.1 - sec 10.0.0.138

dnsmasq configured via dnsmasq.complete. enabled and started (see configuration)

----

have we missed something or the problem is more subtle?

edit: typo

Matty_r commented on 2016-02-09 07:25

@max.bra:

Router: 10.0.0.138 (DNS relay & DHCP server)
piHole: 10.0.0.12

Various other clients are from .1 to .100.

I configured my Router to point to 10.0.0.12. piHole didn't appear to be retrieving DNS entries and then I added 8.8.8.8 to the router as a secondary DNS server. All other clients were able to connect at this point. However piHole still wasn't working.

I connected to piHole and it wasn't able to ping google.com nor 8.8.8.8, I then attempted to use pacman but it wouldn't connect either. I could however ping 10.0.0.138.

max.bra commented on 2016-02-09 07:00

hi Matty_r, can i have your lan topology please?

Matty_r commented on 2016-02-09 03:43

I wasn't able to get this working. Is there anything else I need to do a part from what is in the configuration file, on a clean build?

I followed all of the instructions but it wasn't able to get internet access at all after enabling everything. Do I need to disable dhcp for this to work? I have a IP address reservation set up on my DHCP server.

tdkl commented on 2016-02-05 09:15

Ah I see now. Take a look of what modules it loads and if the kernel is somehow modified, can't see a reason why this couldn't be applied on regular Arch install. But many developers nowadays just ship their own "distro" instead.

slackline commented on 2016-02-05 08:47

Ah, thanks for the pointer on pacman @tdkl

I'll look into using whether Archphile can have this resolved, developer seems active, but will also consider plain archlinuxarm, will need to read around about how to get I2S DAC card working though (it was the convenience of having it supported out of the box in Archphile that appealed).

Thanks for your help.