explorer-monorepo/IP_CONFLICTS_FIXED.md

IP Conflicts Fixed - Complete Report

Date: 2026-01-22
Status: ✅ ALL IP CONFLICTS RESOLVED

---

IP Conflicts Fixed

✅ Conflict 1: 192.168.11.46 - RESOLVED

Before:

• VMID 10020 (order-redis): 192.168.11.46
• VMID 10200 (order-prometheus): 192.168.11.46 ⚠️ CONFLICT

After:

• VMID 10020 (order-redis): 192.168.11.47 ✅
• VMID 10200 (order-prometheus): 192.168.11.46 ✅

Action Taken:

• Stopped VMID 10020
• Reassigned from 192.168.11.46 to 192.168.11.47
• Restarted container
• Verified new IP is active

---

✅ Conflict 2: 192.168.11.112 - RESOLVED

Before:

• VMID 108 (vault-rpc-translator): 192.168.11.112
• VMID 6000 (fabric-1): 192.168.11.112 ⚠️ CONFLICT

After:

• VMID 108 (vault-rpc-translator): 192.168.11.112 ✅
• VMID 6000 (fabric-1): 192.168.11.113 ✅

Action Taken:

• Stopped VMID 6000
• Reassigned from 192.168.11.112 to 192.168.11.113
• Restarted container
• Verified new IP is active

---

ARP Refresh

Traffic Generated From:

• ✅ VMID 10020 (192.168.11.47) - New IP
• ✅ VMID 6000 (192.168.11.113) - New IP
• ✅ VMID 10200 (192.168.11.46) - Now unique
• ✅ VMID 108 (192.168.11.112) - Now unique

Purpose: Refresh ARP tables in UDM Pro and network devices

---

Verification

IP Conflict Check

• ✅ No containers using 192.168.11.46 (except VMID 10200)
• ✅ No containers using 192.168.11.112 (except VMID 108)
• ✅ 192.168.11.47 assigned to VMID 10020 only
• ✅ 192.168.11.113 assigned to VMID 6000 only

---

Summary

Status: ✅ ALL IP CONFLICTS RESOLVED

Changes Made:

1. ✅ VMID 10020: 192.168.11.46 → 192.168.11.47
2. ✅ VMID 6000: 192.168.11.112 → 192.168.11.113

ARP Refresh:

• ✅ Traffic generated from all affected containers
• ✅ UDM Pro should update client list within 30-60 seconds

Next Steps:

• Verify UDM Pro client list shows correct IPs
• Test connectivity to reassigned containers
• Monitor for any remaining conflicts

---

Action: All IP conflicts resolved, ARP entries refreshed