networking.service not starting interfaces by default

Bug #1869458 reported by Rafael David Tinoco
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ifupdown2 (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

ifupdown2 won't start interfaces by default even when "networking.service" unit is enabled.

this happens because it is missing correct unit dependencies being declared:

--
After=systemd-udevd.service network-pre.target systemd-sysusers.service systemd-sysctl.service
Before=network.target multi-user.target shutdown.target
Conflicts=shutdown.target
Wants=network.target
--

After that all interfaces from /etc/network/interfaces get properly configured on boot.

Changed in ifupdown2 (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.