I messed up with remote logins and had to reboot.
(So ignore the previous question. Though confirming how it is done would be handy.)
Rebooted.
Now I'm seeing
interface eth0 does not currently exist
Yeah, there is a link, but to cover all bases.
As the warning says. Likely caused by an interface=NAME option where the interface NAME does not exist. Check if your operating system may have changed from simple (like eth0) to predictable (like enp2s0) interface names. Update your configuration accordingly.
Not as far as I know. I haven't changed any interface names.
https://tricorder.pi-hole.net/Wyk08BDw/
slight update - though in the wrong direction:
Now I'm seeing:
Though I suspect there may be a problem somewhere, as the network PiHole is on has it's own DHCP server, and DNS server.
Digging into the second problem:
Handing out addresses used by known critical infrastructure (like the DHCP server or a relay) is prevented to avoid IP address duplication issues.
This can happen when you have configured a static address assignment for the IP address of your Pi-hole. As this could result in an IP address conflict, Pi-hole offers a different free address from your configured DHCP pool. As this means Pi-hole behaves differently than you configured it to, it issues a warning.
The solution would be to either remove the static reservation for the Pi-hole itself (see ADDRESS in the warning) or simply accept this warning as it should only happen during debug log generation. When this warning appears outside of a running DHCP test, check that your Pi-hole is indeed using a static address.
Ok, I kind of get the meaning, but not all.
PiHole is .23 in my network can if I try to change it (NOT via PiHole) I can't.
The interface GUI is blocked. Don't know if I should be worried or not.
Just mentioning.
So that made it really hard to just move the device (here after called PiHole) to the temporary network, as it had different IP addresses and so PiHole wouldn't work on the new network.
So I had to build an entire Duplicate network so PiHole could be accessed from this machine.
It is given .23 here too.
So it isn't using a different IP address.
What is written kind of implies there is an IP problem.
THOUGH this could be tied in with the interface eth0 does not currently exist problem.
(But if so: why can I see the pages and SSH into it?
This is the network layout (working):
nmap -sP 192.168.17.0/24
Starting Nmap 7.80 ( https://nmap.org ) at 2025-06-07 07:37 AEST
Nmap scan report for EdgeRouter (192.168.17.1)
Host is up (0.0010s latency).
Nmap scan report for NUC (192.168.17.6)
Host is up (0.000087s latency).
Nmap scan report for BedPi (192.168.17.23)
Host is up (0.00063s latency).
Nmap scan report for me-desktop (192.168.17.133)
Host is up (0.00012s latency).
Nmap done: 256 IP addresses (4 hosts up) scanned in 2.36 seconds
And PiHole (AKA BedPi) is on .23
