Setup help pihole and tp link router, some devices no internet.

Hi guys, i have a Pi 3b set up with diet pi and running the latest release of pi hole. Its connected via eth to my tp link vr900 router. However it is only semi working on most devices.

So my connected devices via cable seem to function fine. Browse the web and so forth. And apparently show on the clients list for pihole. There are some query’s but not as many as i would have thought and my test site (speedtest.net), when previously used with a virtual machine of pi hole, managed to block all adds. Not now.

And my wifi devices all on a 2.4ghz network setting at the moment ( issues with a security camera ive yet to fix). Android devices like my phone and tablet tell me im connected but have no internet.

Second i remove the dns setting in the router config page. Normal internet traffic resumes. Im kinda stumped.

This process collects information from your Pi-hole, and optionally uploads it to 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 small 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 can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2020-02-19:11:47:59 debug log has been initialized.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v4.3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.2-0-ge41c4b5

*** [ DIAGNOSING ]: Web version
[i] Web: v4.3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.3-0-g62f2ffc

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.3.1

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.53

*** [ DIAGNOSING ]: php version
[i] 7.3.14

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 10 (buster)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
[✓] armv7l

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.1.102/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
   fe80::ba27:ebff:fe5e:629 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.1.1
   * Pinging 192.168.1.1...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
*:22 dropbear (IPv4)
*:22 dropbear (IPv6)
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
[*:53] is in use by pihole-FTL
[*:53] is in use by pihole-FTL
[127.0.0.1:4711] is in use by pihole-FTL
[[::1]:4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] admaster.de is 0.0.0.0 via localhost (127.0.0.1)
[✓] admaster.de is 0.0.0.0 via Pi-hole (192.168.1.102)
[✓] doubleclick.com is 172.217.169.78 via a remote, public DNS server (8.8.8.8)

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

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.1.102/24
    IPV6_ADDRESS=
    QUERY_LOGGING=false
    INSTALL_WEB_SERVER=false
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    BLOCKING_ENABLED=true
    DNSMASQ_LISTENING=single
    PIHOLE_DNS_1=8.8.8.8
    PIHOLE_DNS_2=8.8.4.4
    PIHOLE_DNS_3=192.168.1.102#53
    DNS_FQDN_REQUIRED=true
    DNS_BOGUS_PRIV=true
    DNSSEC=false
    CONDITIONAL_FORWARDING=false

*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 403 Forbidden
Content-Type: text/html
Content-Length: 341
Date: Wed, 19 Feb 2020 11:48:07 GMT
Server: lighttpd/1.4.53

[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 2907085 Feb 19 00:47 /etc/pihole/gravity.list
   -----head of gravity.list------
   0.0.0.0
   0.nextyourcontent.com
   0.r.msn.com
   0.start.bz

   -----tail of gravity.list------
   zzz.clickbank.net
   zzzezeroe.fr
   zzzpooeaz-france.com
   zzzrtrcm2.com

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r--r-- 1 root root 313 Feb 19 00:44 /etc/pihole/adlists.list
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   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 43 Feb 19 00:47 /etc/pihole/local.list
   192.168.1.102 DietPi
   192.168.1.102 pi.hole

-rw-r--r-- 1 root root 234 Feb 19 00:45 /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
   }

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r--r-- 1 root root 1437 Feb 19 11:39 /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-facility=/var/log/pihole.log
   local-ttl=2
   log-async
   server=8.8.8.8
   server=8.8.4.4
   server=192.168.1.102
   domain-needed
   bogus-priv
   interface=eth0

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 2053 Feb 19 00:46 /etc/lighttpd/lighttpd.conf
   server.modules = (
   	"mod_indexfile",
   	"mod_setenv",
   	"mod_access",
   	"mod_alias",
    	"mod_redirect",
   )
   server.document-root        = "/var/www"
   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
   server.http-parseopts = (
     "header-strict"           => "enable",
     "host-strict"             => "enable",
     "host-normalize"          => "enable",
     "url-normalize-unreserved"=> "enable",
     "url-normalize-required"  => "enable",
     "url-ctrls-reject"        => "enable",
     "url-path-2f-decode"      => "enable",
    
     "url-path-dotseg-remove"  => "enable",
    
    
   )
   index-file.names            = ( "index.php", "index.html" )
   url.access-deny             = ( "~", ".inc" )
   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.conf.pl"
   include "/etc/lighttpd/conf-enabled/*.conf"
   server.modules += (
   	"mod_compress",
   	"mod_dirlisting",
   	"mod_staticfile",
   )

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r--r-- 1 root root 1704 Feb 19 00:45 /etc/cron.d/pihole
   54 3   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
   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
   30 18  * * *   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 0 Feb 19 01:17 /var/log/lighttpd/error.log

