# UDM Pro Client List Analysis

**Date**: 2026-01-22  
**Total Clients**: 29  
**Status**: Analyzing for conflicts and issues

---

## Client Inventory

### Physical Servers
- **192.168.11.10**: ml110 (HPE) - Port 5
- **192.168.11.11**: r630-01 (Dell) - Port 2
- **192.168.11.12**: r630-02 (Dell) - Port 3

### Other Devices
- **192.168.11.23**: ASERET d0:9a (Others) - Port 8 - **ACTIVE** (3.47 GB)

### Proxmox Containers (Proxmox Server Solutions GmbH)

#### Low IP Range (26-35)
- **192.168.11.26**: bc:24:11:71:6a:78 - No connection info
- **192.168.11.27**: bc:24:11:e5:90:97 - Port 2
- **192.168.11.28**: bc:24:11:dc:02:89 - Port 2
- **192.168.11.29**: bc:24:11:a9:6a:ac - Port 2
- **192.168.11.30**: bc:24:11:96:35:30 - Port 2
- **192.168.11.32**: bc:24:11:3f:a2:b0 - Port 2
- **192.168.11.33**: bc:24:11:ad:a7:28 - No connection info
- **192.168.11.34**: bc:24:11:2e:d9:aa - Port 2 - **ACTIVE** (68.5 MB)
- **192.168.11.35**: bc:24:11:8f:0b:84 - Port 3 - **ACTIVE** (2.89 GB)

#### Mid Range (53-63)
- **192.168.11.53**: bc:24:11:ad:45:64 - Port 2
- **192.168.11.57**: bc:24:11:a7:74:23 - Port 3 - **ACTIVE** (2.34 GB)
- **192.168.11.61**: bc:24:11:c5:f0:71 - Port 2
- **192.168.11.62**: bc:24:11:c5:2c:34 - Port 2
- **192.168.11.63**: bc:24:11:43:ab:31 - Port 2

#### High Range (112-240)
- **192.168.11.112**: bc:24:11:7b:db:97 - No connection info
- **192.168.11.140**: bc:24:11:3c:58:2b - Port 3 - **ACTIVE** (205 MB)
- **192.168.11.166**: bc:24:11:a8:c1:5d - Port 2 (MAC swapped)
- **192.168.11.167**: bc:24:11:18:1c:5d - Port 2 (MAC swapped) - **ACTIVE** (55.5 MB)
- **192.168.11.168**: bc:24:11:8d:ec:b7 - No connection info
- **192.168.11.200**: bc:24:11:f2:4f:d4 - Port 2
- **192.168.11.201**: bc:24:11:da:a1:7f - No connection info
- **192.168.11.202**: bc:24:11:e4:bd:63 - Port 2
- **192.168.11.240**: bc:24:11:aa:d7:31 - Port 5 - **ACTIVE** (58.6 MB)

### Unknown/Incomplete Entries
- **No IP**: bc:24:11:af:52:dc - Port 5 - No IP assigned
- **No IP**: ILO---P 43:cb (HPE) - No IP assigned

---

## Issues Identified

### ⚠️ Issue 1: Missing Connection Info
Several Proxmox containers show no connection/network info:
- 192.168.11.26 (bc:24:11:71:6a:78)
- 192.168.11.33 (bc:24:11:ad:a7:28)
- 192.168.11.112 (bc:24:11:7b:db:97)
- 192.168.11.168 (bc:24:11:8d:ec:b7)
- 192.168.11.201 (bc:24:11:da:a1:7f)

**Possible causes**:
- Containers not generating traffic
- ARP not resolved
- Interface not active

### ⚠️ Issue 2: MAC Address Swap (Known)
- 192.168.11.166 → MAC bc:24:11:a8:c1:5d (should be 18:1c:5d)
- 192.168.11.167 → MAC bc:24:11:18:1c:5d (should be a8:c1:5d)

**Status**: Known issue, will self-correct

### ⚠️ Issue 3: Missing IP Addresses
- bc:24:11:af:52:dc - No IP assigned
- ILO---P 43:cb - No IP assigned (HP iLO?)

**Possible causes**:
- DHCP not assigning IP
- Static IP not configured
- Device not fully connected

### ⚠️ Issue 4: Missing IP 192.168.11.31
**Gap in IP range**: 192.168.11.30 → 192.168.11.32

**Question**: Is 192.168.11.31 supposed to be assigned?

---

## Active Containers (With Traffic)

1. **192.168.11.35**: 2.89 GB (Port 3)
2. **192.168.11.57**: 2.34 GB (Port 3)
3. **192.168.11.34**: 68.5 MB (Port 2)
4. **192.168.11.140**: 205 MB (Port 3)
5. **192.168.11.167**: 55.5 MB (Port 2)
6. **192.168.11.240**: 58.6 MB (Port 5)

---

## Next Steps

1. **Verify Container IPs**: Cross-reference with Proxmox container configs
2. **Check Missing Connection Info**: Investigate why some containers show no connection
3. **Resolve Missing IPs**: Check why some devices have no IP
4. **Verify IP Gaps**: Check if 192.168.11.31 should exist

---

**Status**: Analysis complete - checking against Proxmox configs...