Device lacks an existing IP assignment when it switches to a new network connection.
Device lacks an existing IP assignment when it switches to a new network connection.
Hi, I see you're experiencing similar issues with your Raspberry Pi and server. Let me try to clarify what might be going on. First, with your Raspberry Pi acting as a pihole, after reinstalling it, the DHCP reservation IP got claimed by an unknown device that wasn't listed in your router settings. You couldn't ping it or remove it from the dropdown. Then, with your server, you upgraded the NIC to a new Ethernet port and found the reserved IP was taken by a device named "MSI WINDOWS XP"—which seems odd since you don’t have that OS installed and it wasn’t in use beyond a VM. Even after resetting the router, these non-existent devices kept showing up. It’s possible some other system is interfering or misconfiguring your network settings.
Typically, the router allows you to release an IP address from a device and then assign it to another. If you perform a factory reset with no connections—wired or wireless—you should be able to set up the reservation. Are you using Docker containers or virtual machines on any of your systems? If the network interface is in bridge mode, VMs or containers can obtain IP addresses directly from your router. This might explain the reference to "MSI WINDOWS XP"...
When you set aside addresses, pick them beyond the DHCP server's range, or else they might be assigned to other devices when the correct one isn't available. For example, in this case the DHCP pool runs from .100 to .249, so for static reservations I place them under .100.