# 192.168.11.166 Routing Fix

**Date**: 2026-01-22  
**Issue**: 192.168.11.166 not showing in UDM Pro because no traffic from this IP

---

## Root Cause

### Problem Identified
- **Default route**: Configured to use `eth0` (192.168.11.166)
- **Actual routing**: Uses `eth1` (192.168.11.167) for gateway
- **Result**: No traffic from 192.168.11.166 → UDM Pro doesn't see it

### Why This Happens
The kernel routing table shows:
```
default via 192.168.11.1 dev eth0
```

But when actually routing to 192.168.11.1:
```
192.168.11.1 dev eth1 src 192.168.11.167
```

The kernel prefers eth1 because it can actually reach the gateway, even though the default route says eth0.

---

## Solution

### Option 1: Fix Routing (Recommended)
Add explicit route for gateway via eth0:
```bash
ip route add 192.168.11.1 dev eth0
```

### Option 2: Generate Traffic
Force traffic from 192.168.11.166 to make UDM Pro see it:
```bash
ping -I 192.168.11.166 192.168.11.1
curl --interface 192.168.11.166 http://192.168.11.1
```

### Option 3: Remove Unused Interface
If 192.168.11.166 is not needed:
- Remove net0 from container
- Keep only net1 (192.168.11.167)

---

## Status

Fixing routing and generating traffic...

---

**Next Step**: Verify 192.168.11.166 appears in UDM Pro after traffic generation