Something is causing gravity.sh to output to the bash shell. What is the output from cd /etc/.pihole && sudo git status?
pi@raspberrypi:~ $ cd /etc/.pihole && sudo git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory cleanOkay, try pihole -r and go through the repair function. We'll see if that fixes the gravity.sh problem.
I guess there is the problem:
[i] Preparing to run gravity.sh to refresh hosts...
[i] Cleaning up previous install (preserving whitelist/blacklist)
[i] Running gravity.sh
[✗] DNS resolution is currently unavailable
[✓] DNS resolution is now availableWhen installing Pi Hole I edited /etc/resolv.conf and changed nameserver to 8.8.8.8 and 8.8.4.4
After googling for the issue I found this might be the point ...
That's a kind of confusing status report, but the first error of Resolution unavailable is superseded by the following message of Resolution available. Everything should be okay now, try a new pihole -d and we'll take a look.
pi@raspberrypi:~ $ pihole -d
This process collects information from your Pi-hole, and optionally uploads it t o a unique and random directory on tricorder.pi-hole.net.
The intent of this script is to allow users to self-diagnose their installations . This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a smal l team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.
NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers c an access your data via the given token. We have taken these extra steps to secu re your data and will work to further reduce any personal information gathered.
*** [ INITIALIZING ]
[i] 2018-03-02:23:03:58 debug log has been initialized.
*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...
*** [ DIAGNOSING ]: Core version
[i] Core: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.3-0-g1e87850
*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa29
*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0
*** [ DIAGNOSING ]: dnsmasq version
[i] 2.76
*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.35
*** [ DIAGNOSING ]: php version
[i] 5.6.33
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 8 (jessie)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
/opt/pihole/piholeDebug.sh: line 470: $'[\E[32m✓\E[0m] \E[32marmv6l\E[0m': command not found
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.178.26/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth0 interface:
2001:16b8:401f:ee00:3df4:5e13:afc9:9f76 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
fe80::6673:6a53:a019:2992 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
[i] Default IPv4 gateway: 192.168.178.1
* Pinging 192.168.178.1...
[✓] Gateway responded.
[i] Default IPv6 gateway: fe80::3681:c4ff:fe0d:fc6b
* Pinging fe80::3681:c4ff:fe0d:fc6b...
[✓] Gateway responded.
*** [ DIAGNOSING ]: Ports in use
[22] is in use by sshd
[53] is in use by dnsmasq
[80] is in use by lighttpd
[] is in use by
[4711] is in use by pihole-FTL
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] 208.185.87.145.liveadvert.com is 192.168.178.26 via localhost (127.0.0.1)
[✓] 208.185.87.145.liveadvert.com is 192.168.178.26 via Pi-hole (192.168.178.26)
[✓] doubleclick.com is 108.177.119.101 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] msnhomepage.com is 2001:16b8:4042:e500:a58f:6fff:2a03:6534 via localhost (::1)
[✗] Failed to resolve msnhomepage.com via Pi-hole (2001:16b8:4042:e500:a58f:6fff:2a03:6534)
[✓] doubleclick.com is 2a00:1450:4005:80b::200e via a remote, public DNS server (2001:4860:4860::8888)
*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Setup variables
DHCP_START=192.168.178.201
DHCP_END=192.168.178.251
DHCP_ROUTER=192.168.178.1
DHCP_LEASETIME=24
PIHOLE_DOMAIN=lan
DHCP_IPv6=false
DNSMASQ_LISTENING=single
PIHOLE_DNS_3=192.168.178.1
DNS_FQDN_REQUIRED=false
DNS_BOGUS_PRIV=true
DNSSEC=false
DHCP_ACTIVE=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.178.26/24
IPV6_ADDRESS=2001:16b8:4042:e500:a58f:6fff:2a03:6534
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1
*** [ DIAGNOSING ]: Dashboard and block page
[✓] X-Pi-hole: A black hole for Internet advertisements.
[✓] X-Pi-hole: The Pi-hole Web interface is working!
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 12385218 Mar 2 22:26 /etc/pihole/gravity.list
-----head of gravity.list------
192.168.178.26 0.0.0.0
2001:16b8:4042:e500:a58f:6fff:2a03:6534 0.0.0.0
192.168.178.26 0.r.msn.com
2001:16b8:4042:e500:a58f:6fff:2a03:6534 0.r.msn.com
-----tail of gravity.list------
192.168.178.26 zzz.clickbank.net
2001:16b8:4042:e500:a58f:6fff:2a03:6534 zzz.clickbank.net
192.168.178.26 ɢoogle.com
2001:16b8:4042:e500:a58f:6fff:2a03:6534 ɢoogle.com
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 633 Feb 27 13:14 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt
-rw-r--r-- 1 root root 150 Mar 2 22:26 /etc/pihole/local.list
192.168.178.26 raspberrypi
2001:16b8:4042:e500:a58f:6fff:2a03:6534 raspberrypi
192.168.178.26 pi.hole
2001:16b8:4042:e500:a58f:6fff:2a03:6534 pi.hole
-rw-r--r-- 1 root root 234 Mar 2 22:18 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
-rw-r--r-- 1 root root 117 Feb 27 13:15 /etc/pihole/whitelist.txt
raw.githubusercontent.com
mirror1.malwaredomains.com
sysctl.org
zeustracker.abuse.ch
s3.amazonaws.com
hosts-file.net
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rw-r--r-- 1 root root 1540 Mar 2 22:18 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries=extra
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=8.8.8.8
server=8.8.4.4
server=192.168.178.1
bogus-priv
interface=eth0
*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 3027 Mar 2 22:18 /etc/lighttpd/lighttpd.conf
server.modules = (
"mod_access",
"mod_accesslog",
"mod_auth",
"mod_expire",
"mod_compress",
"mod_redirect",
"mod_setenv",
"mod_rewrite"
)
server.document-root = "/var/www/html"
server.error-handler-404 = "pihole/index.php"
server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( "index.php", "index.html", "index.lighttpd.html" )
url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
$HTTP["url"] =~ "^/admin/" {
setenv.add-response-header = (
"X-Pi-hole" => "The Pi-hole Web interface is working!",
"X-Frame-Options" => "DENY"
)
$HTTP["url"] =~ ".ttf$" {
setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
}
$HTTP["url"] =~ "^/admin/\.(.*)" {
url.access-deny = ("")
}
include_shell "cat external.conf 2>/dev/null"
*** [ DIAGNOSING ]: contents of /etc/cron.d
-rw-r--r-- 1 root root 1495 Mar 2 22:18 /etc/cron.d/pihole
7 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
52 13 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
-rw-r--r-- 1 www-data www-data 1323 Mar 2 22:19 /var/log/lighttpd/error.log
2018-02-27 11:41:27: (log.c.164) server started
2018-02-27 12:17:15: (log.c.164) server started
2018-02-27 12:25:50: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 47
2018-02-27 12:26:03: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 47
2018-02-27 12:34:59: (server.c.1558) server stopped by UID = 0 PID = 1
2018-02-27 12:35:19: (log.c.164) server started
2018-02-27 13:11:02: (server.c.1558) server stopped by UID = 0 PID = 1
2018-02-27 13:11:23: (log.c.164) server started
2018-02-27 13:29:04: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 72
2018-02-27 13:29:09: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 47
2018-02-27 17:17:16: (log.c.164) server started
2018-03-02 22:16:36: (server.c.1558) server stopped by UID = 0 PID = 1
2018-03-02 22:16:39: (log.c.164) server started
2018-03-02 22:19:09: (server.c.1558) server stopped by UID = 0 PID = 1
2018-03-02 22:19:12: (log.c.164) server started
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 12430 Mar 2 22:26 /var/log/pihole-FTL.log
[2018-03-02 00:00:02.232] NOTICE: pihole.log has been flushed
[2018-03-02 00:00:02.233] Resetting internal data structure
[2018-03-02 00:00:02.233] Queries in memory before flushing: 84
[2018-03-02 00:00:02.234] FATAL: Trying to free NULL pointer in pihole_log_flushed() (flush.c:61)
[2018-03-02 00:00:02.855] Gravity list entries: 123564
[2018-03-02 00:00:02.856] No blacklist present
[2018-03-02 00:00:02.856] No wildcard blocking list present
[2018-03-02 00:00:02.860] Notice: Increasing queries struct size from 0 to 10000 (440.83 KB)
[2018-03-02 00:00:02.860] Notice: Increasing domains struct size from 0 to 1000 (460.83 KB)
[2018-03-02 00:00:02.861] Notice: Increasing clients struct size from 0 to 10 (460.99 KB)
[2018-03-02 00:00:02.876] New client: 192.168.178.20 (0/10)
[2018-03-02 00:00:02.877] Notice: Increasing forwarded struct size from 0 to 4 (461.09 KB)
[2018-03-02 00:00:02.893] New forward server: 192.168.178.1 (0/4)
[2018-03-02 00:00:02.894] Notice: Increasing overTime struct size from 0 to 100 (465.10 KB)
[2018-03-02 00:00:02.909] New client: 192.168.178.24 (1/10)
[2018-03-02 00:00:02.910] New client: 127.0.0.1 localhost (2/10)
[2018-03-02 00:00:02.911] Notice: Increasing overTime struct size from 100 to 200 (470.03 KB)
[2018-03-02 00:00:02.913] Imported 32 queries from the long-term database
[2018-03-02 00:00:02.914] Reading from /var/log/pihole.log (rw-r--r--)
[2018-03-02 05:24:56.846] New client: 192.168.178.25 (3/10)
[2018-03-02 05:24:56.900] New forward server: 8.8.4.4 google-public-dns-b.google.com (1/4)
[2018-03-02 16:03:01.901] Notice: Increasing overTime struct size from 200 to 300 (475.21 KB)
[2018-03-02 19:04:27.761] New client: 192.168.178.21 (4/10)
[2018-03-02 19:43:53.885] New forward server: 8.8.8.8 google-public-dns-a.google.com (2/4)
[2018-03-02 19:44:46.373] NOTICE: Received signal SIGHUP - re-reading gravity files
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 303237 Mar 2 23:04 /var/log/pihole.log
-----head of pihole.log------
Mar 2 00:00:02 dnsmasq[573]: 3806 127.0.0.1/33330 query[PTR] 20.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 00:00:02 dnsmasq[573]: 3806 127.0.0.1/33330 config 192.168.178.20 is NXDOMAIN
Mar 2 00:00:02 dnsmasq[573]: 3807 127.0.0.1/35037 query[PTR] 1.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 00:00:02 dnsmasq[573]: 3807 127.0.0.1/35037 config 192.168.178.1 is NXDOMAIN
Mar 2 00:00:02 dnsmasq[573]: 3808 127.0.0.1/37358 query[PTR] 24.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 00:00:02 dnsmasq[573]: 3808 127.0.0.1/37358 config 192.168.178.24 is NXDOMAIN
Mar 2 00:00:02 dnsmasq[573]: 3809 127.0.0.1/41033 query[PTR] 20.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 00:00:03 dnsmasq[573]: 3809 127.0.0.1/41033 config 192.168.178.20 is NXDOMAIN
Mar 2 00:00:03 dnsmasq[573]: 3810 127.0.0.1/58039 query[PTR] 24.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 00:00:03 dnsmasq[573]: 3810 127.0.0.1/58039 config 192.168.178.24 is NXDOMAIN
Mar 2 00:59:00 dnsmasq[573]: 3811 127.0.0.1/40202 query[PTR] 20.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 00:59:00 dnsmasq[573]: 3811 127.0.0.1/40202 config 192.168.178.20 is NXDOMAIN
Mar 2 00:59:00 dnsmasq[573]: 3812 127.0.0.1/44760 query[PTR] 24.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 00:59:00 dnsmasq[573]: 3812 127.0.0.1/44760 config 192.168.178.24 is NXDOMAIN
Mar 2 01:59:00 dnsmasq[573]: 3813 127.0.0.1/38105 query[PTR] 20.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 01:59:00 dnsmasq[573]: 3813 127.0.0.1/38105 config 192.168.178.20 is NXDOMAIN
Mar 2 01:59:00 dnsmasq[573]: 3814 127.0.0.1/50244 query[PTR] 24.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 01:59:00 dnsmasq[573]: 3814 127.0.0.1/50244 config 192.168.178.24 is NXDOMAIN
Mar 2 02:59:00 dnsmasq[573]: 3815 127.0.0.1/49425 query[PTR] 20.178.168.192.in-addr.arpa from 127.0.0.1
Mar 2 02:59:00 dnsmasq[573]: 3815 127.0.0.1/49425 config 192.168.178.20 is NXDOMAIN
********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **Looks like you have IPv6 capable clients and Pi-hole, but the IPv6 address is not set up correctly. Try using ULA's instead as they are more stable than the GUA addresses.
1 Like
Hi,
I changed the ULA settings in my router, as DL6ER suggested. Log stil shows
[✓] IPv6 address(es) bound to the eth0 interface: 2001:16b8:4063:3e00:87cd:e2a0:2ce7:d3b0 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127) fd00::40b0:9dc4:ae95:ed07 matches the IP found in /etc/pihole/setupVars.conf fe80::824b:e37c:4274:c6cd does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
I copied the Code in DL6ERs Thread, but it does not seem to change a thing.
IPV6_ADDRESS=$(ip -6 a | grep 'fc\|fd' | awk -F " " '{gsub("/[0-9]*",""); print $2}')
echo ${IPV6_ADDRESS}
sed -i.setupVars.bak "/IPV6_ADDRESS/d;" "/etc/pihole/setupVars.conf"
echo "IPV6_ADDRESS=${IPV6_ADDRESS}" >> "/etc/pihole/setupVars.conf"
pihole -gDid you do a pihole -r > Repair after making the change?
Hi,
yes, now I did. I'm not certrain if it is completely working at the moment. Debug stil shows:
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.178.26/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth0 interface:
2001:16b8:4063:3e00:87cd:e2a0:2ce7:d3b0 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
fd00::40b0:9dc4:ae95:ed07 matches the IP found in /etc/pihole/setupVars.conf
fe80::824b:e37c:4274:c6cd does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
Afterwards I tried it again copying line by line of the code in DL6ER, it says
sed -i.setupVars.bak "/IPV6_ADDRESS/d;" "/etc/pihole/setupVars.conf"
sed: couldn't open temporary file /etc/pihole/sedF9mi0N: Permission denied
Using the code as su does not seem to change a thing...
Is your disk full? Check df -h
Hi,
Filesystem Size Used Avail Use% Mounted on
/dev/root 7.3G 1.1G 5.9G 15% /
devtmpfs 213M 0 213M 0% /dev
tmpfs 218M 0 218M 0% /dev/shm
tmpfs 218M 17M 201M 8% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 218M 0 218M 0% /sys/fs/cgroup
/dev/mmcblk0p1 42M 21M 21M 51% /bootUpdate, still not blocking properly.
*** [ INITIALIZING ]
[i] 2018-03-11:10:32:14 debug log has been initialized.
*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...
*** [ DIAGNOSING ]: Core version
[i] Core: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.3-0-g1e87850
*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa29
*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0
*** [ DIAGNOSING ]: dnsmasq version
[i] 2.76
*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.35
*** [ DIAGNOSING ]: php version
[i] 5.6.33
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 8 (jessie)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
/opt/pihole/piholeDebug.sh: line 470: $'[\E[32m✓\E[0m] \E[32marmv6l\E[0m': comma nd not found
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.178.26/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth0 interface:
2001:16b8:4002:fe00:f2f5:83b2:a077:d598 does not match the IP found in /etc/p ihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for -pi-hole/2127)
fd00::40b0:9dc4:ae95:ed07 matches the IP found in /etc/pihole/setupVars.conf
fe80::824b:e37c:4274:c6cd does not match the IP found in /etc/pihole/setupVar s.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupV ars.conf, there is no need for concern.
The link to the FAQ is for an issue that sometimes occurs when the IPv6 addre ss changes, which is why we check for it.
[i] Default IPv4 gateway: 192.168.178.1
* Pinging 192.168.178.1...
[✓] Gateway responded.
[i] Default IPv6 gateway: fe80::3681:c4ff:fe0d:fc6b
* Pinging fe80::3681:c4ff:fe0d:fc6b...
[✓] Gateway responded.
*** [ DIAGNOSING ]: Ports in use
[22] is in use by sshd
[53] is in use by dnsmasq
[80] is in use by lighttpd
[] is in use by
[4711] is in use by pihole-FTL
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a k nown ad-serving domain
[✓] ad.doubleclick.net.21805.9075.302br.net is 192.168.178.26 via localhost (127 .0.0.1)
[✓] ad.doubleclick.net.21805.9075.302br.net is 192.168.178.26 via Pi-hole (192.1 68.178.26)
[✓] doubleclick.com is 172.217.18.14 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a k nown ad-serving domain
[✓] altfarm.mediaplex.com.77799.9664.302br.net is fd00::40b0:9dc4:ae95:ed07 via localhost (::1)
[✓] altfarm.mediaplex.com.77799.9664.302br.net is fd00::40b0:9dc4:ae95:ed07 via Pi-hole (fd00::40b0:9dc4:ae95:ed07)
[✓] doubleclick.com is 2a00:1450:4005:803::200e via a remote, public DNS server (2001:4860:4860::8888)
*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Setup variables
DHCP_START=192.168.178.201
DHCP_END=192.168.178.251
DHCP_ROUTER=192.168.178.1
DHCP_LEASETIME=24
PIHOLE_DOMAIN=lan
DHCP_IPv6=false
DNSMASQ_LISTENING=single
PIHOLE_DNS_3=192.168.178.1
DNS_FQDN_REQUIRED=false
DNS_BOGUS_PRIV=true
DNSSEC=false
DHCP_ACTIVE=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.178.26/24
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1
IPV6_ADDRESS=fd00::40b0:9dc4:ae95:ed07
*** [ DIAGNOSING ]: Dashboard and block page
[✓] X-Pi-hole: A black hole for Internet advertisements.
[✓] X-Pi-hole: The Pi-hole Web interface is working!
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 10415138 Mar 11 10:29 /etc/pihole/gravity.list
-----head of gravity.list------
192.168.178.26 0.0.0.0
fd00::40b0:9dc4:ae95:ed07 0.0.0.0
192.168.178.26 0.r.msn.com
fd00::40b0:9dc4:ae95:ed07 0.r.msn.com
-----tail of gravity.list------
192.168.178.26 zztxdown.com
fd00::40b0:9dc4:ae95:ed07 zztxdown.com
192.168.178.26 zzz.clickbank.net
fd00::40b0:9dc4:ae95:ed07 zzz.clickbank.net
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 633 Feb 27 13:14 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt
-rw-r--r-- 1 root root 122 Mar 11 10:29 /etc/pihole/local.list
192.168.178.26 raspberrypi
fd00::40b0:9dc4:ae95:ed07 raspberrypi
192.168.178.26 pi.hole
fd00::40b0:9dc4:ae95:ed07 pi.hole
-rw-r--r-- 1 root root 234 Mar 4 16:29 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
-rw-r--r-- 1 root root 138 Mar 4 16:34 /etc/pihole/whitelist.txt
raw.githubusercontent.com
mirror1.malwaredomains.com
sysctl.org
zeustracker.abuse.ch
s3.amazonaws.com
hosts-file.net
imagesrv.adition.com
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rw-r--r-- 1 root root 1540 Mar 4 16:29 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries=extra
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=8.8.8.8
server=8.8.4.4
server=192.168.178.1
bogus-priv
interface=eth0
*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 3027 Mar 4 16:29 /etc/lighttpd/lighttpd.conf
server.modules = (
"mod_access",
"mod_accesslog",
"mod_auth",
"mod_expire",
"mod_compress",
"mod_redirect",
"mod_setenv",
"mod_rewrite"
)
server.document-root = "/var/www/html"
server.error-handler-404 = "pihole/index.php"
server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( "index.php", "index.html", "index.lighttpd.ht ml" )
url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( "application/javascript", "text/css", "text/h tml", "text/plain" )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'let sencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
$HTTP["url"] =~ "^/admin/" {
setenv.add-response-header = (
"X-Pi-hole" => "The Pi-hole Web interface is working!",
"X-Frame-Options" => "DENY"
)
$HTTP["url"] =~ ".ttf$" {
setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
}
$HTTP["url"] =~ "^/admin/\.(.*)" {
url.access-deny = ("")
}
include_shell "cat external.conf 2>/dev/null"
*** [ DIAGNOSING ]: contents of /etc/cron.d
-rw-r--r-- 1 root root 1495 Mar 4 16:29 /etc/cron.d/pihole
8 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker loc al
35 12 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remo te
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote rebo ot
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
-rw-r--r-- 1 www-data www-data 195 Mar 4 16:29 /var/log/lighttpd/error.log
2018-03-04 06:25:10: (server.c.1242) logfiles cycled UID = 0 PID = 19434
2018-03-04 16:29:23: (server.c.1558) server stopped by UID = 0 PID = 1
2018-03-04 16:29:27: (log.c.164) server started
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 3096 Mar 11 10:32 /var/log/pihole-FTL.log
[2018-03-11 00:00:02.720] Gravity list entries: 124314
[2018-03-11 00:00:02.720] No blacklist present
[2018-03-11 00:00:02.721] No wildcard blocking list present
[2018-03-11 00:00:02.724] Notice: Increasing queries struct size from 0 to 10 000 (441.25 KB)
[2018-03-11 00:00:02.725] Notice: Increasing domains struct size from 0 to 10 00 (461.25 KB)
[2018-03-11 00:00:02.726] Notice: Increasing clients struct size from 0 to 10 (461.40 KB)
[2018-03-11 00:00:02.741] New client: 192.168.178.21 (0/10)
[2018-03-11 00:00:02.742] Notice: Increasing forwarded struct size from 0 to 4 (461.50 KB)
[2018-03-11 00:00:02.757] New forward server: 192.168.178.1 (0/4)
[2018-03-11 00:00:02.758] Notice: Increasing overTime struct size from 0 to 1 00 (465.51 KB)
[2018-03-11 00:00:02.774] New client: 192.168.178.24 (1/10)
[2018-03-11 00:00:02.790] New client: 192.168.178.23 (2/10)
[2018-03-11 00:00:02.847] New forward server: 8.8.4.4 google-public-dns-b.goo gle.com (1/4)
[2018-03-11 00:00:02.867] New client: 192.168.178.69 (3/10)
[2018-03-11 00:00:02.924] New forward server: 8.8.8.8 google-public-dns-a.goo gle.com (2/4)
[2018-03-11 00:00:02.937] New client: 127.0.0.1 localhost (4/10)
[2018-03-11 00:00:02.956] New client: 192.168.178.20 (5/10)
[2018-03-11 00:00:02.983] Imported 760 queries from the long-term database
[2018-03-11 00:00:02.984] Reading from /var/log/pihole.log (rw-r--r--)
[2018-03-11 03:08:01.586] Notice: Increasing overTime struct size from 100 to 200 (476.98 KB)
[2018-03-11 03:08:31.228] NOTICE: Received signal SIGHUP - re-reading gravity files
[2018-03-11 03:08:32.539] Gravity list entries: 121059
[2018-03-11 03:08:32.540] No blacklist present
[2018-03-11 03:08:32.540] No wildcard blocking list present
[2018-03-11 03:08:32.541] -> Total DNS queries: 774
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 250288 Mar 11 10:32 /var/log/pihole.log
-----head of pihole.log------
Mar 11 00:00:02 dnsmasq[28490]: 6876 127.0.0.1/59912 query[PTR] 21.178.168.19 2.in-addr.arpa from 127.0.0.1
Mar 11 00:00:02 dnsmasq[28490]: 6876 127.0.0.1/59912 config 192.168.178.21 is NXDOMAIN
Mar 11 00:00:02 dnsmasq[28490]: 6877 127.0.0.1/38258 query[PTR] 1.178.168.192 .in-addr.arpa from 127.0.0.1
Mar 11 00:00:02 dnsmasq[28490]: 6877 127.0.0.1/38258 config 192.168.178.1 is NXDOMAIN
Mar 11 00:00:02 dnsmasq[28490]: 6878 127.0.0.1/40338 query[PTR] 24.178.168.19 2.in-addr.arpa from 127.0.0.1
Mar 11 00:00:02 dnsmasq[28490]: 6878 127.0.0.1/40338 config 192.168.178.24 is NXDOMAIN
Mar 11 00:00:02 dnsmasq[28490]: 6879 127.0.0.1/45954 query[PTR] 23.178.168.19 2.in-addr.arpa from 127.0.0.1
Mar 11 00:00:02 dnsmasq[28490]: 6879 127.0.0.1/45954 config 192.168.178.23 is NXDOMAIN
Mar 11 00:00:02 dnsmasq[28490]: 6880 127.0.0.1/44557 query[PTR] 4.4.8.8.in-ad dr.arpa from 127.0.0.1
Mar 11 00:00:02 dnsmasq[28490]: 6880 127.0.0.1/44557 forwarded 4.4.8.8.in-add r.arpa to 192.168.178.1
Mar 11 00:00:02 dnsmasq[28490]: 6880 127.0.0.1/44557 forwarded 4.4.8.8.in-add r.arpa to 8.8.4.4
Mar 11 00:00:02 dnsmasq[28490]: 6880 127.0.0.1/44557 forwarded 4.4.8.8.in-add r.arpa to 8.8.8.8
Mar 11 00:00:02 dnsmasq[28490]: 6880 127.0.0.1/44557 reply 8.8.4.4 is google- public-dns-b.google.com
Mar 11 00:00:02 dnsmasq[28490]: 6881 127.0.0.1/45536 query[PTR] 69.178.168.19 2.in-addr.arpa from 127.0.0.1
Mar 11 00:00:02 dnsmasq[28490]: 6881 127.0.0.1/45536 config 192.168.178.69 is NXDOMAIN
Mar 11 00:00:02 dnsmasq[28490]: 6882 127.0.0.1/33250 query[PTR] 8.8.8.8.in-ad dr.arpa from 127.0.0.1
Mar 11 00:00:02 dnsmasq[28490]: 6882 127.0.0.1/33250 forwarded 8.8.8.8.in-add r.arpa to 192.168.178.1
Mar 11 00:00:02 dnsmasq[28490]: 6882 127.0.0.1/33250 reply 8.8.8.8 is google- public-dns-a.google.com
Mar 11 00:00:02 dnsmasq[28490]: 6883 127.0.0.1/56132 query[PTR] 20.178.168.19 2.in-addr.arpa from 127.0.0.1
Mar 11 00:00:02 dnsmasq[28490]: 6883 127.0.0.1/56132 config 192.168.178.20 is NXDOMAIN
********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **
* The debug log can be uploaded to tricorder.pi-hole.net for sharing with de velopers only.
* For more information, see: https://pi-hole.net/2016/11/07/crack-our-medica l-tricorder-win-a-raspberry-pi-3/
* If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
[?] Would you like to upload the log? [y/N] y
* Using openssl for transmission.
***********************************
***********************************
[✓] Your debug token is: h1pytqyemg
***********************************
***********************************According to this bit, Pi-hole is blocking domains as expected.
What happens if you dig an ad domain:
dig a-ads.com @192.168.178.26
Hi Jacob!
pi@raspberrypi:~ $ dig a-ads.com @192.168.178.26
; <<>> DiG 9.9.5-9+deb8u15-Raspbian <<>> a-ads.com @192.168.178.26
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53682
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;a-ads.com. IN A
;; ANSWER SECTION:
a-ads.com. 2 IN A 192.168.178.26
;; Query time: 14 msec
;; SERVER: 192.168.178.26#53(192.168.178.26)
;; WHEN: Sat Mar 17 09:26:33 UTC 2018
;; MSG SIZE rcvd: 54This shows that your Pi-hole is indeed working as it is returning the IP of your Pi-hole.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.