Sounds like two network managers (from screenshots) fighting over control of the interfaces:
Better kill network-manager and let dhcpcd5 configure IP etc:
@deHakkelaar Thanks for the response!
I got this when running pi
pi@Pihole:~ $ sudo service network-manager status
Unit network-manager.service could not be found.
pi@Pihole:~ $ sudo service dhcpcd status
dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-01-01 00:03:19 PST; 12h ago
Main PID: 328 (dhcpcd)
Memory: 1.3M
CGroup: /system.slice/dhcpcd.service
└─328 /sbin/dhcpcd -q -b
Jan 01 01:06:58 Pihole dhcpcd[328]: eth0: pid 328 deleted default route via 192.168.0.10
Jan 01 01:07:04 Pihole dhcpcd[328]: eth0: failed to request information
Jan 01 01:07:08 Pihole dhcpcd[328]: eth0: Router Advertisement from fe80::d66e:eff:fe42:4048
Jan 01 01:07:08 Pihole dhcpcd[328]: eth0: fe80::d66e:eff:fe42:4048: no longer a default router
Jan 01 01:07:08 Pihole dhcpcd[328]: eth0: deleting default route via fe80::d66e:eff:fe42:4048
Jan 01 01:07:10 Pihole dhcpcd[328]: eth0: Router Advertisement from fe80::d66e:eff:fe42:4048
Jan 01 01:07:10 Pihole dhcpcd[328]: eth0: adding default route via fe80::d66e:eff:fe42:4048
Jan 01 12:02:35 Pihole dhcpcd[328]: eth0: fe80::d66e:eff:fe42:4048 is reachable again
Jan 01 12:11:02 Pihole dhcpcd[328]: eth0: fe80::d66e:eff:fe42:4048 is reachable again
Jan 01 12:11:02 Pihole dhcpcd[328]: eth0: fe80::d66e:eff:fe42:4048 is reachable again
It seems like my network manager cannot be found?
Thats probably due to dhcpcd5 also being "Active: active" fiddling with the interfaces:
sudo service dhcpcd status
You have to decide which one to keep (or remove them both but bit more work).
EDIT: I wouold disable network-manager as Pi-hole comes with dhcpcd5
What does these thing mean exactly?
pi@Pihole:~ $ sudo service dhcpcd5 status
● dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-01-01 00:03:19 PST; 13h ago
Main PID: 328 (dhcpcd)
Memory: 1.2M
CGroup: /system.slice/dhcpcd.service
└─328 /sbin/dhcpcd -q -b
Jan 01 01:06:58 Pihole dhcpcd[328]: eth0: pid 328 deleted default route via 192.168.0.10
Jan 01 01:07:04 Pihole dhcpcd[328]: eth0: failed to request information
Jan 01 01:07:08 Pihole dhcpcd[328]: eth0: Router Advertisement from fe80::d66e:eff:fe42:4048
Jan 01 01:07:08 Pihole dhcpcd[328]: eth0: fe80::d66e:eff:fe42:4048: no longer a default router
Jan 01 01:07:08 Pihole dhcpcd[328]: eth0: deleting default route via fe80::d66e:eff:fe42:4048
Jan 01 01:07:10 Pihole dhcpcd[328]: eth0: Router Advertisement from fe80::d66e:eff:fe42:4048
Jan 01 01:07:10 Pihole dhcpcd[328]: eth0: adding default route via fe80::d66e:eff:fe42:4048
Jan 01 12:02:35 Pihole dhcpcd[328]: eth0: fe80::d66e:eff:fe42:4048 is reachable again
Jan 01 12:11:02 Pihole dhcpcd[328]: eth0: fe80::d66e:eff:fe42:4048 is reachable again
Jan 01 12:11:02 Pihole dhcpcd[328]: eth0: fe80::d66e:eff:fe42:4048 is reachable again
EDIT: oops mistake hold on!
network-manager is not active:
haha no worries, thank you for your help I appreciate it!
I'm a little lost on these network things.. Trying to learn more and get better at it.
pi@Pihole:~ $ systemctl stop NetworkManager.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to stop 'NetworkManager.service'.
Multiple identities can be used for authentication:
1. ,,, (pi)
2. root
Choose identity to authenticate as (1-2): 1
Password:
==== AUTHENTICATION COMPLETE ===
Failed to stop NetworkManager.service: Unit NetworkManager.service not loaded.
And below ?
sudo service NetworkManager.service status
I believe that's it
pi@Pihole:~ $ sudo service NetworkManager.service status
Unit NetworkManager.service.service could not be found.
pi@Pihole:~ $ systemctl status NetworkManager.service
Unit NetworkManager.service could not be found.
I think we have to go back a step.
I was assuming two network managers screwing things up but it seems not.
So back to the issue, the gateway not responding.
IP 192.168.0.189 or 192.168.0.10 as a gateway seems a bit odd.
Shouldn't your router IP be the gateway address to get on the internet ?
Router IP is probably 192.168.0.1.
I believe you can reconfigure IP settings with Pi-hole through dhcpcd5 by running below and select reconfigure:
pihole -r
traceroute -n 8.8.8.8
ip r
???
pi@Pihole:~ $ traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.0.10 0.492 ms 0.499 ms 0.477 ms
2 10.72.32.1 6.207 ms 10.912 ms 10.594 ms
3 68.4.12.128 11.064 ms 10.747 ms 10.384 ms
4 100.120.104.0 11.547 ms 11.233 ms 10.867 ms
5 68.1.1.167 10.815 ms 68.1.1.171 10.583 ms 14.712 ms
6 72.14.242.92 14.714 ms 72.14.196.240 14.702 ms 72.215.224.175 13.335 ms
7 * 108.170.247.225 14.603 ms 11.200 ms
8 8.8.8.8 10.897 ms 15.672 ms 14.981 ms
pi@Pihole:~ $ ip r
pi@Pihole:~ $ ip r
default via 192.168.0.10 dev eth0 proto dhcp src 192.168.0.190 metric 203
192.168.0.0/16 dev eth0 proto dhcp scope link src 192.168.0.190 metric 203
Here's the new token https://tricorder.pi-hole.net/hc8sy1fko4
I'm not even sure if my LAN is suppose to be on that IP.. This makes me wants to wipe my router or factory reset it.(probably my last option)
Edit:
There's also this page..
Looks good.
What if you run below one on a client device (Win/Mac/Linux):
nslookup pi.hole 192.168.0.190
And without the Pi-hole address on a client ?
nslookup pi.hole
And did gravity update already ?
nc localhost 4711 <<< $'>stats'
If domains_being_blocked still zero, try run below to run gravity:
pihole -g
And remove the 8.8.8.8 Secondary DNS address on the router or ads will still leak through!
Ps. if you change DHCP settings, you have to disconnect and reconnect client devices for the new settings to propagate!
1 Like
Locs-MacBook-Pro-2:~ LocNguyen$ nslookup pi.hole 192.168.0.190
Server: 192.168.0.190
Address: 192.168.0.190#53
Name: pi.hole
Address: 192.168.0.190
Locs-MacBook-Pro-2:~ LocNguyen$ nslookup pi.hole
Server: 192.168.0.190
Address: 192.168.0.190#53
Name: pi.hole
Address: 192.168.0.190
Locs-MacBook-Pro-2:~ LocNguyen$ nc localhost 4711 <<< $'>stats'
Locs-MacBook-Pro-2:~ LocNguyen$ echo ">stats" | nc localhost 4711
Locs-MacBook-Pro-2:~ LocNguyen$ curl -i http://pi.hole/admin/api.php
HTTP/1.1 200 OK
Content-type: application/json
Set-Cookie: PHPSESSID=glr9r31l2vsp4avssfcunpq4h3; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-Pi-hole: The Pi-hole Web interface is working!
X-Frame-Options: DENY
Content-Length: 484
Date: Wed, 01 Jan 2020 21:49:21 GMT
Server: lighttpd/1.4.53
{"domains_being_blocked":113661,"dns_queries_today":53714,"ads_blocked_today":797,"ads_percentage_today":1.483784,"unique_domains":1466,"queries_forwarded":26457,"queries_cached":26460,"clients_ever_seen":11,"unique_clients":11,"dns_queries_all_types":53714,"reply_NODATA":126,"reply_NXDOMAIN":9,"reply_CNAME":743,"reply_IP":436,"privacy_level":0,"status":"enabled","gravity_last_updated":{"file_exists":true,"absolute":1577867058,"relative":{"days":"0","hours":"13","minutes":"25"}}}Locs-MacBook
You know what's the craziest part? it sometimes work like
Locs-MacBook-Pro-2:~ LocNguyen$ nslookup flurry.com
Server: 192.168.0.190
Address: 192.168.0.190#53
Name: flurry.com
Address: 0.0.0.0
Sorry, the last two commands from previous posting should be run on Pi-hole.
Thats probably because of the secondary DNS IP address 8.8.8.8.
I see should I set second DNS as 190.168.0.189?
no worries man, you're helping me a lot! I'm also learning a bunch 
No.
If the router firmware doesnt allow you to leave this field empty, try put in the same IP 192.168.0.190 twice.
I realized when testing that nslookup flurry.com I had my dns manually set on my mac.
Sorry for the confusion
now running it
Locs-MacBook-Pro-2:~ LocNguyen$ nslookup flurry.com
Server: 2001:578:3f::30
Address: 2001:578:3f::30#53
Non-authoritative answer:
Name: flurry.com
Address: 212.82.100.153
Name: flurry.com
Address: 98.136.103.26
Name: flurry.com
Address: 74.6.136.153
This is the pi
pi@Pihole:~ $ nslookup flurry.com
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: flurry.com
Address: 0.0.0.0
Name: flurry.com
This is my mac DNS settings automatically. I dont know what those two other IP are I really want them out of here...
