Raspberry Pi Getting Multiple IP Addresses: DHCP Conflicts

A Raspberry Pi displaying multiple IP addresses usually indicates a DHCP conflict where the device has obtained leases from more than one network source, such as both Ethernet and Wi-Fi. This issue often arises when NetworkManager or dhcpcd manages interfaces simultaneously without proper precedence rules. Resolving this requires identifying active services, verifying interface configurations in /etc/network/interfaces or NetworkManager profiles, and ensuring only the desired connection type is enabled for IP assignment to restore stable connectivity.

Identifying Active Network Services

The first step in troubleshooting multiple IP addresses on a Raspberry Pi OS is determining which service is currently managing your network interfaces. Modern versions of Raspberry Pi OS (Bullseye and Bookworm) use NetworkManager by default, whereas older versions relied on dhcpcd5. Conflicts occur when both services are running or when configuration files contradict each other. You can check the status of these services using the systemctl command. Run systemctl status NetworkManager and systemctl status dhcpcd to see if they are active. If both are running, you may have overlapping management responsibilities. It is generally recommended to stick with one manager to avoid race conditions during IP assignment. Check the output carefully; an inactive service might still hold a lease if it was not stopped cleanly.

Checking Interface Configuration Files

Once you know which service is active, inspect the configuration files that define how each interface behaves. For dhcpcd, the primary configuration file is /etc/dhcpcd.conf. Look for entries that assign static IPs or override DHCP settings for interfaces like eth0 or wlan0. If you are using NetworkManager, the configurations are stored in /etc/NetworkManager/system-connections/ or managed via the nmcli tool. A common cause of duplicate IPs is having a static IP configured in one system while another service attempts to assign a dynamic address via DHCP. Review these files to ensure consistency. If you find conflicting directives, comment out or remove the redundant lines. Ensure that the interface you intend to use is set to acquire an address automatically unless a specific static setup is required.

Verifying Physical and Virtual Interfaces

Sometimes the issue is not software configuration but rather unexpected physical connections. A Raspberry Pi might connect to two networks simultaneously if both Ethernet and Wi-Fi are active. This creates a situation where the device receives an IP from the local router via Ethernet and potentially another from a different source if Wi-Fi is also connected. Use the ip addr show command to list all assigned addresses. Identify which interface holds which IP. If you see multiple IPv4 addresses on the same interface, it suggests a lease renewal issue or a misconfigured static entry. If you see addresses on both eth0 and wlan0, decide which connection should be primary. Disable the unused interface temporarily to isolate the problem. This helps determine if the conflict is internal to a single interface or between different network paths.

Resolving Lease Conflicts

After identifying the correct service and interface, you need to clear any stale DHCP leases that might be causing the duplication. Leases are typically stored in /var/lib/dhcpcd/ for dhcpcd or in NetworkManager's state files. Stop the active network service before clearing these files to prevent immediate reassignment. For dhcpcd, you can delete the lease files associated with the problematic interface. Restart the service afterward to force a fresh request to the DHCP server. If using NetworkManager, you can restart the service or use nmtui to toggle the connection off and on. This process ensures that the device negotiates a new, unique IP address from the DHCP server. Verify the new address with ip addr to confirm only one valid IP is present.

Preventing Future Conflicts

To prevent recurring issues, establish a clear hierarchy for network management. If you choose NetworkManager, disable dhcpcd entirely by running sudo systemctl disable --now dhcpcd. Conversely, if you prefer the simplicity of dhcpcd, stop and disable NetworkManager. Do not run both unless you have advanced knowledge of their interaction. Additionally, consider assigning a static IP within the DHCP range of your router if the device serves a critical function, such as a server. This reduces reliance on dynamic assignment. Refer to guides on configuring static IPs for deeper insights into stable network setups. Regularly monitor your network status after changes to ensure stability. Consistent configuration management prevents the ambiguity that leads to multiple IP assignments.

Frequently Asked Questions

How do I know if my Raspberry Pi is using NetworkManager or dhcpcd?

Run systemctl is-active NetworkManager and systemctl is-active dhcpcd. The service returning "active" is currently managing your network interfaces. Most recent Raspberry Pi OS images default to NetworkManager.

Can I have both Ethernet and Wi-Fi active at the same time?

Yes, but it can lead to routing conflicts if not configured correctly. Both interfaces may receive IP addresses, causing the system to choose the wrong gateway for traffic. It is best practice to disable one interface if you do not need simultaneous connections.

What happens if I don't stop the service before deleting lease files?

The service might immediately recreate the lease or overwrite your changes, leading to persistent conflicts. Stopping the service ensures a clean slate for the next boot or restart sequence.

Is it safe to disable dhcpcd on newer Raspberry Pi OS versions?

Yes, because NetworkManager is the default and fully supported manager in modern releases. Disabling dhcpcd prevents conflicts with NetworkManager's automatic handling of connections.

How can I check if a specific IP is already in use by another device?

Use the arp-scan tool or check your router's DHCP client list. If another device holds the IP you want to assign statically, you must choose a different address to avoid collisions.