# Critical Issues Found - UDM Pro Client Analysis

**Date**: 2026-01-22  
**Status**: ⚠️ **CRITICAL IP CONFLICTS DETECTED**

---

## 🚨 CRITICAL: IP Conflicts Found

### Conflict 1: 192.168.11.46 ⚠️ **CRITICAL**
**Two containers using same IP:**
- **VMID 10020**: order-redis
- **VMID 10200**: order-prometheus

**Impact**: Network routing conflicts, only one can receive traffic

### Conflict 2: 192.168.11.112 ⚠️ **CRITICAL**
**Two containers using same IP:**
- **VMID 108**: vault-rpc-translator
- **VMID 6000**: fabric-1

**Impact**: Network routing conflicts, only one can receive traffic

---

## ⚠️ Missing Client in UDM Pro

### Missing: 192.168.11.31
- **VMID 104**: gitea (on r630-01)
- **Status**: Configured but not visible in UDM Pro
- **Possible causes**:
  - Container not running
  - Interface not active
  - No traffic generated

---

## ⚠️ Containers with Missing Connection Info

These containers are in UDM Pro but show no connection/network info:

1. **192.168.11.26**: VMID 105 (nginxproxymanager)
   - MAC: bc:24:11:71:6a:78
   - No connection info

2. **192.168.11.33**: VMID 101 (proxmox-datacenter-manager)
   - MAC: bc:24:11:ad:a7:28
   - No connection info

3. **192.168.11.112**: VMID 108 or 6000 (CONFLICT - see above)
   - MAC: bc:24:11:7b:db:97
   - No connection info

4. **192.168.11.168**: VMID 10234 (npmplus-secondary)
   - MAC: bc:24:11:8d:ec:b7
   - No connection info (recently moved IP)

5. **192.168.11.201**: Need to identify
   - MAC: bc:24:11:da:a1:7f
   - No connection info

---

## Summary

### ✅ Good News
- Most containers are visible and working
- No duplicate MAC addresses
- Physical servers correctly identified

### 🚨 Critical Issues
- **2 IP conflicts** need immediate resolution
- **1 missing client** (gitea) needs investigation
- **5 containers** with missing connection info

---

## Recommended Actions

### Priority 1: Fix IP Conflicts (URGENT)
1. **192.168.11.46**: Reassign one container (order-redis or order-prometheus)
2. **192.168.11.112**: Reassign one container (vault-rpc-translator or fabric-1)

### Priority 2: Investigate Missing Client
1. Check if VMID 104 (gitea) is running
2. Verify interface is active
3. Generate traffic if needed

### Priority 3: Fix Missing Connection Info
1. Check container status
2. Verify interfaces are active
3. Generate traffic to refresh ARP

---

**Status**: ⚠️ **CRITICAL - IP CONFLICTS REQUIRE IMMEDIATE ATTENTION**