*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 8708 Feb 19 11:39 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2020-02-19 11:18:36.116 1718] Resizing "/FTL-strings" from 4096 to 8192
   [2020-02-19 11:22:54.551 1718] Resizing "/FTL-queries" from 196608 to 393216
   [2020-02-19 11:35:36.670 1718] Shutting down...
   [2020-02-19 11:35:36.673 1718] Finished final database update
   [2020-02-19 11:35:36.675 1718] ########## FTL terminated after 38411456.0 ms! ##########
   [2020-02-19 11:35:37.180 8071] Using log file /var/log/pihole-FTL.log
   [2020-02-19 11:35:37.181 8071] ########## FTL started! ##########
   [2020-02-19 11:35:37.181 8071] FTL branch: master
   [2020-02-19 11:35:37.181 8071] FTL version: v4.3.1
   [2020-02-19 11:35:37.181 8071] FTL commit: b60d63f
   [2020-02-19 11:35:37.181 8071] FTL date: 2019-05-25 21:37:26 +0200
   [2020-02-19 11:35:37.181 8071] FTL user: pihole
   [2020-02-19 11:35:37.181 8071] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2020-02-19 11:35:37.181 8071]    SOCKET_LISTENING: only local
   [2020-02-19 11:35:37.181 8071]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2020-02-19 11:35:37.181 8071]    MAXDBDAYS: max age for stored queries is 365 days
   [2020-02-19 11:35:37.181 8071]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2020-02-19 11:35:37.181 8071]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2020-02-19 11:35:37.182 8071]    DBINTERVAL: saving to DB file every minute
   [2020-02-19 11:35:37.182 8071]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2020-02-19 11:35:37.182 8071]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2020-02-19 11:35:37.182 8071]    PRIVACYLEVEL: Set to 0
   [2020-02-19 11:35:37.182 8071]    IGNORE_LOCALHOST: Show queries from localhost
   [2020-02-19 11:35:37.182 8071]    BLOCKINGMODE: Null IPs for blocked domains
   [2020-02-19 11:35:37.182 8071]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
   [2020-02-19 11:35:37.182 8071]    DBIMPORT: Importing history from database
   [2020-02-19 11:35:37.182 8071]    PIDFILE: Using /var/run/pihole-FTL.pid
   [2020-02-19 11:35:37.182 8071]    PORTFILE: Using /var/run/pihole-FTL.port
   [2020-02-19 11:35:37.183 8071]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2020-02-19 11:35:37.183 8071]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2020-02-19 11:35:37.183 8071]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2020-02-19 11:35:37.183 8071]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2020-02-19 11:35:37.183 8071]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2020-02-19 11:35:37.183 8071]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2020-02-19 11:35:37.183 8071]    AUDITLISTFILE: Using /etc/pihole/auditlog.list

   -----tail of pihole-FTL.log------
   [2020-02-19 11:39:42.263 8419]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2020-02-19 11:39:42.263 8419]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2020-02-19 11:39:42.264 8419]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2020-02-19 11:39:42.264 8419]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2020-02-19 11:39:42.264 8419]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2020-02-19 11:39:42.264 8419]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2020-02-19 11:39:42.264 8419]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2020-02-19 11:39:42.264 8419]    MACVENDORDB: Using /etc/pihole/macvendor.db
   [2020-02-19 11:39:42.264 8419]    PARSE_ARP_CACHE: Active
   [2020-02-19 11:39:42.264 8419] Finished config file parsing
   [2020-02-19 11:39:42.267 8419] Database version is 3
   [2020-02-19 11:39:42.267 8419] Database successfully initialized
   [2020-02-19 11:39:42.268 8419] New forward server: 8.8.4.4 (0/512)
   [2020-02-19 11:39:42.269 8419] New forward server: 8.8.8.8 (1/512)
   [2020-02-19 11:39:42.311 8419] Resizing "/FTL-strings" from 4096 to 8192
   [2020-02-19 11:39:42.345 8419] Resizing "/FTL-queries" from 196608 to 393216
   [2020-02-19 11:39:42.363 8419] Imported 5085 queries from the long-term database
   [2020-02-19 11:39:42.364 8419]  -> Total DNS queries: 5085
   [2020-02-19 11:39:42.364 8419]  -> Cached DNS queries: 3393
   [2020-02-19 11:39:42.364 8419]  -> Forwarded DNS queries: 1525
   [2020-02-19 11:39:42.364 8419]  -> Exactly blocked DNS queries: 167
   [2020-02-19 11:39:42.364 8419]  -> Unknown DNS queries: 0
   [2020-02-19 11:39:42.364 8419]  -> Unique domains: 211
   [2020-02-19 11:39:42.364 8419]  -> Unique clients: 13
   [2020-02-19 11:39:42.364 8419]  -> Known forward destinations: 2
   [2020-02-19 11:39:42.365 8419] Successfully accessed setupVars.conf
   [2020-02-19 11:39:42.373 8421] PID of FTL process: 8421
   [2020-02-19 11:39:42.373 8421] Listening on port 4711 for incoming IPv4 telnet connections
   [2020-02-19 11:39:42.374 8421] Listening on port 4711 for incoming IPv6 telnet connections
   [2020-02-19 11:39:42.374 8421] Listening on Unix socket
   [2020-02-19 11:39:42.376 8421] Received SIGHUP, reloading cache
   [2020-02-19 11:39:42.376 8421] Blocking status is enabled
   [2020-02-19 11:39:42.376 8421] INFO: No whitelist file found
   [2020-02-19 11:39:42.376 8421] Compiled 0 Regex filters and 0 whitelisted domains in 0.2 msec (0 errors)
   [2020-02-19 11:39:44.587 8421] /etc/pihole/gravity.list: parsed 125296 domains (took 2209.4 ms)

