FreeBSD 12 – Interface Renamed After Hypervisor Change and Networking Fails – Persistent Mapping

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

No network connectivity after reboot because configured interface name no longer exists.

Environment & Reproduction

Appears after VM NIC model changes or host migration.

ifconfig -l
grep -E "ifconfig_|defaultrouter" /etc/rc.conf

Root Cause Analysis

Boot scripts reference stale interface identifiers and skip address configuration.

Quick Triage

List active interfaces and compare with rc.conf definitions.

Step-by-Step Diagnosis

Review boot logs for DHCP/static assignment failures.

dmesg | grep -Ei "em|igb|ix|vtnet"
service netif onestatus

Solution – Primary Fix

Update /etc/rc.conf to the correct interface and restart networking.

vi /etc/rc.conf
service netif restart
service routing restart

Solution – Alternative Approaches

Use cloned interface abstraction or automation templates keyed by MAC address.

Verification & Acceptance Criteria

Interface receives expected IP and default route is present.

ifconfig 
netstat -rn | head -n 30

Rollback Plan

Restore previous rc.conf and activate known-good interface values from console.

Prevention & Hardening

Document interface naming assumptions and validate after hypervisor changes.

Related Errors & Cross-Refs

ifconfig: interface does not exist, no carrier, failed to configure network.

Related tutorial: View the step-by-step tutorial for freebsd-12.

View all freebsd-12 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

rc.conf(5), ifconfig(8), and FreeBSD network initialization references.