That would depend on your chosen OS.
But your recent ping results suggest an issue with IPv4 Internet connectivty.
What kind of Internet connection does your ISP provide?
Run from your RPi, what's the result of:
ping -c 3 8.8.8.8
That would depend on your chosen OS.
I use the latest 64 bit version (based on Debian 12.5).
According to https://linuxconfig.org/how-to-enable-disable-firewall-on-raspberry-pi nftables is installed by default. It doesn't seem to be running at the moment:
sudo systemctl status nftables.service
○ nftables.service - nftables
Loaded: loaded (/lib/systemd/system/nftables.service; disabled; preset: enabled)
Active: inactive (dead)
Docs: man:nft(8)
http://wiki.nftables.org
I have cable internet.
ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.2.201 icmp_seq=1 Destination Host Unreachable
From 192.168.2.201 icmp_seq=2 Destination Host Unreachable
From 192.168.2.201 icmp_seq=3 Destination Host Unreachable
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2034ms
pipe 3
Your Internet connection seems to be IPv6 only.
You'd need to consult your ISP and/or your router's documentation on how to configure IPv4 connectivity with your router.
I just tried something that seems to have solved the problem.
Until now, my RPi had a static IP. I switched it back to dynamic, and now I can ping 8.8.8.8 again.
ping -c 3 8.8.8.8
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=117 time=6.31 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=4.38 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=117 time=4.35 ms
Pi-hole is installing again...
I have no idea why my modem doesn't like me to set static IPs to my devices, but there it is.
Thank you so much for your patience, I learned some very useful troubleshooting tricks thanks to you.
... I don't think I'm out of the woods yet.
So, I have a RPi with a dynamic address assigned by my modem (192.168.2.175).
I can ping 8.8.8.8, everything's back to normal.
Next thing I need to do before installing pi-hole is assign a static address to the RPi. We've already established that enabling this from the router itself was a bad idea, so I'm using this method:
sudo apt install dhcpcd5
Which creates dhcpcd.conf
Then:
sudo nano -w /etc/dhcpcd.conf
I scroll down then add these lines:
# Example static IP configuration:
interface eth0
static ip_address=192.168.2.201/24
# static ip6_address=fd51:42f8:caae:d92e::ff/64
static routers=192.168.2.1
static domain_name_servers=192.168.2.1 1.1.1.1
192.168.2.201 is the IP I want to assign to my RPi. It is outside the range of IP addresses that the modem can assign to other devices on the local network.
192.168.2.1 is the modem's IP address.
After saving these changes and rebooting the RPi, I'm able to ssh using 192.168.2.201 (instead of 192.168.2.175, which is the dynamic address assigned to the RPi by the router).
... then I get this:
ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2048ms
So yep, I still have work to do, it seems.
Your earliest resolv.conf already suggested that NetworkManager is your OS's network configuration tool. nmcli and nmtui are the CLI tools used to configure NM.
By installing another such tool, dhcpcd, you've probably created conflicts among that and NM.
I'd recommend to disable one of them, but this really isn't a Pi-hole issue.
You should consider to also consult forums specialising in Raspberry Pi networking.
This right here, This was the key.
That let me set my device IP, gateway, DNS. Traffing is flowing through the RPi now.
Thank you so much.
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.