Better move the file out of there to your home folder:
sudo mv /etc/dnsmasq.d/SoftAp0 ~
Restart pihole-FTL:
sudo systemctl restart pihole-FTL
And check status again:
sudo netstat -nltp | grep ':471'
sudo systemctl status pihole-FTL -l
ubuntu@sparhawk:~$ sudo netstat -nltp | grep ':471'
ubuntu@sparhawk:~$ sudo systemctl status pihole-FTL -l
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Wed 2018-08-08 23:16:13 CDT; 19s ago
Docs: man:systemd-sysv-generator(8)
Process: 1849 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 1853 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Aug 08 23:16:12 sparhawk systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 08 23:16:12 sparhawk pihole-FTL[1853]: Not running
Aug 08 23:16:12 sparhawk su[1876]: Successful su for pihole by root
Aug 08 23:16:12 sparhawk su[1876]: + ??? root:pihole
Aug 08 23:16:12 sparhawk su[1876]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 08 23:16:12 sparhawk pihole-FTL[1853]: dnsmasq: failed to create listening socket for port 53: Address already in use
Aug 08 23:16:12 sparhawk su[1876]: pam_unix(su:session): session closed for user pihole
Aug 08 23:16:13 sparhawk systemd[1]: Started LSB: pihole-FTL daemon.
I'm beginning to think that somehow dnsmasq and pihole-FTL aren't supposed to be running at the same time. And since pihole-FTL is dnsmasq with special sauce, I think that all the error messages produced by pihole-FTL still say 'dnsmasq'.
So... uninstall dnsmasq?
~ T
sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
?
ubuntu@sparhawk:~$ sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1239/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 1400/dnsmasq
tcp6 0 0 :::80 :::* LISTEN 1239/lighttpd
tcp6 0 0 :::53 :::* LISTEN 1400/dnsmasq
udp 0 0 0.0.0.0:53 0.0.0.0:* 1400/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 1400/dnsmasq
udp6 0 0 :::53 :::* 1400/dnsmasq
sudo systemctl disable dnsmasq
sudo systemctl stop dnsmasq
sudo systemctl enable pihole-FTL
sudo systemctl restart pihole-FTL
sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
sudo systemctl status pihole-FTL -l
?
Woo! 
I think we've beaten it into submission!
THANK YOU!
~ T
ubuntu@sparhawk:~$ sudo systemctl disable dnsmasq
Synchronizing state of dnsmasq.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable dnsmasq
ubuntu@sparhawk:~$ sudo systemctl stop dnsmasq
ubuntu@sparhawk:~$ sudo systemctl enable pihole-FTL
pihole-FTL.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable pihole-FTL
ubuntu@sparhawk:~$ sudo systemctl restart pihole-FTL
ubuntu@sparhawk:~$ sudo netstat -nltp | grep ':471'
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 2119/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 2119/pihole-FTL
ubuntu@sparhawk:~$ sudo systemctl status pihole-FTL -l
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Wed 2018-08-08 23:24:00 CDT; 18s ago
Docs: man:systemd-sysv-generator(8)
Process: 2076 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 2080 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Aug 08 23:23:59 sparhawk systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 08 23:23:59 sparhawk pihole-FTL[2080]: Not running
Aug 08 23:23:59 sparhawk su[2103]: Successful su for pihole by root
Aug 08 23:23:59 sparhawk su[2103]: + ??? root:pihole
Aug 08 23:23:59 sparhawk su[2103]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 08 23:24:00 sparhawk pihole-FTL[2080]: FTL started!
Aug 08 23:24:00 sparhawk su[2103]: pam_unix(su:session): session closed for user pihole
Aug 08 23:24:00 sparhawk systemd[1]: Started LSB: pihole-FTL daemon.
1 Like
Sweet.
I altered below one last moment but it should show more ports that Pi-hole took over:
sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
Just to recap, for those interested in v4.0 on Ubuntu 18.04.1:
ubuntu@sparhawk:~$ uname -a
Linux sparhawk 4.14.54-ti-r63 #1 SMP PREEMPT Thu Jul 12 21:52:17 UTC 2018 armv7l armv7l armv7l GNU/Linux
ubuntu@sparhawk:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
ubuntu@sparhawk:~$ pihole -v
Pi-hole version is v4.0 (Latest: v4.0)
AdminLTE version is v4.0 (Latest: v4.0)
FTL version is v4.0 (Latest: v4.0)
A big thanks to @deHakkelaar, @technicalpyro & RamSet for all the help!! You folks are awesome.
~ T
1 Like
Here you go. Looks much better!
~ T
ubuntu@sparhawk:~$ sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 2119/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1239/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 2119/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 2119/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 1239/lighttpd
tcp6 0 0 :::53 :::* LISTEN 2119/pihole-FTL
udp 0 0 0.0.0.0:53 0.0.0.0:* 2119/pihole-FTL
udp6 0 0 :::53 :::* 2119/pihole-FTL
1 Like
I keep my fingers crossed that you will find a final solution that might be usable for Linux Mint 19.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.