chaoy
January 25, 2021, 6:03am
1
Expected Behaviour:
When editing DNS forwardings on my router, it should block ads on my network. I'm using a TP-Link A7 AC1750 flashed with OpenWRT 19.07.5
Actual Behaviour:
When I replace the DNS with my Pi's IP, it kills all internet traffic on my router. Whats strange, and why I think its possible its my router, is that when I manually set my iPhone's DNS to the Pi's IP, everything works mostly as expected. I have tried googling/ checking the forums but I haven't found anything so far that has helped.
Debug Token:
https://tricorder.pi-hole.net/h7gvwuy591
It seems like your Pi has connectivity issues
192.168.2.1
* Pinging 192.168.2.1
192.168.2.1...
[✗] Gateway did not respond.
Do you block Port 53 on your network?
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)
Your router advertises itself via DHCP as DNS server on eth0
and wlan0
*** [ 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.2.1
Offered IP address: 192.168.2.127
Server IP address: 192.168.2.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.2.1
lease-time: 120 ( 2m )
renewal-time: 60 ( 1m )
rebinding-time: 105 ( 1m 45s )
netmask: 255.255.255.0
broadcast: 192.168.2.255
router: 192.168.2.1
dns-server: 192.168.2.1
* Received 310 bytes from wlan0:192.168.2.1
Offered IP address: 192.168.2.128
Server IP address: 192.168.2.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.2.1
lease-time: 120 ( 2m )
renewal-time: 60 ( 1m )
rebinding-time: 105 ( 1m 45s )
netmask: 255.255.255.0
broadcast: 192.168.2.255
router: 192.168.2.1
dns-server: 192.168.2.1
domain-name: "lan"
hostname: "raspberrypi"
--- end of options ---
What's the output of
echo ">top-clients >quit" | nc localhost 4711
chaoy
January 25, 2021, 9:38pm
3
It was indeed the router. Port 53 was being used for an older DNS project I had. I turned it off and it worked great.
system
Closed
February 15, 2021, 9:39pm
4
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.