| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Otherwise the call to stop() would generate a new unwanted state
transition.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Merge another early part of 'lr/default-unmanaged-bgo746566'
https://bugzilla.gnome.org/show_bug.cgi?id=746566
|
| |
| |
| |
| |
| |
| | |
NM_DEVICE_CHECK_CON_AVAILABLE_FOR_USER_REQUEST is a multi-flag value combining all
the hooks that compose a user-request. Add a special value that has no esplicit
meaning except that it ~is~ a user-request.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For update, don't delete first and add it again. Just do it
in one step.
For recheck, don't delete all connections first to add them
all anew. Instead, check what changes and only emit the changed
signal if there are any actual changes.
|
|/ |
|
|
|
|
|
|
| |
Also use NM_UTILS_LOOKUP_STR() macro, which can transform
unknown values to their numerical representation using
alloca().
|
|
|
|
|
| |
Due to using a switch stetement, it is no longer only useful for looking
up strings, and it certainly doesn't use a table anymore.
|
|
|
|
|
|
| |
The compiler will likely optimize a switch() statement also to a table
lookup, but it also works for negative values and values with large
gaps.
|
| |
|
| |
|
|
|
|
| |
_NM_UTILS_STRING_LOOKUP_TABLE_DEFINE()
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=761001
|
|
|
|
|
|
|
|
|
|
| |
Only install nm-settings-ifcfg-rh.5 man page if the ifcfg-rh
configuration plugin has been enabled.
But still add them to EXTRA_DIST so that the source tarball
contains the generated man-file, but it isn't installed.
https://bugzilla.gnome.org/show_bug.cgi?id=759823
|
|
|
|
| |
Fixes: 1408b8c0a21105f3ea6d2e58d0fc03835f255d34
|
|\
| |
| |
| |
| |
| |
| | |
Remove iptables rules for connection sharing upon termination to avoid
the presence of duplicate rules when NM is restarted.
https://bugzilla.gnome.org/show_bug.cgi?id=692673
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When connection sharing is enabled, the removal of iptables rules is
delegated to the NMActRequest destructor; but for this to work it is
required that the object is properly dereferenced upon NM termination.
Clean up the active connections which are in DEACTIVATED state when
quitting, so that they are unexported and destroyed.
https://bugzilla.gnome.org/show_bug.cgi?id=692673
|
|/
|
|
|
|
|
|
|
| |
The rules were added to the list using g_slist_append() and then
applied one at time using "iptables --insert" which puts them at the
beginning of the chain, reversing the initial order.
Instead, list them in the desired order and use g_slist_prepend() to
achieve the same result. This has no functional changes.
|
|
|
|
| |
CAP_SYS_CHROOT is needed for openvpn hardening.
|
|
|
|
|
| |
Also, decouple the build from the test run; it looks better in the .yml file as
well as in the travis UI.
|
|\
| |
| |
| | |
Update build script to prefer dbus-run-session over dbus-launch.
|
| | |
|
| |
| |
| |
| | |
Like on Ubuntu 12.04 which is currently used by our Travic CI setup.
|
| | |
|
|/
|
|
|
|
|
|
|
| |
The dbus-run-session utility was designed to run a process within a
D-Bus session, specifically for running regressions tests and is much
better suited then dbus-launch. As an additional benefit, this avoids
any X dependencies.
https://mail.gnome.org/archives/networkmanager-list/2016-January/msg00023.html
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Point in case:
# ip link add link dummy0 name dummy0.vlan type vlan id 4095
RTNETLINK answers: Numerical result out of range
This potentially causes existing (invalid) connections to disappear
as they now fail verification.
Instead of adjusting the range of the GObject property
NM_SETTING_VLAN_ID, reject it during vlan. This is a bit more
forgiving to an older client that isn't aware of this new restriction,
so he can first set the value without raising a critical warning.
|
| |
|
| |
|
|
|
|
|
|
|
| |
nm_utils_new_vlan_name() should reject the reserved VLAN id 4095, and
the test case should not test reserved values 0 and 4095.
Fixes: 778207f23eb2ac022b2ee47968a484fdb94626fe
|
|
|
|
| |
failed tests
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=1300755
|
|
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=1300755
|
| |
|
| |
|
|
|
|
|
| |
Fixes: 4dbaac4ba24ebc8b257fffe5197cc8e362804a58
Fixes: d8e1590c5058de91126bfa790c27aea944a2b596
|
| |
|
| |
|
|
|
|
|
| |
CID 59376 (#2-1 of 2): Argument cannot be negative (NEGATIVE_RETURNS)
negative_returns: urandom is passed to a parameter that cannot be negative.
|
|
|
|
|
|
| |
Coverity: CID 59378 (#1 of 1): Nesting level does not match indentation
(NESTING_INDENT_MISMATCH) This statement is indented to column 41, as if
it were nested within the preceding parent statement, but it is not.
|
|
|
|
|
| |
Coverity: CID 59384 (#3-1 of 3): Resource leak (RESOURCE_LEAK)26.
leaked_handle: Handle variable fd going out of scope leaks the handle
|
|\
| |
| |
| | |
https://bugzilla.redhat.com/show_bug.cgi?id=1298007
|
| |
| |
| |
| |
| | |
nm_supplicant_interface_new() should be merely a convenient interface
for creating the object directly.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
nm_supplicant_manager_iface_release()
nm_supplicant_manager_iface_get() would cache and reuse the supplicant
interface. But no ref-counting was in place so that the first user returning
the interface via nm_supplicant_manager_iface_release() would destroy the
instance for others.
This is broken for a very long time. Which shows that we hardly ever
have a cache-hit and usually create a new instance. So, instead of
letting nm_supplicant_manager_create_interface() check for existing
supplicant interface, always create a new instance. This also makes
sense, because we would expect that per ifname only one instance is
requested at a time. Also add an assertion that we don't return
multiple supplicant interface instances for the same ifname.
Drop nm_supplicant_manager_iface_release() in favor of requiring users
to unref the returned instance.
Also, use a GSList instead of a GHashTable for the cache.
Also, previously callers would pass @is_wireless to nm_supplicant_manager_iface_get(),
but the cache lookup did not consider that value. That doesn't matter
now as we always create a new instance.
https://bugzilla.redhat.com/show_bug.cgi?id=1298007
|
| |
| |
| |
| |
| |
| | |
Also, don't only consider the @die_count whether to start the supplicant,
but check for is_available() -- which already considers @die_count and
@running.
|
| |
| |
| |
| | |
interface_add()
|
| |
| |
| |
| | |
A plain constructor for a GObject cannot fail.
|