# IP Conflict - CRITICAL ISSUE

**Date**: 2026-01-21  
**Status**: ⚠️ **CRITICAL - TWO CONTAINERS USING SAME IP**

---

## IP Conflict: 192.168.11.167

### Both Containers Are Running and Active

| VMID | Host | Hostname | IP Address | Interface | MAC Address | Status |
|------|------|----------|------------|-----------|-------------|--------|
| **10233** | r630-01 | npmplus | 192.168.11.167 | eth1 (net1) | BC:24:11:A8:C1:5D | ✅ Running |
| **10234** | r630-02 | npmplus-secondary | 192.168.11.167 | eth0 (net0) | **BC:24:11:8D:EC:B7** | ✅ Running |

---

## Critical Discovery

### UDM Pro MAC Address Match

**UDM Pro shows**: `bc:24:11:8d:ec:b7` for "NPMplus dot 167"  
**VMID 10234 MAC**: `BC:24:11:8D:EC:B7` ✅ **MATCHES**

**This means:**
- UDM Pro is seeing **VMID 10234** (npmplus-secondary) on r630-02
- NOT VMID 10233 (npmplus) on r630-01
- Traffic intended for npmplus may be going to the wrong container!

---

## Impact

### Network Routing Conflicts

1. **Both containers claim same IP**: 192.168.11.167
2. **Both are running**: Both have the IP active
3. **MAC address conflict**: UDM Pro sees VMID 10234's MAC
4. **Traffic routing**: Traffic may be going to wrong container
5. **Connectivity issues**: Explains why NPMplus is inconsistent

### Why This Causes Problems

- ARP table conflicts (which MAC responds?)
- UDM Pro port forwarding may target wrong container
- Network traffic split between two containers
- Service availability unpredictable

---

## Resolution

### Option 1: Reassign VMID 10234 (Recommended)

**VMID 10234** (npmplus-secondary) should be reassigned to a different IP.

**Recommended IP**: `192.168.11.168` (next available)

**Steps:**
1. Stop VMID 10234
2. Change IP from 192.168.11.167 to 192.168.11.168
3. Restart container
4. Verify no conflicts

### Option 2: Remove VMID 10234 IP

If npmplus-secondary is not needed:
1. Stop VMID 10234
2. Remove IP assignment
3. Keep container for other purposes

---

## Verification After Fix

After reassigning VMID 10234:

```bash
# Verify no conflicts
# Check r630-01
pct config 10233 | grep 192.168.11.167

# Check r630-02
pct config 10234 | grep 192.168.11.168

# Verify UDM Pro sees correct MAC
# Should see BC:24:11:A8:C1:5D for 192.168.11.167
```

---

## Summary

**Status**: ⚠️ **CRITICAL IP CONFLICT**

**Conflict**: Two containers using 192.168.11.167
- VMID 10233 (npmplus) on r630-01
- VMID 10234 (npmplus-secondary) on r630-02

**UDM Pro is seeing**: VMID 10234 (wrong container!)

**Action Required**: Reassign VMID 10234 to different IP (192.168.11.168)

---

**Next Step**: Fix IP conflict by reassigning VMID 10234