π ~1 min read
Table of contents
Symptom & Impact
Server boots without expected network, breaking remote access and services.
Environment & Reproduction
Common after virtual hardware changes or driver updates.
ifconfig -l
cat /etc/rc.conf | grep ifconfig
Root Cause Analysis
rc.conf binds IP settings to an interface name that changed.
Quick Triage
Identify current interface names and test temporary DHCP/static assignment.
ifconfig
dhclient
Step-by-Step Diagnosis
Compare saved rc.conf entries with current device inventory and logs.
dmesg | egrep 'em|igb|ix|vtnet'
grep -n 'ifconfig_' /etc/rc.conf

Solution – Primary Fix
Update interface keys in rc.conf and restart netif/routing services.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
sysrc ifconfig_vtnet0='inet 10.0.0.20/24'
service netif restart
service routing restart

Solution – Alternative Approaches
Use bridge/VLAN abstraction so service IPs are less tied to raw NIC names.
Verification & Acceptance Criteria
Expected IP and default route are present and reachable.
ifconfig vtnet0
netstat -rn
Rollback Plan
Restore previous rc.conf from backup and apply temporary rescue network config.
Prevention & Hardening
Track interface naming in change plans and validate post-reboot connectivity checks.
Related Errors & Cross-Refs
no carrier, interface does not exist, network unreachable after reboot.
Related tutorial: View the step-by-step tutorial for freebsd-14.
View all freebsd-14 tutorials on the Tutorials Hub β
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
FreeBSD rc.conf networking and interface configuration handbook sections.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today β we respond within one business day.