Package Details: pi-hole-ftl 5.25.2-2

Git Clone URL: https://aur.archlinux.org/pi-hole-ftl.git (read-only, click to copy)
Package Base: pi-hole-ftl
Description: The Pi-hole FTL engine
Upstream URL: https://github.com/pi-hole/FTL
Licenses: EUPL-1.2
Conflicts: dnsmasq
Provides: dnsmasq
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 56
Popularity: 1.50
First Submitted: 2017-05-07 15:23 (UTC)
Last Updated: 2024-08-10 09:53 (UTC)

Required by (65)

Sources (6)

Pinned Comments

max.bra commented on 2018-02-09 16:46 (UTC) (edited on 2019-10-18 23:13 (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 .. 44 Next › Last »

max.bra commented on 2021-12-25 08:56 (UTC) (edited on 2021-12-25 08:57 (UTC) by max.bra)

@Mettacrawer How do you start FTL? What is your system?
The service pi-hole-FTL.service takes care of this directly and there should be no need to do anything manually.
Otherwise there would be an entry on the wiki don't you think?

Mettacrawer commented on 2021-12-24 22:05 (UTC) (edited on 2021-12-24 22:07 (UTC) by Mettacrawer)

I updated to 5.12.1-1 today and pihole-FTL complained of missing capabilities:

WARNING: Required Linux capability CAP_IPC_LOCK not available
WARNING: Required Linux capability CAP_CHOWN not available

(and so on)

I was able to make it start by adding the capabilities to the pihole-FTL binary:

sudo setcap cap_net_admin,cap_net_bind_service,cap_net_raw,cap_sys_nice,cap_chown,cap_ipc_lock=ep /usr/bin/pihole-FTL

I'm not sure if that is the best way to fix it.

compiler1413 commented on 2021-10-25 13:58 (UTC) (edited on 2021-10-25 13:59 (UTC) by compiler1413)

Hi, not to detract from existing issues, I've wanted to report another race condition for a while.

Perhaps this is just me, but if I restart pihole-FTL systemd service too fast, or sometimes even with an existing but killed service, files may be left in /dev/shm that cause a conflict to start the process.

pihole-FTL[15477]: ########## FTL started! ##########
pihole-FTL[15477]: FTL branch: master
pihole-FTL[15477]: FTL version: v5.8.1
pihole-FTL[15477]: FTL commit: builtfromreleasetarball
pihole-FTL[15477]: FTL date: 2021-04-21
pihole-FTL[15477]: FTL user: pihole
pihole-FTL[15477]: Compiled for armv7l (compiled locally) using cc (GCC) 10.2.0
pihole-FTL[15477]: FATAL: create_shm(): Failed to create shared memory object "FTL-lock": File exists
pihole-FTL[15477]: Initialization of shared memory failed.
systemd[1]: pihole-FTL.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 3.
systemd[1]: Stopped Pi-hole FTLDNS engine.
systemd[1]: pihole-FTL.service: Start request repeated too quickly.
systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Pi-hole FTLDNS engine.

I'm not sure if there's a way to wipe any /dev/shm/FTL* files before starting the process, I'm not entirely familiar with systemd service files.

max.bra commented on 2021-10-16 13:56 (UTC)

@kaivai
1) seems to be a race condition. for some reason systemd is starting FTL before network is fully up... network manager used (have you tried with systemd-netword)?
2) no idea without further configurations.

kaivai commented on 2021-10-16 13:22 (UTC) (edited on 2021-10-16 13:23 (UTC) by kaivai)

Thanks max.bra! Apologies, this is my first use of dnsmasq and I am not experienced at networks - I am likely doing something incorrect.

Q1. network-online.target is not mandatory ..

That sounds very reasonable to me!

Q2. do you have pi-hole on a "firewall" box with two nics?

No, I encountered this on two separate devices connected to the same (regular consumer) router, while using this with pi-hole-standalone. Replies to DNS queries like host google.com 127.0.0.1 weren't making it back to my lo interface. I was able to watch the request/reply with tcpdump -i any port 53 as the A? google.com went out and A 142.251.32.78 was sent back but it never reached my loopback interface and the request eventually timed out.

max.bra commented on 2021-10-13 08:53 (UTC) (edited on 2021-10-13 08:57 (UTC) by max.bra)

hi kaivai, arch packages are not necessarily working out of the box. often there is a need for configuration and adaptations for your system. for example, lighttpd is an optional dep (because you can use other web server) and of course web interface is not working without user intervention.
1) network-online.target is not mandatory (dnsmasq can resolve lan hostnames only and live happy) and you are the first submitting this problem. perhaps the problem lies in your particular configuration.
2) reading the dnsmasq documentation, bind-interfaces has nothing to do with dhcp especially if external.

-z, --bind-interfaces
        On systems which support it, dnsmasq binds the wildcard address, even 
when it is listening on only some interfaces. It then discards requests that it 
shouldn't reply to. This has the advantage of working even when interfaces come 
and go and change address. This option forces dnsmasq to really bind only the 
interfaces it is listening on. About the only time when this is useful is when 
running another nameserver (or another instance of dnsmasq) on the same machine.
Setting this option also enables multiple instances of dnsmasq which provide 
DHCP service to run in the same machine.

do you have pi-hole on a "firewall" box with two nics?

kaivai commented on 2021-10-13 01:21 (UTC) (edited on 2021-10-13 01:22 (UTC) by kaivai)

Thanks for this package! Not sure if this belongs upstream, but in case you would like them. I needed to make 2x changes for this to work for me:

1) if not requires network-online.target, service start fails due to network-interface not existing yet.

# /lib/systemd/system/pihole-FTL.service
[Unit]
After=network.target network-online.target

# ...

2) set bind-interfaces for networks with DHCP provided by non-dnsmasq/pihole

# /etc/dnsmasq.conf

bind-interfaces

graysky commented on 2021-08-24 12:03 (UTC)

@PowaBanga - Builds for me on aarch64 (RPi4 not 3 but shouldn't matter). Are you using makepkg or some aurhelper? Hint: never use an aurhelper.

max.bra commented on 2021-08-24 12:02 (UTC)

Hi powabanga, I'm on mobile and can't read properly all but I think that you too are in need of a swap space. Current ftl need about 800mb of ram to compile.

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