- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
3.7 KiB
VLAN 11 Dual IP Configuration - Complete
Last Updated: 2026-01-15
Status: ✅ CONFIGURED
Configuration Summary
Current Setup
- System: WSL2 (Ubuntu 24.04.3 LTS)
- Primary Interface: eth0
- IP Addresses:
- ✅ 192.168.0.4/24 (Default network - preserved)
- ✅ 192.168.11.23/24 (VLAN 11 - added)
Network Access
Default Network (192.168.0.0/24):
- ✅ UDM Pro: 192.168.0.1
- ✅ Other devices on Default network
VLAN 11 (192.168.11.0/24):
- ✅ Gateway: 192.168.11.1
- ✅ ml110: 192.168.11.10
- ✅ r630-01: 192.168.11.11
- ✅ r630-02: 192.168.11.12
Configuration Commands Used
# Add VLAN 11 IP address
sudo ip addr add 192.168.11.23/24 dev eth0
# Add route to VLAN 11 network (route already existed - this is fine)
sudo ip route add 192.168.11.0/24 dev eth0 src 192.168.11.23
Note: The "File exists" error for the route is normal - it means the route was already configured.
Verification
Check IP Addresses
ip addr show eth0 | grep "inet "
Expected Output:
inet 192.168.0.4/24 ... (Default network)
inet 192.168.11.23/24 ... (VLAN 11)
Check Routes
ip route show | grep "192.168"
Expected Output:
192.168.0.0/24 dev eth0 ...
192.168.11.0/24 dev eth0 src 192.168.11.23 ...
Test Connectivity
# Default network
ping -c 3 192.168.0.1 # UDM Pro
# VLAN 11
ping -c 3 192.168.11.1 # VLAN 11 gateway
ping -c 3 192.168.11.10 # ml110
ping -c 3 192.168.11.11 # r630-01
ping -c 3 192.168.11.12 # r630-02
Persistence (WSL2)
Since this is WSL2, the IP configuration will be lost on reboot. To make it persistent:
Option 1: Auto-Configuration on Login
./scripts/unifi/add-vlan11-ip-to-bashrc.sh
This adds the configuration to ~/.bashrc so it runs automatically on each login.
Option 2: Manual Addition to ~/.bashrc
Add this to the end of ~/.bashrc:
# Auto-configure VLAN 11 secondary IP
if [ -n "$(ip link show eth0 2>/dev/null)" ] && ! ip addr show eth0 | grep -q "192.168.11.23"; then
sudo ip addr add 192.168.11.23/24 dev eth0 2>/dev/null || true
sudo ip route add 192.168.11.0/24 dev eth0 src 192.168.11.23 2>/dev/null || true
fi
Benefits
With dual IP configuration:
-
Access to Default Network:
- UDM Pro web UI (192.168.0.1)
- Devices on 192.168.0.0/24
- Internet access (if configured)
-
Access to VLAN 11:
- Proxmox hosts (192.168.11.10-12)
- Services on VLAN 11
- Management of VLAN 11 resources
-
Dual Network Access:
- No need to switch networks
- Access both simultaneously
- Best of both worlds
Troubleshooting
Issue: Route "File exists" Error
Status: ✅ This is normal!
The route already exists, which means it was configured previously. This is fine - no action needed.
Issue: IP Address Not Showing
Check:
ip addr show eth0 | grep "192.168.11.23"
If not found, add it:
sudo ip addr add 192.168.11.23/24 dev eth0
Issue: Cannot Reach VLAN 11 Hosts
Check:
- Verify IP is configured:
ip addr show eth0 | grep "192.168.11.23" - Verify route exists:
ip route show | grep "192.168.11" - Test gateway:
ping 192.168.11.1 - Check firewall rules on target hosts
Summary
Status: ✅ CONFIGURED AND WORKING
Configuration:
- ✅ Dual IP addresses configured
- ✅ Routes configured
- ✅ Both networks accessible
Next Steps:
- ✅ Configuration complete
- ⏳ Add to ~/.bashrc for persistence (optional)
- ✅ Ready to use both networks
You now have:
- Access to Default network (192.168.0.0/24)
- Access to VLAN 11 (192.168.11.0/24)
- Both networks working simultaneously
Last Updated: 2026-01-15