2016-03-01 09:56:51 +01:00
|
|
|
/* -*- Mode: C; tab-width: 4; indent-tabs-mode: t; c-basic-offset: 4 -*- */
|
|
|
|
|
/* NetworkManager -- Network link manager
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
|
* (at your option) any later version.
|
|
|
|
|
*
|
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
|
*
|
|
|
|
|
* You should have received a copy of the GNU General Public License along
|
|
|
|
|
* with this program; if not, write to the Free Software Foundation, Inc.,
|
|
|
|
|
* 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
|
|
|
|
*
|
|
|
|
|
* Copyright 2004 - 2016 Red Hat, Inc.
|
|
|
|
|
* Copyright 2005 - 2008 Novell, Inc.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef __NM_CORE_UTILS_H__
|
|
|
|
|
#define __NM_CORE_UTILS_H__
|
|
|
|
|
|
|
|
|
|
#include <stdio.h>
|
|
|
|
|
#include <arpa/inet.h>
|
|
|
|
|
|
|
|
|
|
#include "nm-connection.h"
|
|
|
|
|
|
2018-10-17 14:09:13 +02:00
|
|
|
#include "nm-utils/nm-time-utils.h"
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
/*****************************************************************************/
|
|
|
|
|
|
2016-03-07 11:45:44 +01:00
|
|
|
#define NM_PLATFORM_LIFETIME_PERMANENT G_MAXUINT32
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
#define NM_DEFINE_SINGLETON_INSTANCE(TYPE) \
|
|
|
|
|
static TYPE *singleton_instance
|
|
|
|
|
|
|
|
|
|
#define NM_DEFINE_SINGLETON_REGISTER(TYPE) \
|
|
|
|
|
NM_DEFINE_SINGLETON_INSTANCE (TYPE); \
|
|
|
|
|
static void \
|
|
|
|
|
_singleton_instance_weak_ref_cb (gpointer data, \
|
|
|
|
|
GObject *where_the_object_was) \
|
|
|
|
|
{ \
|
|
|
|
|
nm_log_dbg (LOGD_CORE, "disposing %s singleton (%p)", G_STRINGIFY (TYPE), singleton_instance); \
|
|
|
|
|
singleton_instance = NULL; \
|
|
|
|
|
} \
|
|
|
|
|
static inline void \
|
|
|
|
|
nm_singleton_instance_register (void) \
|
|
|
|
|
{ \
|
|
|
|
|
g_object_weak_ref (G_OBJECT (singleton_instance), _singleton_instance_weak_ref_cb, NULL); \
|
|
|
|
|
_nm_singleton_instance_register_destruction (G_OBJECT (singleton_instance)); \
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void _nm_singleton_instance_register_destruction (GObject *instance);
|
|
|
|
|
|
|
|
|
|
/* By default, the getter will assert that the singleton will be created only once. You can
|
|
|
|
|
* change this by redefining NM_DEFINE_SINGLETON_ALLOW_MULTIPLE. */
|
|
|
|
|
#ifndef NM_DEFINE_SINGLETON_ALLOW_MULTIPLE
|
|
|
|
|
#define NM_DEFINE_SINGLETON_ALLOW_MULTIPLE FALSE
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#define NM_DEFINE_SINGLETON_GETTER(TYPE, GETTER, GTYPE, ...) \
|
|
|
|
|
NM_DEFINE_SINGLETON_INSTANCE (TYPE); \
|
|
|
|
|
NM_DEFINE_SINGLETON_REGISTER (TYPE); \
|
2018-10-24 10:52:42 +02:00
|
|
|
static char _already_created_##GETTER = FALSE; \
|
2016-03-01 09:56:51 +01:00
|
|
|
TYPE * \
|
|
|
|
|
GETTER (void) \
|
|
|
|
|
{ \
|
|
|
|
|
if (G_UNLIKELY (!singleton_instance)) { \
|
2018-10-24 10:52:42 +02:00
|
|
|
g_assert (!(_already_created_##GETTER) || (NM_DEFINE_SINGLETON_ALLOW_MULTIPLE)); \
|
|
|
|
|
(_already_created_##GETTER) = TRUE;\
|
2016-03-01 09:56:51 +01:00
|
|
|
singleton_instance = (g_object_new (GTYPE, ##__VA_ARGS__, NULL)); \
|
|
|
|
|
g_assert (singleton_instance); \
|
|
|
|
|
nm_singleton_instance_register (); \
|
|
|
|
|
nm_log_dbg (LOGD_CORE, "create %s singleton (%p)", G_STRINGIFY (TYPE), singleton_instance); \
|
|
|
|
|
} \
|
|
|
|
|
return singleton_instance; \
|
2018-10-24 10:52:42 +02:00
|
|
|
} \
|
|
|
|
|
_nm_unused static void \
|
|
|
|
|
_nmtst_##GETTER##_reset (TYPE *instance) \
|
|
|
|
|
{ \
|
|
|
|
|
/* usually, the singleton can only be created once (and further instantiations
|
|
|
|
|
* are guarded by an assert). For testing, we need to reset the singleton to
|
|
|
|
|
* allow multiple instantiations. */ \
|
|
|
|
|
g_assert (G_IS_OBJECT (instance)); \
|
|
|
|
|
g_assert (instance == singleton_instance); \
|
|
|
|
|
g_assert (_already_created_##GETTER); \
|
|
|
|
|
g_object_unref (instance); \
|
|
|
|
|
\
|
|
|
|
|
/* require that the last unref also destroyed the singleton. If this fails,
|
|
|
|
|
* somebody still keeps a reference. Fix your test! */ \
|
|
|
|
|
g_assert (!singleton_instance); \
|
|
|
|
|
_already_created_##GETTER = FALSE; \
|
2016-03-01 09:56:51 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* attach @instance to the data or @owner. @owner owns a reference
|
|
|
|
|
* to @instance thus the lifetime of @instance is at least as long
|
|
|
|
|
* as that of @owner. Use this when @owner depends on @instance. */
|
|
|
|
|
#define NM_UTILS_KEEP_ALIVE(owner, instance, unique_token) \
|
|
|
|
|
G_STMT_START { \
|
|
|
|
|
g_object_set_data_full (G_OBJECT (owner), \
|
|
|
|
|
".nm-utils-keep-alive-" unique_token "", \
|
|
|
|
|
g_object_ref (instance), \
|
|
|
|
|
g_object_unref); \
|
|
|
|
|
} G_STMT_END
|
|
|
|
|
|
|
|
|
|
/*****************************************************************************/
|
|
|
|
|
|
|
|
|
|
gboolean nm_ethernet_address_is_valid (gconstpointer addr, gssize len);
|
|
|
|
|
|
2016-04-12 15:55:44 +02:00
|
|
|
gconstpointer nm_utils_ipx_address_clear_host_address (int family, gpointer dst, gconstpointer src, guint8 plen);
|
2016-03-01 09:56:51 +01:00
|
|
|
in_addr_t nm_utils_ip4_address_clear_host_address (in_addr_t addr, guint8 plen);
|
|
|
|
|
const struct in6_addr *nm_utils_ip6_address_clear_host_address (struct in6_addr *dst, const struct in6_addr *src, guint8 plen);
|
2017-09-11 21:34:35 +02:00
|
|
|
|
|
|
|
|
static inline int
|
|
|
|
|
nm_utils_ip4_address_same_prefix_cmp (in_addr_t addr_a, in_addr_t addr_b, guint8 plen)
|
|
|
|
|
{
|
|
|
|
|
NM_CMP_DIRECT (htonl (nm_utils_ip4_address_clear_host_address (addr_a, plen)),
|
|
|
|
|
htonl (nm_utils_ip4_address_clear_host_address (addr_b, plen)));
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
2017-07-26 10:58:39 +02:00
|
|
|
int nm_utils_ip6_address_same_prefix_cmp (const struct in6_addr *addr_a, const struct in6_addr *addr_b, guint8 plen);
|
|
|
|
|
|
2017-09-11 21:34:35 +02:00
|
|
|
static inline gboolean
|
|
|
|
|
nm_utils_ip4_address_same_prefix (in_addr_t addr_a, in_addr_t addr_b, guint8 plen)
|
|
|
|
|
{
|
|
|
|
|
return nm_utils_ip4_address_same_prefix_cmp (addr_a, addr_b, plen) == 0;
|
|
|
|
|
}
|
|
|
|
|
|
2017-07-26 10:58:39 +02:00
|
|
|
static inline gboolean
|
|
|
|
|
nm_utils_ip6_address_same_prefix (const struct in6_addr *addr_a, const struct in6_addr *addr_b, guint8 plen)
|
|
|
|
|
{
|
|
|
|
|
return nm_utils_ip6_address_same_prefix_cmp (addr_a, addr_b, plen) == 0;
|
|
|
|
|
}
|
|
|
|
|
|
2017-09-11 21:34:35 +02:00
|
|
|
#define NM_CMP_DIRECT_IN4ADDR_SAME_PREFIX(a, b, plen) \
|
|
|
|
|
NM_CMP_RETURN (nm_utils_ip4_address_same_prefix_cmp ((a), (b), (plen)))
|
|
|
|
|
|
2017-07-26 10:58:39 +02:00
|
|
|
#define NM_CMP_DIRECT_IN6ADDR_SAME_PREFIX(a, b, plen) \
|
|
|
|
|
NM_CMP_RETURN (nm_utils_ip6_address_same_prefix_cmp ((a), (b), (plen)))
|
|
|
|
|
|
2017-10-13 14:00:22 +02:00
|
|
|
static inline void
|
|
|
|
|
nm_hash_update_in6addr (NMHashState *h, const struct in6_addr *addr)
|
2017-07-26 10:50:23 +02:00
|
|
|
{
|
2017-10-16 12:38:16 +02:00
|
|
|
nm_assert (addr);
|
|
|
|
|
|
|
|
|
|
nm_hash_update (h, addr, sizeof (*addr));
|
2017-07-26 10:50:23 +02:00
|
|
|
}
|
|
|
|
|
|
2017-10-13 14:00:22 +02:00
|
|
|
static inline void
|
|
|
|
|
nm_hash_update_in6addr_prefix (NMHashState *h, const struct in6_addr *addr, guint8 plen)
|
2017-07-26 10:50:23 +02:00
|
|
|
{
|
|
|
|
|
struct in6_addr a;
|
|
|
|
|
|
2017-10-16 12:38:16 +02:00
|
|
|
nm_assert (addr);
|
2017-10-13 14:00:22 +02:00
|
|
|
|
2017-07-26 10:50:23 +02:00
|
|
|
nm_utils_ip6_address_clear_host_address (&a, addr, plen);
|
|
|
|
|
/* we don't hash plen itself. The caller may want to do that.*/
|
2017-10-13 14:00:22 +02:00
|
|
|
nm_hash_update_in6addr (h, &a);
|
2017-07-26 10:50:23 +02:00
|
|
|
}
|
|
|
|
|
|
2017-03-24 11:27:41 +01:00
|
|
|
double nm_utils_exp10 (gint16 e);
|
2017-03-23 16:01:07 +01:00
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
/**
|
|
|
|
|
* nm_utils_ip6_route_metric_normalize:
|
|
|
|
|
* @metric: the route metric
|
|
|
|
|
*
|
|
|
|
|
* For IPv6 route, kernel treats the value 0 as IP6_RT_PRIO_USER (1024).
|
|
|
|
|
* Thus, when comparing metric (values), we want to treat zero as NM_PLATFORM_ROUTE_METRIC_DEFAULT_IP6.
|
|
|
|
|
*
|
|
|
|
|
* Returns: @metric, if @metric is not zero, otherwise 1024.
|
|
|
|
|
*/
|
|
|
|
|
static inline guint32
|
|
|
|
|
nm_utils_ip6_route_metric_normalize (guint32 metric)
|
|
|
|
|
{
|
2018-04-24 11:20:03 +02:00
|
|
|
return metric ?: 1024 /*NM_PLATFORM_ROUTE_METRIC_DEFAULT_IP6*/;
|
2016-03-01 09:56:51 +01:00
|
|
|
}
|
|
|
|
|
|
2017-08-30 19:10:59 +02:00
|
|
|
static inline guint32
|
|
|
|
|
nm_utils_ip_route_metric_normalize (int addr_family, guint32 metric)
|
|
|
|
|
{
|
|
|
|
|
return addr_family == AF_INET6 ? nm_utils_ip6_route_metric_normalize (metric) : metric;
|
|
|
|
|
}
|
|
|
|
|
|
2017-10-04 15:21:21 +02:00
|
|
|
static inline guint32
|
|
|
|
|
nm_utils_ip_route_metric_penalize (int addr_family, guint32 metric, guint32 penalty)
|
|
|
|
|
{
|
|
|
|
|
metric = nm_utils_ip_route_metric_normalize (addr_family, metric);
|
|
|
|
|
if (metric < G_MAXUINT32 - penalty)
|
|
|
|
|
return metric + penalty;
|
|
|
|
|
return G_MAXUINT32;
|
|
|
|
|
}
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
int nm_utils_modprobe (GError **error, gboolean suppress_error_loggin, const char *arg1, ...) G_GNUC_NULL_TERMINATED;
|
|
|
|
|
|
|
|
|
|
void nm_utils_kill_process_sync (pid_t pid, guint64 start_time, int sig, guint64 log_domain,
|
|
|
|
|
const char *log_name, guint32 wait_before_kill_msec,
|
|
|
|
|
guint32 sleep_duration_msec, guint32 max_wait_msec);
|
|
|
|
|
|
|
|
|
|
typedef void (*NMUtilsKillChildAsyncCb) (pid_t pid, gboolean success, int child_status, void *user_data);
|
|
|
|
|
void nm_utils_kill_child_async (pid_t pid, int sig, guint64 log_domain, const char *log_name,
|
|
|
|
|
guint32 wait_before_kill_msec,
|
|
|
|
|
NMUtilsKillChildAsyncCb callback, void *user_data);
|
|
|
|
|
gboolean nm_utils_kill_child_sync (pid_t pid, int sig, guint64 log_domain, const char *log_name,
|
|
|
|
|
int *child_status, guint32 wait_before_kill_msec,
|
|
|
|
|
guint32 sleep_duration_msec);
|
|
|
|
|
|
|
|
|
|
const char *nm_utils_find_helper (const char *progname,
|
|
|
|
|
const char *try_first,
|
|
|
|
|
GError **error);
|
|
|
|
|
|
2016-04-27 14:47:59 +02:00
|
|
|
char *nm_utils_read_link_absolute (const char *link_file, GError **error);
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
typedef enum {
|
|
|
|
|
NM_MATCH_SPEC_NO_MATCH = 0,
|
|
|
|
|
NM_MATCH_SPEC_MATCH = 1,
|
|
|
|
|
NM_MATCH_SPEC_NEG_MATCH = 2,
|
|
|
|
|
} NMMatchSpecMatchType;
|
|
|
|
|
|
core: refactor evaluation of device's match-spec
Previously, we would have different functions like
- nm_match_spec_device_type()
- nm_match_spec_hwaddr()
- nm_match_spec_s390_subchannels()
- nm_match_spec_interface_name()
which all would handle one type of match-spec.
So, to get the overall result whether the arguments
match or not, nm_device_spec_match_list() had to stich
them together and iterate the list multiple times.
Refactor the code to have one nm_match_spec_device()
function that gets all relevant paramters.
The upside is:
- the logic how to evaluate the match-spec is all at one place
(match_device_eval()) instead of spread over multiple
functions.
- It requires iterating the list at most twice. Twice, because
we do a fast pre-search for "*".
One downside could be, that we have to pass all 4 arguments
for the evaluation, even if the might no be needed. That is,
because "nm-core-utils.c" shall be independend from NMDevice, it
cannot receive a device instance to get the parameters as needed.
As we would add new match-types, the argument list would grow.
However, all arguments are cached and fetching them from the
device's private data is very cheap.
(cherry picked from commit b957403efd53ff7d826ac7a4f80487032c03824b)
2017-01-20 19:50:25 +01:00
|
|
|
NMMatchSpecMatchType nm_match_spec_device (const GSList *specs,
|
|
|
|
|
const char *interface_name,
|
device: fix order of params in nm_match_spec_device prototype
The following commit:
b869d9cc0 device: add spec "driver:" to match devices
added two parameters ("driver" and "driver_version") to the
nm_match_spec_device() function.
However, the definition of the function and its declaration are not
consistent.
The prototype shows:
nm_match_spec_device (const GSList *specs,
const char *interface_name,
const char *driver,
const char *driver_version,
const char *device_type,
But the definition shows:
nm_match_spec_device (const GSList *specs,
const char *interface_name,
const char *device_type,
const char *driver,
const char *driver_version,
Since all parameters are pointers to const char, the type checking
succeeds at compile time.
All currently existing invocations of the function are correct and pass
the arguments in the order described in the definition/implementation.
This patch only changes the prototype so that potential future
invocations don't end up buggy.
Fixes: b869d9cc0dda4fe5300f5ec5b5a090199ecd4e3e
2018-07-06 14:35:33 +02:00
|
|
|
const char *device_type,
|
2017-03-17 16:18:48 +01:00
|
|
|
const char *driver,
|
|
|
|
|
const char *driver_version,
|
core: refactor evaluation of device's match-spec
Previously, we would have different functions like
- nm_match_spec_device_type()
- nm_match_spec_hwaddr()
- nm_match_spec_s390_subchannels()
- nm_match_spec_interface_name()
which all would handle one type of match-spec.
So, to get the overall result whether the arguments
match or not, nm_device_spec_match_list() had to stich
them together and iterate the list multiple times.
Refactor the code to have one nm_match_spec_device()
function that gets all relevant paramters.
The upside is:
- the logic how to evaluate the match-spec is all at one place
(match_device_eval()) instead of spread over multiple
functions.
- It requires iterating the list at most twice. Twice, because
we do a fast pre-search for "*".
One downside could be, that we have to pass all 4 arguments
for the evaluation, even if the might no be needed. That is,
because "nm-core-utils.c" shall be independend from NMDevice, it
cannot receive a device instance to get the parameters as needed.
As we would add new match-types, the argument list would grow.
However, all arguments are cached and fetching them from the
device's private data is very cheap.
(cherry picked from commit b957403efd53ff7d826ac7a4f80487032c03824b)
2017-01-20 19:50:25 +01:00
|
|
|
const char *hwaddr,
|
device: add "dhcp-plugin" match spec for device
The need for this is the following:
"ipv4.dhcp-client-id" can be specified via global connection defaults.
In absence of any configuration in NetworkManager, the default depends
on the DHCP client plugin. In case of "dhclient", the default further
depends on /etc/dhcp.
For "internal" plugin, we may very well want to change the default
client-id to "mac" by universally installing a configuration
snippet
[connection-use-mac-client-id]
ipv4.dhcp-client-id=mac
However, if we the user happens to enable "dhclient" plugin, this also
forces the client-id and overrules configuration from /etc/dhcp. The real
problem is, that dhclient can be configured via means outside of NetworkManager,
so our defaults shall not overwrite defaults from /etc/dhcp.
With the new device spec, we can avoid this issue:
[connection-dhcp-client-id]
match-device=except:dhcp-plugin:dhclient
ipv4.dhcp-client-id=mac
This will be part of the solution for rh#1640494. Note that merely
dropping a configuration snippet is not yet enough. More fixes for
DHCP will follow. Also, bug rh#1640494 may have alternative solutions
as well. The nice part of this new feature is that it is generally
useful for configuring connection defaults and not specifically for
the client-id issue.
Note that this match spec is per-device, although the plugin is selected
globally. That makes some sense, because in the future we may or may not
configure the DHCP plugin per-device or per address family.
https://bugzilla.redhat.com/show_bug.cgi?id=1640494
2018-10-24 08:43:45 +02:00
|
|
|
const char *s390_subchannels,
|
|
|
|
|
const char *dhcp_plugin);
|
core: refactor evaluation of device's match-spec
Previously, we would have different functions like
- nm_match_spec_device_type()
- nm_match_spec_hwaddr()
- nm_match_spec_s390_subchannels()
- nm_match_spec_interface_name()
which all would handle one type of match-spec.
So, to get the overall result whether the arguments
match or not, nm_device_spec_match_list() had to stich
them together and iterate the list multiple times.
Refactor the code to have one nm_match_spec_device()
function that gets all relevant paramters.
The upside is:
- the logic how to evaluate the match-spec is all at one place
(match_device_eval()) instead of spread over multiple
functions.
- It requires iterating the list at most twice. Twice, because
we do a fast pre-search for "*".
One downside could be, that we have to pass all 4 arguments
for the evaluation, even if the might no be needed. That is,
because "nm-core-utils.c" shall be independend from NMDevice, it
cannot receive a device instance to get the parameters as needed.
As we would add new match-types, the argument list would grow.
However, all arguments are cached and fetching them from the
device's private data is very cheap.
(cherry picked from commit b957403efd53ff7d826ac7a4f80487032c03824b)
2017-01-20 19:50:25 +01:00
|
|
|
NMMatchSpecMatchType nm_match_spec_config (const GSList *specs,
|
|
|
|
|
guint nm_version,
|
|
|
|
|
const char *env);
|
2016-03-01 09:56:51 +01:00
|
|
|
GSList *nm_match_spec_split (const char *value);
|
|
|
|
|
char *nm_match_spec_join (GSList *specs);
|
|
|
|
|
|
2018-08-09 09:29:51 +02:00
|
|
|
gboolean nm_wildcard_match_check (const char *str,
|
|
|
|
|
const char *const *patterns,
|
|
|
|
|
guint num_patterns);
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
/*****************************************************************************/
|
|
|
|
|
|
2017-08-30 19:17:29 +02:00
|
|
|
gboolean nm_utils_connection_has_default_route (NMConnection *connection,
|
|
|
|
|
int addr_family,
|
|
|
|
|
gboolean *out_is_never_default);
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
char *nm_utils_new_vlan_name (const char *parent_iface, guint32 vlan_id);
|
2016-04-20 10:45:31 +02:00
|
|
|
const char *nm_utils_new_infiniband_name (char *name, const char *parent_name, int p_key);
|
2016-03-01 09:56:51 +01:00
|
|
|
|
2017-02-03 15:38:58 +01:00
|
|
|
int nm_utils_cmp_connection_by_autoconnect_priority (NMConnection *a, NMConnection *b);
|
2016-03-01 09:56:51 +01:00
|
|
|
|
2018-03-29 11:47:52 +02:00
|
|
|
void nm_utils_log_connection_diff (NMConnection *connection,
|
|
|
|
|
NMConnection *diff_base,
|
|
|
|
|
guint32 level, guint64 domain,
|
|
|
|
|
const char *name,
|
|
|
|
|
const char *prefix,
|
|
|
|
|
const char *dbus_path);
|
2016-03-01 09:56:51 +01:00
|
|
|
|
|
|
|
|
gboolean nm_utils_is_valid_path_component (const char *name);
|
2016-03-08 17:35:41 +01:00
|
|
|
const char *NM_ASSERT_VALID_PATH_COMPONENT (const char *name);
|
2017-10-23 13:55:54 +02:00
|
|
|
|
2017-10-23 13:55:54 +02:00
|
|
|
#define NM_UTILS_SYSCTL_IP_CONF_PATH_BUFSIZE 100
|
2017-10-23 13:55:54 +02:00
|
|
|
|
2017-10-23 13:55:54 +02:00
|
|
|
const char *nm_utils_sysctl_ip_conf_path (int addr_family, char *buf, const char *ifname, const char *property);
|
2016-03-01 09:56:51 +01:00
|
|
|
|
2017-10-23 14:24:28 +02:00
|
|
|
gboolean nm_utils_sysctl_ip_conf_is_path (int addr_family, const char *path, const char *ifname, const char *property);
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
gboolean nm_utils_is_specific_hostname (const char *name);
|
|
|
|
|
|
core: refactor loading machine-id and cache it
Previously, whenever we needed /etc/machine-id we would re-load it
from file. The are 3 downsides of that:
- the smallest downside is the runtime overhead of repeatedly
reading the file and parse it.
- as we read it multiple times, it may change anytime. Most
code in NetworkManager does not expect or handle a change of
the machine-id.
Generally, the admin should make sure that the machine-id is properly
initialized before NetworkManager starts, and not change it. As such,
a change of the machine-id should never happen in practice.
But if it would change, we would get odd behaviors. Note for example
how generate_duid_from_machine_id() already cached the generated DUID
and only read it once.
It's better to pick the machine-id once, and rely to use the same
one for the remainder of the program.
If the admin wants to change the machine-id, NetworkManager must be
restarted as well (in case the admin cares).
Also, as we now only load it once, it makes sense to log an error
(once) when we fail to read the machine-id.
- previously, loading the machine-id could fail each time. And we
have to somehow handle that error. It seems, the best thing what we
anyway can do, is to log an error once and continue with a fake
machine-id. Here we add a fake machine-id based on the secret-key
or the boot-id. Now obtaining a machine-id can no longer fail
and error handling is no longer necessary.
Also, ensure that a machine-id of all zeros is not valid.
Technically, a machine-id is not an RFC 4122 UUID. But it's
the same size, so we also use NMUuid data structure for it.
While at it, also refactor caching of the boot-id and the secret
key. In particular, fix the thread-safety of the double-checked
locking implementations.
2018-10-30 14:07:11 +01:00
|
|
|
struct _NMUuid;
|
|
|
|
|
|
|
|
|
|
const char *nm_utils_machine_id_str (void);
|
|
|
|
|
const struct _NMUuid *nm_utils_machine_id_bin (void);
|
|
|
|
|
gboolean nm_utils_machine_id_is_fake (void);
|
|
|
|
|
|
2018-12-12 10:14:51 +01:00
|
|
|
const char *nm_utils_boot_id_str (void);
|
|
|
|
|
const struct _NMUuid *nm_utils_boot_id_bin (void);
|
2016-04-25 21:18:06 +02:00
|
|
|
|
2018-12-12 10:10:38 +01:00
|
|
|
gboolean nm_utils_host_id_get (const guint8 **out_host_id,
|
|
|
|
|
gsize *out_host_id_len);
|
core: never fail reading host-id timestamp and never change it
The timestamp of the host-id is the timestamp of the secret_key file.
Under normal circumstances, reading the timestamp should never fail,
and reading it multiple times should always yield the same result.
If we unexpectedly fail to read the timestamp from the file we want:
- log a warning, so that the user can find out what's wrong. But
do so only once.
- we don't want to handle errors or fail operation due to a missing
timestamp. Remember, it's not supposed to ever fail, and if it does,
just log a warning and proceed with a fake timestamp instead. In
that case something is wrong, but using a non-stable, fake timestamp
is the least of the problems here.
We already have a stable identifier (the host-id) which we can use to
generate a fake timestamp. Use it.
In case the user would replace the secret_key file, we also don't want
that accessing nm_utils_host_id_get_timestamp*() yields different
results. It's not implemented (nor necessary) to support reloading a
different timestamp. Hence, nm_utils_host_id_get_timestamp() should
memoize the value and ensure that it never changes.
2018-12-12 11:04:12 +01:00
|
|
|
gint64 nm_utils_host_id_get_timestamp_ns (void);
|
2016-04-25 18:14:25 +02:00
|
|
|
|
2018-12-20 08:50:07 +01:00
|
|
|
int nm_utils_arp_type_detect_from_hwaddrlen (gsize hwaddr_len);
|
2018-12-14 08:45:09 +01:00
|
|
|
|
2017-05-28 17:34:31 +03:00
|
|
|
/* IPv6 Interface Identifier helpers */
|
2016-03-01 09:56:51 +01:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* NMUtilsIPv6IfaceId:
|
|
|
|
|
* @id: convenience member for validity checking; never use directly
|
|
|
|
|
* @id_u8: the 64-bit Interface Identifier
|
|
|
|
|
*
|
|
|
|
|
* Holds a 64-bit IPv6 Interface Identifier. The IID is a sequence of bytes
|
|
|
|
|
* and should not normally be treated as a %guint64, but this is done for
|
|
|
|
|
* convenience of validity checking and initialization.
|
|
|
|
|
*/
|
|
|
|
|
struct _NMUtilsIPv6IfaceId {
|
|
|
|
|
union {
|
|
|
|
|
guint64 id;
|
|
|
|
|
guint8 id_u8[8];
|
|
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#define NM_UTILS_IPV6_IFACE_ID_INIT { { .id = 0 } }
|
|
|
|
|
|
2016-04-30 16:43:10 +02:00
|
|
|
void nm_utils_ipv6_addr_set_interface_identifier (struct in6_addr *addr,
|
|
|
|
|
const NMUtilsIPv6IfaceId iid);
|
|
|
|
|
|
|
|
|
|
void nm_utils_ipv6_interface_identifier_get_from_addr (NMUtilsIPv6IfaceId *iid,
|
|
|
|
|
const struct in6_addr *addr);
|
|
|
|
|
|
|
|
|
|
gboolean nm_utils_ipv6_interface_identifier_get_from_token (NMUtilsIPv6IfaceId *iid,
|
|
|
|
|
const char *token);
|
|
|
|
|
|
|
|
|
|
const char *nm_utils_inet6_interface_identifier_to_token (NMUtilsIPv6IfaceId iid,
|
|
|
|
|
char *buf);
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
gboolean nm_utils_get_ipv6_interface_identifier (NMLinkType link_type,
|
|
|
|
|
const guint8 *hwaddr,
|
|
|
|
|
guint len,
|
|
|
|
|
guint dev_id,
|
|
|
|
|
NMUtilsIPv6IfaceId *out_iid);
|
|
|
|
|
|
2016-12-18 14:03:38 +01:00
|
|
|
typedef enum {
|
|
|
|
|
/* The stable type. Note that this value is encoded in the
|
|
|
|
|
* generated addresses, thus the numbers MUST not change.
|
|
|
|
|
*
|
|
|
|
|
* Also note, if we ever allocate ID 255, we must take care
|
|
|
|
|
* that nm_utils_ipv6_addr_set_stable_privacy() extends the
|
|
|
|
|
* uint8 encoding of this value. */
|
2016-12-18 13:54:26 +01:00
|
|
|
NM_UTILS_STABLE_TYPE_UUID = 0,
|
2016-06-21 18:07:56 +02:00
|
|
|
NM_UTILS_STABLE_TYPE_STABLE_ID = 1,
|
2016-12-18 13:54:26 +01:00
|
|
|
NM_UTILS_STABLE_TYPE_GENERATED = 2,
|
|
|
|
|
NM_UTILS_STABLE_TYPE_RANDOM = 3,
|
2016-06-21 18:07:56 +02:00
|
|
|
} NMUtilsStableType;
|
|
|
|
|
|
2016-12-18 13:54:26 +01:00
|
|
|
NMUtilsStableType nm_utils_stable_id_parse (const char *stable_id,
|
2018-05-22 18:35:43 +02:00
|
|
|
const char *deviceid,
|
2018-11-02 12:07:09 +01:00
|
|
|
const char *hwaddr,
|
2016-12-18 13:54:26 +01:00
|
|
|
const char *bootid,
|
2018-05-22 18:35:43 +02:00
|
|
|
const char *uuid,
|
2016-12-18 13:54:26 +01:00
|
|
|
char **out_generated);
|
|
|
|
|
|
|
|
|
|
char *nm_utils_stable_id_random (void);
|
|
|
|
|
char *nm_utils_stable_id_generated_complete (const char *msg);
|
2016-10-18 11:54:58 +02:00
|
|
|
|
2016-12-18 14:03:38 +01:00
|
|
|
gboolean nm_utils_ipv6_addr_set_stable_privacy_impl (NMUtilsStableType stable_type,
|
2016-10-18 11:54:58 +02:00
|
|
|
struct in6_addr *addr,
|
|
|
|
|
const char *ifname,
|
|
|
|
|
const char *network_id,
|
2017-04-27 13:58:38 +02:00
|
|
|
guint32 dad_counter,
|
2018-12-12 10:10:38 +01:00
|
|
|
guint8 *host_id,
|
|
|
|
|
gsize host_id_len,
|
2016-10-18 11:54:58 +02:00
|
|
|
GError **error);
|
|
|
|
|
|
2016-06-21 18:07:56 +02:00
|
|
|
gboolean nm_utils_ipv6_addr_set_stable_privacy (NMUtilsStableType id_type,
|
|
|
|
|
struct in6_addr *addr,
|
2016-03-01 09:56:51 +01:00
|
|
|
const char *ifname,
|
2016-06-21 18:07:00 +02:00
|
|
|
const char *network_id,
|
2017-04-27 13:58:38 +02:00
|
|
|
guint32 dad_counter,
|
2016-03-01 09:56:51 +01:00
|
|
|
GError **error);
|
|
|
|
|
|
all: make MAC address randomization algorithm configurable
For the per-connection settings "ethernet.cloned-mac-address"
and "wifi.cloned-mac-address", and for the per-device setting
"wifi.scan-rand-mac-address", we may generate MAC addresses using
either the "random" or "stable" algorithm.
Add new properties "generate-mac-address-mask" that allow to configure
which bits of the MAC address will be scrambled.
By default, the "random" and "stable" algorithms scamble all bits
of the MAC address, including the OUI part and generate a locally-
administered, unicast address.
By specifying a MAC address mask, we can now configure to perserve
parts of the current MAC address of the device. For example, setting
"FF:FF:FF:00:00:00" will preserve the first 3 octects of the current
MAC address.
One can also explicitly specify a MAC address to use instead of the
current MAC address. For example, "FF:FF:FF:00:00:00 68:F7:28:00:00:00"
sets the OUI part of the MAC address to "68:F7:28" while scrambling
the last 3 octects.
Similarly, "02:00:00:00:00:00 00:00:00:00:00:00" will scamble
all bits of the MAC address, except clearing the second-least
significant bit. Thus, creating a burned-in address, globally
administered.
One can also supply a list of MAC addresses like
"FF:FF:FF:00:00:00 68:F7:28:00:00:00 00:0C:29:00:00:00 ..." in which
case a MAC address is choosen randomly.
To fully scamble the MAC address one can configure
"02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00".
which also randomly creates either a locally or globally administered
address.
With this, the following macchanger options can be implemented:
`macchanger --random`
This is the default if no mask is configured.
-> ""
while is the same as:
-> "00:00:00:00:00:00"
-> "02:00:00:00:00:00 02:00:00:00:00:00"
`macchanger --random --bia`
-> "02:00:00:00:00:00 00:00:00:00:00:00"
`macchanger --ending`
This option cannot be fully implemented, because macchanger
uses the current MAC address but also implies --bia.
-> "FF:FF:FF:00:00:00"
This would yields the same result only if the current MAC address
is already a burned-in address too. Otherwise, it has not the same
effect as --ending.
-> "FF:FF:FF:00:00:00 <MAC_ADDR>"
Alternatively, instead of using the current MAC address,
spell the OUI part out. But again, that is not really the
same as macchanger does because you explictly have to name
the OUI part to use.
`machanger --another`
`machanger --another_any`
-> "FF:FF:FF:00:00:00 <MAC_ADDR> <MAC_ADDR> ..."
"$(printf "FF:FF:FF:00:00:00 %s\n" "$(sed -n 's/^\([0-9a-fA-F][0-9a-fA-F]\) \([0-9a-fA-F][0-9a-fA-F]\) \([0-9a-fA-F][0-9a-fA-F]\) .*/\1:\2:\3:00:00:00/p' /usr/share/macchanger/wireless.list | xargs)")"
2016-06-22 20:31:39 +02:00
|
|
|
char *nm_utils_hw_addr_gen_random_eth (const char *current_mac_address,
|
|
|
|
|
const char *generate_mac_address_mask);
|
2016-10-18 11:54:58 +02:00
|
|
|
char *nm_utils_hw_addr_gen_stable_eth_impl (NMUtilsStableType stable_type,
|
|
|
|
|
const char *stable_id,
|
2018-12-12 10:10:38 +01:00
|
|
|
const guint8 *host_id,
|
|
|
|
|
gsize host_id_len,
|
2016-10-18 11:54:58 +02:00
|
|
|
const char *ifname,
|
|
|
|
|
const char *current_mac_address,
|
|
|
|
|
const char *generate_mac_address_mask);
|
device: extend MAC address handling including randomization for ethernet and wifi
Extend the "ethernet.cloned-mac-address" and "wifi.cloned-mac-address"
settings. Instead of specifying an explicit MAC address, the additional
special values "permanent", "preserve", "random", "random-bia", "stable" and
"stable-bia" are supported.
"permanent" means to use the permanent hardware address. Previously that
was the default if no explict cloned-mac-address was set. The default is
thus still "permanent", but it can be overwritten by global
configuration.
"preserve" means not to configure the MAC address when activating the
device. That was actually the default behavior before introducing MAC
address handling with commit 1b49f941a69af910b0e68530be7339e8053068e5.
"random" and "random-bia" use a randomized MAC address for each
connection. "stable" and "stable-bia" use a generated, stable
address based on some token. The "bia" suffix says to generate a
burned-in address. The stable method by default uses as token the
connection UUID, but the token can be explicitly choosen via
"stable:<TOKEN>" and "stable-bia:<TOKEN>".
On a D-Bus level, the "cloned-mac-address" is a bytestring and thus
cannot express the new forms. It is replaced by the new
"assigned-mac-address" field. For the GObject property, libnm's API,
nmcli, keyfile, etc. the old name "cloned-mac-address" is still used.
Deprecating the old field seems more complicated then just extending
the use of the existing "cloned-mac-address" field, although the name
doesn't match well with the extended meaning.
There is some overlap with the "wifi.mac-address-randomization" setting.
https://bugzilla.gnome.org/show_bug.cgi?id=705545
https://bugzilla.gnome.org/show_bug.cgi?id=708820
https://bugzilla.gnome.org/show_bug.cgi?id=758301
2016-05-24 15:57:16 +02:00
|
|
|
char *nm_utils_hw_addr_gen_stable_eth (NMUtilsStableType stable_type,
|
|
|
|
|
const char *stable_id,
|
all: make MAC address randomization algorithm configurable
For the per-connection settings "ethernet.cloned-mac-address"
and "wifi.cloned-mac-address", and for the per-device setting
"wifi.scan-rand-mac-address", we may generate MAC addresses using
either the "random" or "stable" algorithm.
Add new properties "generate-mac-address-mask" that allow to configure
which bits of the MAC address will be scrambled.
By default, the "random" and "stable" algorithms scamble all bits
of the MAC address, including the OUI part and generate a locally-
administered, unicast address.
By specifying a MAC address mask, we can now configure to perserve
parts of the current MAC address of the device. For example, setting
"FF:FF:FF:00:00:00" will preserve the first 3 octects of the current
MAC address.
One can also explicitly specify a MAC address to use instead of the
current MAC address. For example, "FF:FF:FF:00:00:00 68:F7:28:00:00:00"
sets the OUI part of the MAC address to "68:F7:28" while scrambling
the last 3 octects.
Similarly, "02:00:00:00:00:00 00:00:00:00:00:00" will scamble
all bits of the MAC address, except clearing the second-least
significant bit. Thus, creating a burned-in address, globally
administered.
One can also supply a list of MAC addresses like
"FF:FF:FF:00:00:00 68:F7:28:00:00:00 00:0C:29:00:00:00 ..." in which
case a MAC address is choosen randomly.
To fully scamble the MAC address one can configure
"02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00".
which also randomly creates either a locally or globally administered
address.
With this, the following macchanger options can be implemented:
`macchanger --random`
This is the default if no mask is configured.
-> ""
while is the same as:
-> "00:00:00:00:00:00"
-> "02:00:00:00:00:00 02:00:00:00:00:00"
`macchanger --random --bia`
-> "02:00:00:00:00:00 00:00:00:00:00:00"
`macchanger --ending`
This option cannot be fully implemented, because macchanger
uses the current MAC address but also implies --bia.
-> "FF:FF:FF:00:00:00"
This would yields the same result only if the current MAC address
is already a burned-in address too. Otherwise, it has not the same
effect as --ending.
-> "FF:FF:FF:00:00:00 <MAC_ADDR>"
Alternatively, instead of using the current MAC address,
spell the OUI part out. But again, that is not really the
same as macchanger does because you explictly have to name
the OUI part to use.
`machanger --another`
`machanger --another_any`
-> "FF:FF:FF:00:00:00 <MAC_ADDR> <MAC_ADDR> ..."
"$(printf "FF:FF:FF:00:00:00 %s\n" "$(sed -n 's/^\([0-9a-fA-F][0-9a-fA-F]\) \([0-9a-fA-F][0-9a-fA-F]\) \([0-9a-fA-F][0-9a-fA-F]\) .*/\1:\2:\3:00:00:00/p' /usr/share/macchanger/wireless.list | xargs)")"
2016-06-22 20:31:39 +02:00
|
|
|
const char *ifname,
|
|
|
|
|
const char *current_mac_address,
|
|
|
|
|
const char *generate_mac_address_mask);
|
device: extend MAC address handling including randomization for ethernet and wifi
Extend the "ethernet.cloned-mac-address" and "wifi.cloned-mac-address"
settings. Instead of specifying an explicit MAC address, the additional
special values "permanent", "preserve", "random", "random-bia", "stable" and
"stable-bia" are supported.
"permanent" means to use the permanent hardware address. Previously that
was the default if no explict cloned-mac-address was set. The default is
thus still "permanent", but it can be overwritten by global
configuration.
"preserve" means not to configure the MAC address when activating the
device. That was actually the default behavior before introducing MAC
address handling with commit 1b49f941a69af910b0e68530be7339e8053068e5.
"random" and "random-bia" use a randomized MAC address for each
connection. "stable" and "stable-bia" use a generated, stable
address based on some token. The "bia" suffix says to generate a
burned-in address. The stable method by default uses as token the
connection UUID, but the token can be explicitly choosen via
"stable:<TOKEN>" and "stable-bia:<TOKEN>".
On a D-Bus level, the "cloned-mac-address" is a bytestring and thus
cannot express the new forms. It is replaced by the new
"assigned-mac-address" field. For the GObject property, libnm's API,
nmcli, keyfile, etc. the old name "cloned-mac-address" is still used.
Deprecating the old field seems more complicated then just extending
the use of the existing "cloned-mac-address" field, although the name
doesn't match well with the extended meaning.
There is some overlap with the "wifi.mac-address-randomization" setting.
https://bugzilla.gnome.org/show_bug.cgi?id=705545
https://bugzilla.gnome.org/show_bug.cgi?id=708820
https://bugzilla.gnome.org/show_bug.cgi?id=758301
2016-05-24 15:57:16 +02:00
|
|
|
|
2018-10-30 08:37:48 +01:00
|
|
|
/*****************************************************************************/
|
|
|
|
|
|
2018-11-23 13:00:07 +01:00
|
|
|
guint32 nm_utils_create_dhcp_iaid (gboolean legacy_unstable_byteorder,
|
|
|
|
|
const guint8 *interface_id,
|
|
|
|
|
gsize interface_id_len);
|
|
|
|
|
|
2018-10-30 08:37:48 +01:00
|
|
|
GBytes *nm_utils_dhcp_client_id_systemd_node_specific_full (gboolean legacy_unstable_byteorder,
|
|
|
|
|
const guint8 *interface_id,
|
|
|
|
|
gsize interface_id_len,
|
|
|
|
|
const guint8 *machine_id,
|
|
|
|
|
gsize machine_id_len);
|
|
|
|
|
|
|
|
|
|
GBytes *nm_utils_dhcp_client_id_systemd_node_specific (gboolean legacy_unstable_byteorder,
|
|
|
|
|
const char *ifname);
|
|
|
|
|
|
|
|
|
|
/*****************************************************************************/
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
void nm_utils_array_remove_at_indexes (GArray *array, const guint *indexes_to_delete, gsize len);
|
|
|
|
|
|
|
|
|
|
void nm_utils_setpgid (gpointer unused);
|
|
|
|
|
|
|
|
|
|
typedef enum {
|
|
|
|
|
NM_UTILS_TEST_NONE = 0,
|
|
|
|
|
|
|
|
|
|
/* Internal flag, marking that either nm_utils_get_testing() or _nm_utils_set_testing() was called. */
|
|
|
|
|
_NM_UTILS_TEST_INITIALIZED = (1LL << 0),
|
|
|
|
|
|
|
|
|
|
/* Indicate that test mode is enabled in general. Explicitly calling _nm_utils_set_testing() will always set this flag. */
|
|
|
|
|
_NM_UTILS_TEST_GENERAL = (1LL << 1),
|
|
|
|
|
|
|
|
|
|
/* Don't check the owner of keyfiles during testing. */
|
|
|
|
|
NM_UTILS_TEST_NO_KEYFILE_OWNER_CHECK = (1LL << 2),
|
|
|
|
|
|
|
|
|
|
_NM_UTILS_TEST_LAST,
|
|
|
|
|
NM_UTILS_TEST_ALL = (((_NM_UTILS_TEST_LAST - 1) << 1) - 1) & ~(_NM_UTILS_TEST_INITIALIZED),
|
|
|
|
|
} NMUtilsTestFlags;
|
|
|
|
|
|
|
|
|
|
gboolean nm_utils_get_testing_initialized (void);
|
|
|
|
|
NMUtilsTestFlags nm_utils_get_testing (void);
|
|
|
|
|
void _nm_utils_set_testing (NMUtilsTestFlags flags);
|
|
|
|
|
|
|
|
|
|
void nm_utils_g_value_set_strv (GValue *value, GPtrArray *strings);
|
|
|
|
|
|
|
|
|
|
guint nm_utils_parse_debug_string (const char *string,
|
|
|
|
|
const GDebugKey *keys,
|
|
|
|
|
guint nkeys);
|
|
|
|
|
|
2016-03-07 11:11:59 +01:00
|
|
|
void nm_utils_ifname_cpy (char *dst, const char *name);
|
|
|
|
|
|
2016-03-07 11:45:44 +01:00
|
|
|
guint32 nm_utils_lifetime_rebase_relative_time_on_now (guint32 timestamp,
|
|
|
|
|
guint32 duration,
|
2016-03-15 17:40:43 +01:00
|
|
|
gint32 now);
|
2016-03-07 11:45:44 +01:00
|
|
|
|
2018-02-07 21:32:10 +01:00
|
|
|
guint32 nm_utils_lifetime_get (guint32 timestamp,
|
|
|
|
|
guint32 lifetime,
|
|
|
|
|
guint32 preferred,
|
|
|
|
|
gint32 now,
|
|
|
|
|
guint32 *out_preferred);
|
2016-03-07 11:45:44 +01:00
|
|
|
|
|
|
|
|
gboolean nm_utils_ip4_address_is_link_local (in_addr_t addr);
|
|
|
|
|
|
2016-06-02 19:17:35 +02:00
|
|
|
const char *nm_utils_dnsmasq_status_to_string (int status, char *dest, gsize size);
|
2016-05-01 22:24:41 +02:00
|
|
|
|
2016-06-03 22:07:38 +02:00
|
|
|
void nm_utils_get_reverse_dns_domains_ip4 (guint32 ip, guint8 plen, GPtrArray *domains);
|
2016-06-03 22:07:42 +02:00
|
|
|
void nm_utils_get_reverse_dns_domains_ip6 (const struct in6_addr *ip, guint8 plen, GPtrArray *domains);
|
2016-06-03 22:07:38 +02:00
|
|
|
|
2016-11-17 09:56:16 +01:00
|
|
|
struct stat;
|
|
|
|
|
|
|
|
|
|
gboolean nm_utils_validate_plugin (const char *path, struct stat *stat, GError **error);
|
2016-11-03 18:07:11 +01:00
|
|
|
char **nm_utils_read_plugin_paths (const char *dirname, const char *prefix);
|
2017-03-03 23:59:16 +01:00
|
|
|
char *nm_utils_format_con_diff_for_audit (GHashTable *diff);
|
|
|
|
|
|
2018-04-21 13:04:39 +02:00
|
|
|
GVariant *nm_utils_strdict_to_variant (GHashTable *options);
|
|
|
|
|
|
2017-10-09 11:56:51 +02:00
|
|
|
/*****************************************************************************/
|
|
|
|
|
|
|
|
|
|
/* this enum is compatible with ICMPV6_ROUTER_PREF_* (from <linux/icmpv6.h>,
|
|
|
|
|
* the values for netlink attribute RTA_PREF) and "enum ndp_route_preference"
|
|
|
|
|
* from <ndp.h>. */
|
|
|
|
|
typedef enum {
|
|
|
|
|
NM_ICMPV6_ROUTER_PREF_MEDIUM = 0x0, /* ICMPV6_ROUTER_PREF_MEDIUM */
|
|
|
|
|
NM_ICMPV6_ROUTER_PREF_LOW = 0x3, /* ICMPV6_ROUTER_PREF_LOW */
|
|
|
|
|
NM_ICMPV6_ROUTER_PREF_HIGH = 0x1, /* ICMPV6_ROUTER_PREF_HIGH */
|
|
|
|
|
NM_ICMPV6_ROUTER_PREF_INVALID = 0x2, /* ICMPV6_ROUTER_PREF_INVALID */
|
|
|
|
|
} NMIcmpv6RouterPref;
|
|
|
|
|
|
|
|
|
|
const char *nm_icmpv6_router_pref_to_string (NMIcmpv6RouterPref pref, char *buf, gsize len);
|
2016-11-03 18:07:11 +01:00
|
|
|
|
2017-03-07 11:04:36 +01:00
|
|
|
/*****************************************************************************/
|
|
|
|
|
|
|
|
|
|
const char *nm_activation_type_to_string (NMActivationType activation_type);
|
|
|
|
|
|
|
|
|
|
/*****************************************************************************/
|
|
|
|
|
|
2018-01-10 11:23:33 +01:00
|
|
|
const char *nm_utils_parse_dns_domain (const char *domain, gboolean *is_routing);
|
|
|
|
|
|
2016-03-01 09:56:51 +01:00
|
|
|
#endif /* __NM_CORE_UTILS_H__ */
|