[SOLVED] Pihole + Network Manager configuration

[boyboy1]

Please follow the below template, it will help us to help you!

Actual Behaviour:

Dns service not running
FTL is offiline

Hello.

I used pihole with raspbian jessy and it worked very well.

Now I’m on Raspbian Stretch, RPI 3B+.
Recently i have installed Strech with NetworkManager but since pihole never work.

here is my configuration :

**/etc/NetworkManager/NetworkManager.conf**
[main]
plugins=ifupdown,keyfile
#dns=dnsmasq
[ifupdown]
managed=false

**/etc/resolv.conf**
nameserver 127.0.0.1

**/etc/dnsmasq.conf**
listen-address=127.0.0.1

**ls /etc/NetworkManager/dnsmasq.d/**
_cache.conf_

**sudo service pihole-FTL status**
_● pihole-FTL.service - LSB: pihole-FTL daemon_
_   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)_
_   Active: active (exited) since Tue 2018-09-25 22:15:49 CEST; 7min ago_
_     Docs: man:systemd-sysv-generator(8)_
_   CGroup: /system.slice/pihole-FTL.service_

_sept. 25 22:15:48 rasp systemd[1]: Starting LSB: pihole-FTL daemon..._
_sept. 25 22:15:48 rasp pihole-FTL[2564]: Not running_
_sept. 25 22:15:48 rasp pihole-FTL[2564]: Failed to set capabilities on file `/usr/bin/pihole-FTL' (Operation not supported)_
_sept. 25 22:15:48 rasp pihole-FTL[2564]: The value of the capability argument is not permitted for a file. Or the file is not a regular (non-s_
_sept. 25 22:15:48 rasp su[2587]: Successful su for pihole by root_
_sept. 25 22:15:48 rasp su[2587]: + ??? root:pihole_
_sept. 25 22:15:48 rasp su[2587]: pam_unix(su:session): session opened for user pihole by (uid=0)_
_sept. 25 22:15:49 rasp pihole-FTL[2564]: dnsmasq: failed to create listening socket for port 53: Permission denied_
_sept. 25 22:15:49 rasp systemd[1]: Started LSB: pihole-FTL daemon._

 **sudo service dnsmasq status**
_● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server_
_   Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset: enabled)_
_   Active: inactive (dead)_

EDIT: after a rebootI have to run the command sudo service dnsmasq start.
And finally DNS is active on pihole web interface but FTL is offline

how to configure and start automatic dnsmasq at startup and fix FTL ?

Thanks for your help
Boyboy frenchman

Debug Token:

0le4kqx4a5

[boyboy1]

For information

piboy@rasp:~ $ file /usr/bin/pihole-FTL
/usr/bin/pihole-FTL: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=5864a2037d20fbf1a54d3ee377c9ebbc0b7400da, not stripped

piboy@rasp:~ $ dpkg --print-architecture
armhf

piboy@rasp:~ $ uname -a
Linux rasp 4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l GNU/Linux

[jfb]

Your debug log shows dnsmasq running on port 53, and pihole-FTL not running.

*** [ DIAGNOSING ]: Ports in use
...
*:80 lighttpd (IPv4)
*:80 lighttpd (IPv6)
*:53 dnsmasq (IPv4)
*:53 dnsmasq (IPv6)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

@boyboy1

after a rebootI have to run the command sudo service dnsmasq start .

Why are you manually starting dnsmasq? pihole-FTL contains the required dnsmasq code (new to Pi-Hole V 4.0), so dnsmasq should not be running as a separate process.

Pi-hole v4.0 Released With FTLDNS, Improved Blocking Modes, Regex, Docker, and More

Originally published at: https://pi-hole.net/2018/08/06/pi-hole-v4-0-released-with-ftldns-improved-blocking-modes-regex-docker-and-more/ We're very pleased to release Pi-hole v4.0 today, which includes fixes, tweaks, and lots of new stuff, including FTLDNS (special thanks to our beta testers!) In a sentence, FTLDNS is dnsmasq with Pi-hole's special sauce baked in. FTLDNS does everything dnsmasq does because it is dnsmasq--just our fork of it. So all of your existing config files will stil…

[boyboy1]

Hello,
so i do sudo service dnsmasq stop and reboot. Then DNS is running correctly.

piboy@rasp:~ $ pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date

[✓] Everything is up to date!

a new debug show :

76hc9fmbcs

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] mkt354.com is 74.112.69.45 via localhost (127.0.0.1)
[✗] Failed to resolve mkt354.com via Pi-hole (192.168.0.40)
[✓] doubleclick.com is 172.217.22.142 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is inactive
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

I turn around...

[boyboy1]

I explore a track :

sudo systemctl stop dnsmasq
sudo systemctl disable dnsmasq
reboot

sudo systemctl status pihole-FTL -l

sept. 26 15:24:05 rasp pihole-FTL[2385]: dnsmasq: failed to create listening socket for port 53: Permission denied

sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'

Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 2317/lighttpd
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1689/dnsmasq
tcp6 0 0 :::80 :::* LISTEN 2317/lighttpd
udp 0 0 127.0.0.1:53 0.0.0.0:* 1689/dnsmasq

sudo skill 1689
sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'

Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 2317/lighttpd
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 3159/dnsmasq
tcp6 0 0 :::80 :::* LISTEN 2317/lighttpd
udp 0 0 127.0.0.1:53 0.0.0.0:* 3159/dnsmasq

dnsmasq is already running...
Is this normal ?
and FTL on webinterface is offline

[Jeroen1]

Not sure if I am missing something....
You should not run dnsmasq anymore.
Latest Pihole-FTL has dnsmasq "build in" An update to latest version would have disabled DNSmasq for you during update
Disable dnsmasq during boot should fix your issue. As you start the old dnsmasq before the Pihole-ftl service, port 53 is in use.

Try a re-install off pihole.

[deHakkelaar]

@boyboy1

sudo systemctl stop dnsmasq
sudo systemctl disable dnsmasq
reboot

That should stop dnsmasq from starting at boot.

pi@noads:~ $ whereis dnsmasq
dnsmasq: /usr/sbin/dnsmasq /etc/dnsmasq.conf /etc/dnsmasq.d /usr/share/dnsmasq /usr/share/man/man8/dnsmasq.8.gz

pi@noads:~ $ dpkg -S /usr/sbin/dnsmasq
dnsmasq-base: /usr/sbin/dnsmasq

But if it still does start, try remove the package as you wont need it anymore:

sudo apt-get remove dnsmasq-base

Maybe need to run repair after:

pihole -r

[boyboy1]

Hello

@deHakkelaar

pi@noads:~ $ whereis dnsmasq dnsmasq: /usr/sbin/dnsmasq /etc/dnsmasq.conf /etc/dnsmasq.d /usr/share/dnsmasq /usr/share/man/man8/dnsmasq.8.gz pi@noads:~ $ dpkg -S /usr/sbin/dnsmasq dnsmasq-base: /usr/sbin/dnsmasq

I have the same thing as you
But after sudo apt-get remove dnsmasq-base and reboot`
DNS service is not running
FTL is offline

[deHakkelaar]

sudo service pihole-FTL status -l

?

[boyboy1]

piboy@rasp:~ $ sudo service pihole-FTL status -l

● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Wed 2018-09-26 21:16:07 CEST; 9min ago
Docs: man:systemd-sysv-generator(8)

sept. 26 21:16:07 rasp systemd[1]: Starting LSB: pihole-FTL daemon...
sept. 26 21:16:07 rasp pihole-FTL[1881]: Not running
sept. 26 21:16:07 rasp pihole-FTL[1881]: Failed to set capabilities on file `/usr/bin/pihole-FTL' (Operation not supported)
sept. 26 21:16:07 rasp pihole-FTL[1881]: The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
sept. 26 21:16:07 rasp su[1904]: Successful su for pihole by root
sept. 26 21:16:07 rasp su[1904]: + ??? root:pihole
sept. 26 21:16:07 rasp su[1904]: pam_unix(su:session): session opened for user pihole by (uid=0)
sept. 26 21:16:07 rasp pihole-FTL[1881]: dnsmasq: failed to create listening socket for port 53: Permission denied
sept. 26 21:16:07 rasp systemd[1]: Started LSB: pihole-FTL daemon.

[deHakkelaar]

@boyboy1

sept. 26 21:16:07 rasp pihole-FTL[1881]: Failed to set capabilities on file `/usr/bin/pihole-FTL’ (Operation not supported)

DNS Service not running - Ubuntu 16.04.5 LTS

Read this about "Linux capabilities": https://docs.pi-hole.net/ftldns/in-depth/#linux-capabilities And I believe a solution is offered here:

[boyboy1]

I understand the article but I do not understand the solution that is proposed

[deHakkelaar]

Solution is in this post by @DL6ER:

Problem with FTL and dnsmasq after pihole -up (Ubuntu 16.04.5 LTS)

In your /etc/init.d/pihole-FTL you can find a line su -s /bin/sh -c "/usr/bin/pihole-FTL" "$FTLUSER" replace it by /usr/bin/pihole-FTL

Edit the file as proposed with for example nano:

sudo nano /etc/init.d/pihole-FTL

[boyboy1]

OMG
thats all right !!

I tested this a few days ago but it did not work, maybe because of dnsmasq ...

This to fix the problem and everything is working properly

thanks to you