explorer-monorepo/192.168.11.166_SOLUTION.md

192.168.11.166 Not in UDM Pro - Solution

Date: 2026-01-22
Issue: 192.168.11.166 not appearing in UDM Pro client list

---

Root Cause Analysis

Problem

• 192.168.11.166 (eth0) is configured but generates no traffic
• 192.168.11.167 (eth1) is actively used for all routing
• UDM Pro only sees devices that generate network traffic

Why No Traffic from 192.168.11.166?

1. Default route: Says to use eth0 (192.168.11.166)
2. Actual routing: Kernel uses eth1 (192.168.11.167) because:
   • eth0 cannot reach gateway (100% packet loss)
   • eth1 can reach gateway successfully
   • Kernel automatically prefers working interface

Result

• All traffic goes out via 192.168.11.167
• No traffic from 192.168.11.166
• UDM Pro never sees ARP requests from 192.168.11.166
• Therefore, 192.168.11.166 doesn't appear in client list

---

Current Status in UDM Pro

✅ Visible Clients

• 192.168.11.167: MAC bc:24:11:a8:c1:5d ✅ Active
• 192.168.11.168: MAC bc:24:11:8d:ec:b7 ✅ Active

❌ Missing Client

• 192.168.11.166: MAC BC:24:11:18:1C:5D ❌ Not visible (no traffic)

---

Solutions

Option 1: Generate Traffic (Temporary Visibility)

Force traffic from 192.168.11.166 to make UDM Pro see it:

# This will generate ARP requests
ping -I 192.168.11.166 192.168.11.1

Note: This only makes it visible temporarily. If no traffic continues, it will disappear again.

Option 2: Fix eth0 Connectivity (If Needed)

If you need 192.168.11.166 to work:

1. Check ARP cache for gateway on eth0
2. Verify gateway responds to eth0
3. Fix routing if needed

Option 3: Remove Unused Interface (Recommended)

If 192.168.11.166 is not needed:

• Remove net0 from container
• Keep only net1 (192.168.11.167)
• This simplifies configuration

---

Recommendation

Since 192.168.11.167 is working and all traffic uses it:

• Option 3 is recommended: Remove 192.168.11.166 if not needed
• If you need both IPs, fix eth0 connectivity first

If you just want UDM Pro to see it:

• Generate traffic periodically (not practical long-term)
• Or accept that it won't show if it's not used

---

Summary

Status: 192.168.11.166 is configured but not generating traffic

Reason: Kernel routes via eth1 (192.168.11.167) because eth0 cannot reach gateway

Solution:

• Remove unused interface (recommended)
• Or fix eth0 connectivity if needed
• Or generate periodic traffic (temporary visibility only)

---

Action: Decide if 192.168.11.166 is needed, then either fix it or remove it