# IP Conflict Found - CRITICAL

**Date**: 2026-01-21  
**Status**: ⚠️ **CRITICAL IP CONFLICT DETECTED**

---

## IP Conflict: 192.168.11.167

### Two Containers Using Same IP

| VMID | Host | Hostname | IP Address | Interface | Status |
|------|------|----------|------------|-----------|--------|
| **10233** | r630-01 | npmplus | 192.168.11.167 | eth1 (net1) | ✅ Running |
| **10234** | r630-02 | ? | 192.168.11.167 | ? | ? |

---

## Impact

**Critical Network Issue:**
- Both containers claim the same IP address (192.168.11.167)
- Network routing conflicts will occur
- Only one container can properly receive traffic
- UDM Pro may see conflicting MAC addresses
- This explains connectivity issues

---

## Investigation

Checking VMID 10234 details...

---

## Resolution Required

One of these containers must be reassigned to a different IP address.

**Recommendation:**
- Keep VMID 10233 (npmplus) on 192.168.11.167 (it's actively being used)
- Reassign VMID 10234 to a different IP address

---

**Status**: ⚠️ **CRITICAL - RESOLUTION REQUIRED**