delta/NetworkManager.git/include, branch th/NMStringTable

platform, devices: add support for vxlan devices

2014-03-06T14:48:15+00:00

Since vxlan is new-ish, and vxlan IPv6 support in particular has only
been in the kernel since 3.11, we include our own copy of the vxlan
netlink constants rather than depending on the installed headers.

replace snprintf by g_snprintf

2014-02-24T20:35:33+00:00

Use the glib wrapper for snprintf.

Signed-off-by: Thomas Haller

build: improve our use of glib's version macros to catch more bugs

2014-02-13T16:24:37+00:00

We were setting GLIB_VERSION_MAX_ALLOWED to 2.34, since we provide
reimplementations of a few 2.34 functions in nm-glib-compat.h. But
this was turning off warnings for the 2.34+ APIs we *didn't* have
compat versions of too.

Fix this by setting MAX_ALLOWED to 2.32 (same as MIN_REQUIRED), and
defining macros to wrap calls to compat-ified functions and disable
deprecation warnings around them.

This points out several places where we were accidentally using 2.34
APIs without noticing, which need to be fixed now.

libnm-util, libnm-glib: add versioned deprecation/availability macros

2014-02-13T16:24:37+00:00

Add versioned NM_DEPRECATED_IN_* and NM_AVAILABLE_IN_* macros, and tag
new/deprecated functions accordingly. (All currently-deprecated
functions are assumed to have been deprecated in 0.9.10.)

Add NM_VERSION_MIN_REQUIRED and NM_VERSION_MAX_ALLOWED macros which
can be set to determine which versions will cause warnings.

With the current settings, external consumers of the
libnm-util/libnm-glib APIs will have MIN_REQUIRED and MAX_ALLOWED both
set to NM_VERSION_0_9_8 by default, meaning they will get warnings
about functions added in 0.9.10. NM internally sets
NM_VERSION_MAX_ALLOWED to NM_VERSION_NEXT_STABLE to ensure that it is
always allowed to use all APIs.

core: implement update_connection() for Team

2013-11-08T22:35:18+00:00

core: set up and tear down DCB/FCoE when DCB is enabled

2013-10-31T18:29:22+00:00

dispatcher: fix memory leak in nm-dispatcher-action

2013-10-22T17:53:46+00:00

Signed-off-by: Thomas Haller

vpn: fix VPN plugin D-Bus errors

2013-09-27T11:26:29+00:00

The errors were documented as org.freedesktop.NetworkManager.VPN.Error.*,
but the actual values were org.freedesktop.NetworkManager.VPN.Plugin.*

Also update the errors documentation.

vpn: fix connecting to VPN (bgo #708255)

2013-09-27T11:26:09+00:00

The ConnectInteractive() -> Connect() fallback code doesn't work, because
_connect_internal() changes the state to NM_VPN_SERVICE_STATE_STARTING before
checking if it can implement ConnectInteractive(), and then when the Connect()
call comes in, the VPN is not in STOPPED or INIT, so it returns an error.

The commit moves setting state to STARTING after the ConnectInteractive() check
availability, in the plugin. We introduce new plugin error and set it when the
the plugin does not implement ConnectInteractive(). NetworkManager uses this
error for ConnectInteractive() -> Connect() fallback.

https://bugzilla.gnome.org/show_bug.cgi?id=708255

libnm-glib: change "Since: 0.9.10" to "Since: 0.9.8.6" for backported API

2013-09-11T18:10:55+00:00