Please follow the below template, it will help us to help you!
Expected Behaviour:
Ads are blocked on my client devices.
Actual Behaviour:
Ads are not blocked on my client devices
Debug Token:
[✓] Your debug token is: ize4m9wiow
Hi guys, I searched through several help posts about this topic but I haven't found a solution yet. PiHole is definitely running on my BeagleBone Black, it's address is reserved in my router's DHCP settings and the only DNS server defined in the router DHCP/DNS settings is the IP of the Beaglebone.
I have released and renewed the IP of my laptop, and that did not help, though the IP address remains the same.
Any ideas? Thanks!
I'm on OSX, so that ipconfig command doesn't work on my machine. I tried setting the DNS server as my Pi-hole in the WiFi preferences, but still I get ads.
I'm also have Avast anti-virus installed, but I saw no difference after disabling both the web-shield and email-shield.
I'm running a Linksys WRT1900ACS and have set one DNS entry there, pointing to the pi-hole.
=]
jfb
November 25, 2018, 8:32pm
4
Your debug log shows why your Pi-Hole is not working. In Version 4.0 of Pi-Hole, which you are running, dnsmasq is included in pihole-FTL, and dnsmasq does not run as a separate process. Your debug log shows the ports in use and dnsmasq is running.
*** [ DIAGNOSING ]: Ports in use
*:3000 systemd (IPv6)
*:1880 systemd (IPv6)
*:22 sshd (IPv4)
*:22 sshd (IPv6)
*:8080 apache2 (IPv6)
*:8080 apache2 (IPv6)
*:8080 apache2 (IPv6)
*:80 lighttpd (IPv4)
*:80 lighttpd (IPv6)
*:53 dnsmasq (IPv4)
*:53 dnsmasq (IPv6)
The fix is to stop and disable dnsmasq and start pihole-FTL
sudo service dnsmasq stop
sudo service dnsmasq disable
sudo service pihole-FTL restart
1 Like
Thanks for the suggestions!
The second command doesn't like the 'disable' option:
debian@beaglebone:~$ sudo service dnsmasq disable
but substituting 'stop' for 'disable' seemed to execute fine. And now:
debian@beaglebone:~$ pihole status
I still get ads as far as Block Ads! is concerned!
What else might I try?
jfb
November 25, 2018, 8:38pm
6
Run a new debug log and post the token.
New log here!:
[✓] Your debug token is: 6bfbc4xw46
jfb
November 25, 2018, 9:39pm
8
dnsmasq is no longer on port 53, but neither is pihole-FTL.
*** [ DIAGNOSING ]: Ports in use
*:3000 systemd (IPv6)
*:1880 systemd (IPv6)
*:22 sshd (IPv4)
*:22 sshd (IPv6)
*:8080 apache2 (IPv6)
*:8080 apache2 (IPv6)
*:8080 apache2 (IPv6)
*:80 lighttpd (IPv4)
*:80 lighttpd (IPv6)
Try removing dnsmasq (so no chance it can interfere) and then restart pihole-FTL:
sudo apt remove dnsmasq
If that doesn't resolve it, then run pihole -r and select "repair"
jfb
November 25, 2018, 9:43pm
9
The correct command should have been:
sudo systemctl disable dnsmasq
Hi again, thanks for your continued support.
I removed dnsmasq, ran pihole repair and rebooted the machine. Pihole still says it's not running. New debug log here:
[✓] Your debug token is: t1g9a1nhyf
For what it's worth, I'm running the latest standard Beaglebone image.
=]
One more thing: when I run repair, or after the install procedure, I have to comment a line ina config file:
dnsmasq: illegal repeated keyword at line 35 of /etc/dnsmasq.d/01-pihole.conf:
#cache-size=10000
That solved the DNS issue a while back but no longer.
And check for alien dnsmasq config files not belonging to Pi-hole:
sudo grep -v '#\|^$' -R /etc/dnsmasq.*
1 Like
Here's what I see in /etc/dnsmasq.conf:
# Include another lot of configuration options.
#conf-file=/etc/dnsmasq.more.conf
conf-dir=/etc/dnsmasq.d
# Include all the files in a directory except those ending in .bak
#conf-dir=/etc/dnsmasq.d,.bak
# Include all files in a directory which end in .conf
#conf-dir=/etc/dnsmasq.d/,*.conf
The alien check shows this:
/etc/dnsmasq.conf:conf-dir=/etc/dnsmasq.d
What does this mean?
=]
Move that alien SoftAp0 file to your home folder:
sudo mv /etc/dnsmasq.d/SoftAp0 ~
Restart:
sudo service pihole-FTL restart
Check status:
sudo service pihole-FTL status -l
pihole status
And try do a DNS lookup:
host pi.hole localhost
1 Like
Hi guys,
pihole-FTL status check shows:
ebian@beaglebone:~$ 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 Sun 2018-11-25 23:01:31 UTC; 5s ago
Docs: man:systemd-sysv-generator(8)
Process: 3178 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 3184 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Nov 25 23:01:30 beaglebone systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 25 23:01:30 beaglebone pihole-FTL[3184]: Not running
Nov 25 23:01:30 beaglebone pihole-FTL[3184]: chown: cannot access '/etc/pihole/dhcp.lea
Nov 25 23:01:30 beaglebone su[3207]: Successful su for pihole by root
Nov 25 23:01:30 beaglebone su[3207]: + ??? root:pihole
Nov 25 23:01:30 beaglebone su[3207]: pam_unix(su:session): session opened for user piho
Nov 25 23:01:31 beaglebone pihole-FTL[3184]: FTL started!
Nov 25 23:01:31 beaglebone systemd[1]: Started LSB: pihole-FTL daemon.
pihols status check shows:
debian@beaglebone:~$ pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
DNS lookup check shows:
ebian@beaglebone:~$ host pi.hole localhost
Using domain server:
Name: localhost
Address: ::1#53
Aliases:
pi.hole has address
I'll go point my router back to the pihole, brb...
Dont point your router WAN DNS .... do this pushing Pi-hole's IP to the clients for DNS via DHCP:
It works! Man, what an ordeal. Seems to me the problem was the SoftAP definition for dnsmasq?
Thanks a ton!
1 Like
That and the dnsmasq daemon still running.
Cheers!!!
1 Like
Ah, yep that's what I meant - I added the pi-hole to my router's DHCP DNS settings.
Mmmm, ok well it was working before I rebooted. How can I get the system to run reliably upon startup?
=]
What troubles do you have now ?
nslookup pi.hole <PIHOLE_IP_ADDRESS>
