//nbkelley /homelab

OPNsense Interface Reassignment & NIC Troubleshooting#

What Was Established#

Procedures for reassigning WAN/LAN interfaces via the OPNsense console following a system upgrade, and troubleshooting connectivity loss after a physical NIC replacement.

Key Decisions#

  • Console-Based Reassignment: Use the OPNsense console menu (1. Assign Interfaces) to map physical ports to WAN/LAN roles.
  • Network-Only Reset: If configuration is lost, use 2. Reset to factory defaults and select “Reset only the network configuration” to preserve other settings.
  • Manual Config Edit: Fallback to vi /conf/config.xml to manually adjust <interfaces> tags (<wan>, <lan>) if the menu fails.
  • NIC Troubleshooting Workflow: Verify driver recognition (vmstat -i), link status (ifconfig), and system logs (dmesg). Check NAT/Outbound and LAN firewall rules. Isolate hardware issues by reverting to the original NIC.

Current Configuration#

  • Gateway: UCG Express “Olorín” (OPNsense) at 192.168.1.1.
  • VLANs: Gandalf (192.168.1.x), Mithrandir (192.168.2.x), Tharkûn (192.168.3.x), Rivendell (192.168.4.x).
  • Switch: Netgear MS308E (trunk/access VLANs managed via OPNsense).

Historical Notes#

  • Procedures documented for OPNsense upgrades where interface assignments reset.
  • Troubleshooting steps refined for scenarios involving physical NIC swaps (e.g., 2.5GbE to 1GbE) causing interface loss.
  • Note: Driver support (Intel igb/em, Realtek) and firmware updates may be required for newer NICs.

Open Questions#

  • Specific driver requirements for the current UCG Express “Olorín” gateway NICs.
  • Automation of interface reassignment to prevent manual console steps during future upgrades.

Sources#

  • ingested/chats/034-Reassign WAN and LAN on OPNsense Post-Upgrade.md
  • Historical DeepSeek conversation on OPNsense console interface reassignment and NIC troubleshooting.
Backward UniFi UX7 & Netgear MS308E VLAN Setup OPNsense DHCP Configuration Forward