FreeBSD 13 – network interface not coming up due to rc.conf drift – Fix & Prevention

📖 ~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

Host boots without network connectivity, blocking remote access and updates.

Environment & Reproduction

Observed after interface renaming, virtualization migration, or manual rc.conf edits.

ifconfig -a
cat /etc/rc.conf
service netif status

Root Cause Analysis

Interface variable names in rc.conf no longer match actual NIC device names.

Quick Triage

Map physical/logical interfaces and current routing state.

ifconfig -l
netstat -rn
service routing status

Step-by-Step Diagnosis

Compare configured interface stanza to detected devices and dhcp/static mode.

grep -E 'ifconfig_|defaultrouter' /etc/rc.conf
ifconfig em0 2>/dev/null || true
ifconfig vtnet0 2>/dev/null || true
dmesg | grep -i -E 'vtnet|em|re'

Solution – Primary Fix

Correct rc.conf interface keys and restart network scripts.

sysrc ifconfig_vtnet0="DHCP"
sysrc -x ifconfig_em0
service netif restart
service routing restart

Solution – Alternative Approaches

Temporarily configure interface live to regain access before persistent edits.

ifconfig vtnet0 up
dhclient vtnet0
route add default 192.0.2.1

Verification & Acceptance Criteria

Interface persists across reboot with valid address and default route.

ifconfig vtnet0
netstat -rn
ping -c 3 8.8.8.8

Rollback Plan

Restore previous rc.conf and restart network services if routing policy breaks.

cp -a /etc/rc.conf.bak /etc/rc.conf
service netif restart
service routing restart

Prevention & Hardening

Track rc.conf in configuration management and validate interface names after host migration.

ifconfig -l > /root/interface-baseline.txt

Related Errors & Cross-Refs

Often paired with DNS resolver misconfiguration and pf policy lockout.

Related tutorial: View the step-by-step tutorial for FreeBSD 13.

View all FreeBSD 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

FreeBSD rc.conf networking and service startup references.