# DHCP：检测到192.168.1.100地址冲突，正在禁用接口eth0

- **ID:** `networking/dhcp-address-conflict`
- **领域:** networking
- **类别:** network_error
- **验证级别:** ai_generated
- **修复率:** 85%

## 根因

DHCP客户端收到IP地址的ACK后，通过ARP探测发现另一台主机正在使用相同IP，导致客户端释放该地址并禁用接口以避免IP冲突。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| ISC DHCP client 4.4-4.5 | active | — | — |
| systemd-networkd 250-256 | active | — | — |
| dhcpcd 9.4-10.0 | active | — | — |
| Linux kernel 5.15-6.8 | active | — | — |
| Windows 10/11 DHCP client | active | — | — |

## 解决方案

1. ```
   Release and request a new IP: `dhclient -r eth0; dhclient eth0` to get a different address from the pool.
   ```
2. ```
   Identify the conflicting host by checking ARP table: `arp -a | grep 192.168.1.100` and remove it from the network, or exclude that IP from the DHCP pool on the server.
   ```
3. ```
   Configure a DHCP reservation on the server for the client's MAC address to ensure it always gets the same IP and avoid conflicts.
   ```

## 无效尝试

- **Setting a static IP on the client without checking the DHCP pool** — The static IP may still conflict with the DHCP server's pool, leading to the same error or network instability. (80% 失败率)
- **Restarting the DHCP client repeatedly (e.g., `dhclient -r && dhclient`)** — The conflicting host is still on the network; the same IP may be reassigned, causing immediate conflict again. (85% 失败率)
- **Ignoring the error and assuming it's a one-time glitch** — The interface remains disabled, so the client has no network connectivity until manually re-enabled. (95% 失败率)