| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
#1158529)
|
| |
|
|
|
|
|
| |
If the AUTOCONNECT_SLAVES variable is missing, we suppose values compatible
with initscripts, i.e. "yes" for bonds and teams, "no" for bridges.
|
|
|
|
| |
- split DEFAULT to DEFAULT_NO and DEFAULT_YES
|
| |
|
|
|
|
|
|
|
|
|
| |
When a master connection is activated, check all its slaves and decide whether
they should be activated as well. This is done according to the
autoconnect-slaves property.
https://bugzilla.gnome.org/show_bug.cgi?id=735052
https://bugzilla.redhat.com/show_bug.cgi?id=1158529
|
| |
|
|
|
|
|
|
|
|
| |
AUTOCONNECT_SLAVES is an NetworkManager extension. initscripts always activate
slaves with the master connection for bond and team, and doesn't activate
automatically slaves for bridge.
NetworkManager behaviour is controlled by this variable. If the variable is
missing the default value from configuration file is used.
|
|
|
|
|
|
|
|
| |
The property is used for controlling whether slaves should be brought up with
a master connection. If 0, activating the master will not activate slaves.
But if set to 1, activating the master will bring up slaves as well.
The property can have the third state (-1), meaning that the value is default.
That is either a value set in the configuration file for the property, or 0.
|
| |
|
|
|
|
|
|
|
|
|
| |
Adjust nmcli prompt-color description and make it more friendly for
translators.
nmcli> nmcli prompt-color green
https://bugzilla.gnome.org/show_bug.cgi?id=744936
|
|
|
|
|
|
|
| |
nmc_property_connection_get_metered() must return non-localized strings
that can be parsed by nmc_property_connection_set_metered().
Fixes: f0aebfd7462dea9b3ebc579a49248027f6d23905
|
|
|
|
|
|
|
|
|
| |
warning: function declaration isn’t a prototype [-Wstrict-prototypes]
In C function() and function(void) are two different prototypes (as opposed to
C++).
function() accepts an arbitrary number of arguments
function(void) accepts zero arguments
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Expose information about whether a connection is metered and use some
heuristics to choose a reasonable default when the value is not
configured.
https://bugzilla.gnome.org/show_bug.cgi?id=741725
https://bugzilla.redhat.com/show_bug.cgi?id=1200452
|
| |
| |
| |
| |
| |
| | |
This introduces a global metered property which makes easier for
clients to obtain the metered status of the current primary
connection.
|
| |
| |
| |
| |
| | |
Valid values must not be translated in error messages generated in
nmc_string_to_bool() and nmc_string_to_tristate().
|
| | |
|
| |
| |
| |
| |
| |
| | |
Change type of return value and 'def' argument of svTrueValue() to
gint to make clear that it can be something different from TRUE and
FALSE.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The metered property of a NMDevice that reaches the activated state is
copied from the active connection and if its value is 'unknown' some
heuristics are used to guess the actual value.
When the connection is torn down the metered property is reset to
'unknown'.
|
| |
| |
| |
| |
| |
| |
| | |
Some versions of Android's DHCP server send option 43 (Vendor specific
information) with value "ANDROID_METERED" in Wi-Fi hotspot mode.
Mark the NMIP4Config as metered when such option is received.
|
| |
| |
| |
| |
| |
| |
| | |
This adds support for DHCP option 43 (Vendor Specific Information) to
the internal DHCP client. The option carries an opaque object of n
octets, interpreted by vendor-specific code on the clients and
servers.
|
| |
| |
| |
| |
| |
| |
| | |
Some DHCP servers send specific options to give a hint that clients
should avoid unneeded data usage.
Add a metered flag to NMIP4Config to keep track of this information.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Add a 'metered' enum property to NMSettingConnection with possible
values: unknown,yes,no. The value indicates the presence of limitations
in the amount of traffic flowing through the connection.
|
| | |
|
|/ |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- add new file 'nm-platform-utils.c' and moves some independent utility
functions there (ethtool, udev).
- some refactoring of platform code, including initialization of
NMPlatform instance.
- run platform tests in a separate user namespace, which allow
us to run root-tests as non-root.
https://bugzilla.gnome.org/show_bug.cgi?id=747981
|
| | |
|
| |
| |
| |
| |
| | |
Whether we have support depends on the kernel, and is not
per NMLinuxPlatform instance.
|
| | |
|
| |
| |
| |
| | |
nmp_utils_mii_supports_carrier_detect()
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There is no general purpose file for platform utilities.
We only have nm-platform.h, which contains (mostly) functions
that operate on a NMPlatform instance (and that can be mocked
using NMFakePlatform).
Add a new file for independent utility functions. nm-platform-utils.c
should not call into functions having a NMPlatform instance, to
have them independent from platform caching and the platform
singleton.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
nm_platform_query_devices() would raise an 'added' signal
for all its links. That is bad style because it could
confuse other listeners for platform signals which don't
expect such artificial change signals.
The public API of NMPlatform already gives NMManager the ability
to 'pull' all the links and iterate them itself.
Before, nm_platform_query_devices() would also initialize udev
devices, so there was a more compelling reason for this function.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We already populate the netlink cache in constructed(). No need
to wait with udev devices until nm_platform_query_devices(). Just
do it right away.
Add a hack to keep 'lo' default-unmanaged. Now that we load
udev devices earlier, we end up clearing the default-unmanged
flag on 'lo', which has bad consequences.
|
| | |
|
| |
| |
| |
| | |
This fixes the test run in a container/our NETNS/NEWUSER test jail.
|
| |
| |
| |
| |
| |
| | |
We don't want error logging for nm_platform_link_add() which
tries to load the bonding module. Later we will run tests as non-root,
where modprobe will fail. Logging an error would break the tests.
|
| | |
|
|/
|
|
|
|
| |
Even if asserts are not enabled, still let the compiler see what we would
assert. Otherwise, we get warnings about unused variables or we migth miss
compile errors inside nm_assert().
|
|
|
|
|
|
| |
This reverts commit 6a841c0cd1532f6e2e04c2fbb674ee3f69c714b7.
We do actually need the modules for connectivity checking.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- support new [connection] section in NetworkManager.conf
- allow configuring a default value for ipvx.route-metric
- allow configuring a default value for ipv6.ip6-privacy
and read the fallback configuration from sysctl.
https://bugzilla.gnome.org/show_bug.cgi?id=695383
https://bugzilla.gnome.org/show_bug.cgi?id=721200
https://bugzilla.redhat.com/show_bug.cgi?id=1187525
|