*** [ DIAGNOSING ]: contents of /dev/shm
-rw------- 1 pihole pihole 323584 Feb 19 11:39 /dev/shm/FTL-clients
-rw------- 1 pihole pihole 108 Feb 19 11:39 /dev/shm/FTL-counters
-rw------- 1 pihole pihole 65536 Feb 19 11:39 /dev/shm/FTL-domains
-rw------- 1 pihole pihole 12288 Feb 19 11:39 /dev/shm/FTL-forwarded
-rw------- 1 pihole pihole 28 Feb 19 11:39 /dev/shm/FTL-lock
-rw------- 1 pihole pihole 53248 Feb 19 11:39 /dev/shm/FTL-overTime
-rw------- 1 pihole pihole 393216 Feb 19 11:43 /dev/shm/FTL-queries
-rw------- 1 pihole pihole 12 Feb 19 11:39 /dev/shm/FTL-settings
-rw------- 1 pihole pihole 8192 Feb 19 11:39 /dev/shm/FTL-strings

*** [ DIAGNOSING ]: Locale
    LANG=

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 1589 Feb 19 11:39 /var/log/pihole.log
   -----head of pihole.log------
   Feb 19 11:35:36 dnsmasq[1718]: exiting on receipt of SIGTERM
   Feb 19 11:35:37 dnsmasq[8073]: started, version pi-hole-2.80 cachesize 10000
   Feb 19 11:35:37 dnsmasq[8073]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify dumpfile
   Feb 19 11:35:37 dnsmasq[8073]: using nameserver 8.8.4.4#53
   Feb 19 11:35:37 dnsmasq[8073]: using nameserver 8.8.8.8#53
   Feb 19 11:35:37 dnsmasq[8073]: read /etc/hosts - 5 addresses
   Feb 19 11:35:37 dnsmasq[8073]: read /etc/pihole/local.list - 2 addresses
   Feb 19 11:35:37 dnsmasq[8073]: failed to load names from /etc/pihole/black.list: No such file or directory
   Feb 19 11:35:39 dnsmasq[8073]: read /etc/pihole/gravity.list - 125296 addresses
   Feb 19 11:39:40 dnsmasq[8073]: exiting on receipt of SIGTERM
   Feb 19 11:39:42 dnsmasq[8421]: started, version pi-hole-2.80 cachesize 10000
   Feb 19 11:39:42 dnsmasq[8421]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify dumpfile
   Feb 19 11:39:42 dnsmasq[8421]: ignoring nameserver 192.168.1.102 - local interface
   Feb 19 11:39:42 dnsmasq[8421]: using nameserver 8.8.4.4#53
   Feb 19 11:39:42 dnsmasq[8421]: using nameserver 8.8.8.8#53
   Feb 19 11:39:42 dnsmasq[8421]: read /etc/hosts - 5 addresses
   Feb 19 11:39:42 dnsmasq[8421]: read /etc/pihole/local.list - 2 addresses
   Feb 19 11:39:42 dnsmasq[8421]: failed to load names from /etc/pihole/black.list: No such file or directory
   Feb 19 11:39:44 dnsmasq[8421]: read /etc/pihole/gravity.list - 125296 addresses


