76 lines
1.8 KiB
Markdown
76 lines
1.8 KiB
Markdown
# 192.168.11.166 Not Showing in UDM Pro
|
|
|
|
**Date**: 2026-01-22
|
|
**Issue**: 192.168.11.166 is not appearing as a client in UDM Pro
|
|
|
|
---
|
|
|
|
## Current UDM Pro Client Status
|
|
|
|
### ✅ Visible Clients
|
|
- **192.168.11.167**: MAC `bc:24:11:a8:c1:5d` (VMID 10233, eth1)
|
|
- Connection: UDM Pro Port 2
|
|
- Status: Active
|
|
- Uptime: 3d 22h 37m 33s
|
|
|
|
- **192.168.11.168**: MAC `bc:24:11:8d:ec:b7` (VMID 10234, eth0)
|
|
- Connection: Not specified
|
|
- Status: Active
|
|
- Uptime: Jan 22 2026 1:36 PM
|
|
|
|
### ❌ Missing Client
|
|
- **192.168.11.166**: MAC `BC:24:11:18:1C:5D` (VMID 10233, eth0)
|
|
- **Not visible in UDM Pro**
|
|
|
|
---
|
|
|
|
## Analysis
|
|
|
|
### Possible Reasons
|
|
|
|
1. **No Traffic from 192.168.11.166**
|
|
- Interface may be configured but not actively used
|
|
- Default route may use eth1 (192.168.11.167) instead
|
|
- No outbound traffic from this IP
|
|
|
|
2. **Interface Not Routing**
|
|
- eth0 may not be the primary interface
|
|
- Gateway may be configured only on eth1
|
|
- Routing table may prefer eth1
|
|
|
|
3. **UDM Pro Not Seeing ARP**
|
|
- No ARP requests from 192.168.11.166
|
|
- Interface may be passive
|
|
- No network activity on this IP
|
|
|
|
---
|
|
|
|
## Investigation
|
|
|
|
Checking container configuration and routing...
|
|
|
|
---
|
|
|
|
## Resolution Options
|
|
|
|
### Option 1: Generate Traffic from 192.168.11.166
|
|
Force traffic from this IP to make UDM Pro see it:
|
|
- Ping gateway from 192.168.11.166
|
|
- Make HTTP request from this IP
|
|
- Generate ARP traffic
|
|
|
|
### Option 2: Verify Interface is Active
|
|
Ensure eth0 is actively routing traffic:
|
|
- Check default route uses eth0
|
|
- Verify gateway is reachable from eth0
|
|
- Test connectivity from this IP
|
|
|
|
### Option 3: Remove Unused Interface (if not needed)
|
|
If 192.168.11.166 is not needed:
|
|
- Remove net0 interface
|
|
- Keep only net1 (192.168.11.167)
|
|
|
|
---
|
|
|
|
**Status**: Investigation in progress...
|