Could you provide a source for that?
NetworkManager
's documentation would list explicit properties for addressN
, gateway
and dns
, see Table 5. ipv4 setting (section).
Could you provide a source for that?
NetworkManager
's documentation would list explicit properties for addressN
, gateway
and dns
, see Table 5. ipv4 setting (section).
Uhm... I'll look for it, this time I just copied my nmconnection configuration, but I found that way of describing the gateway somewhere when I configured my rpi a few month ago.
I did as you suggested, using nmtui
to set a static address. Pi-Hole still has the original error, but now I get this result from running a command you previously provided:
zed1@raspberrypi:~ $ dig @9.9.9.9 tricorder.pi-hole.net
; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> @9.9.9.9 tricorder.pi-hole.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51629
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;tricorder.pi-hole.net. IN A
;; ANSWER SECTION:
tricorder.pi-hole.net. 60 IN CNAME docker-2-ny1.pi-hole.net.
docker-2-ny1.pi-hole.net. 3600 IN A 164.90.255.4
;; Query time: 31 msec
;; SERVER: 9.9.9.9#53(9.9.9.9) (UDP)
;; WHEN: Fri Nov 22 20:59:33 GMT 2024
;; MSG SIZE rcvd: 93
zed1@raspberrypi:~ $
That demonstrates that your machine knows how to forward packets to public IPs now.
You could verify your IPv4 gateway by running:
ip route
sudo grep -A6 ipv4 /etc/NetworkManager/system-connections/BT-2RFJW3.nmconnection
For the latter, you may have to look for the correct .nmconnection file, as NM
may have changed the name for your connection.
Did you get rid of dnsmasq
yet?
Also, please provide a fresh debug token.
I ran the commands - see below. The directory to the .nmonnection file looks fine (visually checked against File Explorer in the Pi). I've just got rid of dnsmasq
.
zed1@raspberrypi:~ $ ip route
default via 192.168.1.254 dev wlan0 proto static metric 600
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.111 metric 600
zed1@raspberrypi:~ $ grep -A6 ipv4 /etc/NetworkManager/system-connections/BT-2RF JW3.nmconnection
grep: /etc/NetworkManager/system-connections/BT-2RFJW3.nmconnection: Permission denied
I restarted Pi-hole, it is now active, however there are some fresh errors in the log. It appears to be working though - I've set my laptop to use Pi-hole for DNS, and it's all good. Debug token is https://tricorder.pi-hole.net/5l7cAHbv/
It seems uninstalling dnsmasq
has removed the configuration directory:
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
/etc/dnsmasq.d does not exist.
As Pi-hole's embedded pihole-FTL
is a tailored dnsmasq
fork, it needs that directory.
Try running pihole -r
with Repair.
Thank you very much, all errors are now resolved.