********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **

    * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
    * For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
    * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
[i] Debug script running in automated mode
    * Using curl for transmission.

***********************************
***********************************
[✓] Your debug token is: https://tricorder.pi-hole.net/32s89f93fm
***********************************
***********************************

   * Provide the token above to the Pi-hole team for assistance at
   * https://discourse.pi-hole.net
   * Your log will self-destruct on our server after 48 hours.
   * A local copy of the debug log can be found at: /var/log/pihole_debug.log![1|581x500](upload://kW69xq4CbxuEOLmeV4HZUNKtRGf.jpeg) 

You’ve created a DNS loop.
You should not configure Pi-hole’s own IP address as an upstream DNS server/resolver or most DNS queries would just endlessly loop and loop and loop and loop back to Pi-hole :wink:

http://pi.hole/admin/settings.php?tab=dns

so what would i change to make it effective network wide without manually

changing it on every device ?

The screen capture you posted is the Pi-Hole upstream DNS server page, which does not affect the network use of Pi-Hole. You are using the Google DNS Servers as upstream servers, which will work fine. Let’s check that these are the only DNS Servers in the setupVars.conf file:

grep PIHOLE_DNS /etc/pihole/setupVars.conf

EDIT: I was just to post below @jfb :wink:

Setup router as described in below FAQ (methods 1 or 2):

Disconnect client(s) from network and reconnect.
Check what DNS server(s) is/are assigned to the clients via the router DHCP service.
On Linux/MacOS clients run below:

cat /etc/resolv.conf

Or if Linux network-manager is installed, check profiles:

nmcli connection show --active

nmcli connection show <UUID> | grep -i dns

Or on Windows clients:

ipconfig /all | findstr "Server"

Or on Android clients if have the “Terminal Emulator” app installed:

getprop net.dns1

getprop net.dns2

getprop net.dns3

Only one DNS server IP should be configured on the clients, the Pi-hole IP address.
If any others are listed, ads will leak through via those other DNS servers.

I saw you said you were having an issue with your security camera. Where you able to get it running? I am new to Pi and pi hole and am having issues with one camera. I have SimplySafe with 2 security cameras that are working fine but i cannot get the doorbell camera to connect at all to the network. I can’t even get it to show up anywhere. Its acting as if it is unplugged.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.