diff options
| author | Michael Biebl <biebl@debian.org> | 2022-05-13 15:12:23 +0200 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2022-05-13 15:12:23 +0200 |
| commit | 84afb2ff5f7405ec3b98bbe627cd071105626087 (patch) | |
| tree | fc82d122eda3fede7ace3026a09af018e1af3174 /docs/api/html | |
| parent | d26308b229deb999da934f582aa8f3d5caaa63c0 (diff) | |
| parent | 87d61411bb3453587d21487da04fcf770fee7d55 (diff) | |
Update upstream source from tag 'upstream/1.38.0'
Update to upstream version '1.38.0' with Debian dir fb301733063d70b26e8eff5a4877a6a4f0bcddc2
Diffstat (limited to 'docs/api/html')
| -rw-r--r-- | docs/api/html/index.html | 2 | ||||
| -rw-r--r-- | docs/api/html/nm-dbus-types.html | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/api/html/index.html b/docs/api/html/index.html index 1fbe7a13..34b74087 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@ <div> <div><table class="navigation" id="top" width="100%" cellpadding="2" cellspacing="0"><tr><th valign="middle"><p class="title">NetworkManager Reference Manual</p></th></tr></table></div> <div><p class="releaseinfo"> - for NetworkManager 1.37.92 + for NetworkManager 1.38.0 The latest version of this documentation can be found on-line at <a class="ulink" href="https://networkmanager.dev/docs/api/latest/" target="_top">https://networkmanager.dev/docs/api/latest/</a>. diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index 6ee39f84..673eb0e4 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -3070,7 +3070,7 @@ <hr> <div class="refsect2"> <a name="NMMetered"></a><h3>enum NMMetered</h3> -<p>The NMMetered enum has two different purposes: one is to configure "connection.metered" setting of a connection profile in NMSettingConnection, and the other is to express the actual metered state of the NMDevice at a given moment.</p> +<p>The NMMetered enum has two different purposes: one is to configure "connection.metered" setting of a connection profile in NMSettingConnection, and the other is to express the actual metered state of the <a href="/usr/share/gtk-doc/html/libnm/NMActiveConnection.html#NMDevice-struct">NMDevice</a> at a given moment.</p> <p>For the connection profile only NM_METERED_UNKNOWN, NM_METERED_NO and NM_METERED_YES are allowed.</p> <p>The device's metered state at runtime is determined by the profile which is currently active. If the profile explicitly specifies NM_METERED_NO or NM_METERED_YES, then the device's metered state is as such. If the connection profile leaves it undecided at NM_METERED_UNKNOWN (the default), then NetworkManager tries to guess the metered state, for example based on the device type or on DHCP options (like Android devices exposing a "ANDROID_METERED" DHCP vendor option). This then leads to either NM_METERED_GUESS_NO or NM_METERED_GUESS_YES.</p> <p>Most applications probably should treat the runtime state NM_METERED_GUESS_YES like NM_METERED_YES, and all other states as not metered.</p> |