RTFM · Troubleshooting
Interfaces missing
eth0 vanished, or the interface has another name entirely: driver loading, renaming surprises, bridges, and virtual switches explained.

Distinguish absent from renamed
An interface that renamed itself looks identical to one that never existed. List everything the kernel knows about before concluding hardware failure.
ip -o link show
ls /sys/class/net/
dmesg | grep -iE 'eth|enp|firmware|link up'Driver did not load
If /sys/class/net contains only lo, the NIC driver either failed to load or lacks firmware. The dmesg excerpt names both precisely.
1. Identify the NIC
lspci gives vendor:device IDs for the controller.
2. Check firmware messages
dmesg | grep -i firmware — 'failed to load' lines name the required file.
3. Install matching firmware/drivers
apk search finds the relevant package; the Bootstrap guide explains kernel module selection for custom kernels.
4. Or modprobe directly
modprobe <drivername> loads immediately to prove the diagnosis without rebooting.
Bridges, OVS and VLAN devices
Missing bridge or OVS ports mean the datapath was never created. Verify existence first:
ovs-vsctl show # OVS datapath present?
ovs-vsctl list-br
ip link show type bridgeProve it works: predictable interface mapping
you can state which physical port corresponds to which interface name, documented in /etc/network.d comments, so next week's failure starts ahead.
Did we miss something?
If this page left something unanswered, found an error, or there is another subject you would like documented, tell us. Saphira’s documentation grows from real problems people need to solve.
Send feedback or request a new section →
Prefer not to do it yourself?
Everything needed to do the work yourself is documented here and remains free — we charge for human time, not for withholding knowledge. Sometimes the missing resource is simply time. The same people who build Saphira can provide paid professional help with implementation, migration, troubleshooting and administration.