After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761001 - The NetworkManager's systemd service MUST order itself after network-pre.target
The NetworkManager's systemd service MUST order itself after network-pre.target
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal major
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-01-22 19:42 UTC by Steven
Modified: 2016-01-23 16:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Steven 2016-01-22 19:42:50 UTC 
Currently, NetworkManager will happily start and connect to networks before network-pre.target has started. According to the manual:

> This passive target unit may be pulled in by services that want to run before any network is set up, for example for the purpose of setting up a firewall. All network management software orders itself after this target, but does not pull it in.

This means that NetworkManger is starting before firewalls. The solution is to add an `After=network-pre.target` line to the NetworkManager.service unit.
Comment 2 Steven 2016-01-23 16:07:31 UTC 
That was fast. Thanks!