Expected Behaviour:
Pihole should blocking ads and run without problems and internet cut off.
Actual Behaviour:
Internet conncetion after 30-40 minutes after launch cuts off. I think it's my router's fault TP-LINK Archer v6 V2.0, because after rebooting everything works fine until next 30min.
Debug Token:
https://tricorder.pi-hole.net/va5FHAMW/
Please elaborate on the problem.
The Pi-hole host platform is losing its connection to the LAN? Or is your router losing connection to the internet?
Of note in your debug log - 4 DHCP servers are active (or perhaps just three, the first two may be duplicates):
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 300 bytes from eth0:192.168.0.132
Offered IP address: 192.168.0.112
Server IP address: N/A
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.0.132
lease-time: 86400 ( 1d )
netmask: 255.255.255.0
router: 192.168.0.132
dns-server: 192.168.0.34
dns-server: 8.8.8.8
--- end of options ---
* Received 300 bytes from eth0:192.168.0.132
Offered IP address: 192.168.0.112
Server IP address: N/A
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.0.132
lease-time: 86400 ( 1d )
netmask: 255.255.255.0
router: 192.168.0.132
dns-server: 192.168.0.34
dns-server: 8.8.8.8
--- end of options ---
* Received 300 bytes from eth0:192.168.0.3
Offered IP address: 192.168.0.124
Server IP address: 192.168.0.3
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.0.3
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
broadcast: 192.168.0.255
dns-server: 192.168.0.34
dns-server: 8.8.8.8
router: 192.168.0.3
--- end of options ---
* Received 300 bytes from eth0:192.168.0.1
Offered IP address: 192.168.0.123
Server IP address: 192.168.0.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.0.1
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
broadcast: 192.168.0.255
dns-server: 192.168.0.34
dns-server: 8.8.8.8
router: 192.168.0.1
--- end of options ---
DHCP packets received on interface eth0: 4
Why do you have so many active DHCP servers?
And, you should not have your DHCP server(s) offering Google as a DNS server. Pi-hole should be the only DNS server available to clients.
Yes, i use pi-hole on ethernet cable.
I changed DHCP servers for only pi-hole, maybe it will help.
New debug token: https://tricorder.pi-hole.net/goQfkhHW/
You still have the same 4 DHCP servers showing in your debug log.
Please answer my previous questions. This makes it easier to help you.
It's running from LAN. Without pihole it is working without problem
I have 1 router and 2 access points.
Now i changed it, but still i have the problem
Your Pi is able to connect to the router? Yes or no.
The router is connected to the internet? Yes or no.
From the Pi terminal, what are the outputs of the following:
nslookup pi-hole.net
ping -C3 8.8.8.8
yes
yes
server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: pi-hole.net Address: 3.18.136.52
it shows all commands for ping
-p contents of padding byte -q quiet output -Q use quality of service bits -s use as number of data bytes to be sent -S use as SO_SNDBUF socket option value -t define time to live -U print user-to-user latency -v verbose output -V print version and exit -w reply wait in seconds -W time to wait for response IPv4 options: -4 use IPv4 -b allow pinging broadcast -R record route -T define timestamp, can be one of <tsonly|tsandaddr|tsprespec> IPv6 options: -6 use IPv6 -F define flow label, default is random -N use icmp6 node info query, try as argument For more details see ping(8)
My mistake. This should be:
ping -c3 8.8.8.8
this ping is when internet works fine
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=2.82 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=2.93 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=2.89 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 2.822/2.880/2.933/0.045 ms
I also have debug token when internet doesn't work. Maybe it will help https://tricorder.pi-hole.net/aQ2cD9im/
But can it generate a link without internet connection? I think that it's not routers fault, because pihole have the connection and generates this debug link, when other devices doesn't have connection.
I found out that i can ping IPs directly from my router. When i pinged 8.8.8.8 it responded, but when i tried to do it from CMD in Windows it didn't responded.
The problem appears to lie in that Windows client or your router.
When you ping an IP directly, there is no DNS resolution involved, and Pi-hole is not part of the transaction.
If the Windows client cannot ping the IP, there is a connectivity problem between the client and the destination IP.
But my access points and phones, also dont have connection.
Another indication that you have a router problem.
I know but what is the cause? I searched all router dns settings and i've set it to pihole dns or turned them off
I don't know. I have zero knowledge of your network configuration, hardware, software, clients, modem, etc.
You will need to visit the networking forums and forums for your router and modem to figure out why your specific network is having problems.
This is not a Pi-hole problem. The problem lies in your network.
Thanks for your advices. I have few more questions: Should I disable DHCP server on access points and enable it only on main router or enable on all of it?
In what cases should I use Pi-Hole DHCP server?
You want a single DHCP server on your network. That should be the router or Pi-hole, but not both.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.