diff options
| author | Thomas Haller <thaller@redhat.com> | 2018-04-19 13:24:11 +0200 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2018-04-30 16:36:29 +0200 |
| commit | 5a1f84b085835742e715a05b4e5e65e518a47c42 (patch) | |
| tree | d110e1a194686efad4c50629ce94e906ed0e0405 /src/nm-manager.c | |
| parent | feb1ec1e879146b88c6ee23ddf5ed37b2ec83ec5 (diff) | |
| download | NetworkManager-5a1f84b085835742e715a05b4e5e65e518a47c42.tar.gz | |
core: add activation-reasons for external/assume connections
Until now, we only really cared about whether a connection was activated
with reason NM_ACTIVATION_REASON_AUTOCONNECT_SLAVES or not.
Now however, we will care about whether a connection was activated via
(genuine) autoconnect by NMPolicy, or external/assume by NMManager.
Add a new reason to distinguish between them.
Diffstat (limited to 'src/nm-manager.c')
| -rw-r--r-- | src/nm-manager.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/nm-manager.c b/src/nm-manager.c index 4a831f3e8c..25ba1c278a 100644 --- a/src/nm-manager.c +++ b/src/nm-manager.c @@ -2562,7 +2562,7 @@ recheck_assume_connection (NMManager *self, device, subject, generated ? NM_ACTIVATION_TYPE_EXTERNAL : NM_ACTIVATION_TYPE_ASSUME, - NM_ACTIVATION_REASON_AUTOCONNECT, + generated ? NM_ACTIVATION_REASON_EXTERNAL : NM_ACTIVATION_REASON_ASSUME, &error); if (!active) { |