Network Interface Not Managed by NetworkManager

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

Desktop or server NIC appears disconnected while link is physically up. DHCP, DNS, and routing changes are ignored, causing partial outages.

Environment & Reproduction

Happens on Ubuntu 16.04 when /etc/network/interfaces defines interfaces manually and conflicts with NetworkManager defaults. Reproduce with iface stanzas left from templates.

Root Cause Analysis

NetworkManager marks interfaces unmanaged if traditional ifupdown config claims ownership. Mixed management layers create inconsistent network state.

Quick Triage

Use nmcli device status and check /etc/NetworkManager/NetworkManager.conf. Inspect /etc/network/interfaces for non-loopback iface definitions.

Step-by-Step Diagnosis

Confirm active handlers with systemctl status NetworkManager networking. Trace interface events in journalctl -u NetworkManager and verify DHCP lease behavior.

Solution – Primary Fix

Remove or comment legacy iface entries for managed NICs, set managed=true if needed, then restart NetworkManager. Reconnect using nmcli con up .

Solution – Alternative Approaches

Keep static configuration in ifupdown and disable NetworkManager for server-only roles, ensuring one clear source of truth for networking.

Verification & Acceptance Criteria

nmcli shows interface as connected and managed, IP and gateway are correct, and DNS resolution works consistently.

Rollback Plan

Restore previous /etc/network/interfaces and NetworkManager.conf files, restart networking services, and verify prior connectivity model.

Prevention & Hardening

Standardize on one network stack per host profile and enforce config checks during image build. Document cloud-init network ownership expectations.

Related Errors & Cross-Refs

Can coincide with temporary DNS failures, default route missing, and DHCP timeout errors in journal logs.

Related tutorial: View the step-by-step tutorial for Ubuntu 16.04 LTS.

View all Ubuntu 16.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

NetworkManager(8), interfaces(5), and Ubuntu 16.04 networking transition notes.