delta/NetworkManager.git/src/nm-manager.h, branch th/NMStringTable

core: provide useful error messages to main() on Manager creation failure

2014-01-24T19:14:05+00:00

api/core: add Devices property to the Manager

2014-01-23T23:34:12+00:00

core: move virtual device autoconnect tracking bits out of NMManager

2014-01-23T20:16:09+00:00

Virtual devices may be created and destroyed, but we need to keep
their autoconnect state across that. Previously this was handled by
NMManager, but it really belongs with the other autoconnect tracking
in NMPolicy and NMSettingsConnection.

This also fixes a bug where NMPolicy would sometimes decide to
autoactivate a virtual device connection which NMManager would then
have to cancel.

Revert "core: add Devices property to Manager"

2013-11-25T21:19:09+00:00

This reverts commit c1768154c4cfdc394cd175396157e5e4c48359af.

Not supposed to be committed yet, see dcbw/dbus-properties for the
real patch.

core: add Devices property to Manager

2013-11-25T17:59:13+00:00

Helps other bindings.

core: don't allow activating the same connection twice (rh #997998)

2013-11-06T15:21:27+00:00

Change the rules for connection activation so that a given
NMConnection can only be used by a single NMActiveConnection at any
given time.

core: pass NMAuthSubject around activation paths instead of uid + dbus sender

2013-10-31T19:15:08+00:00

core: make nm_manager_activate_connection() take a Device, not a path

2013-10-31T19:15:07+00:00

Simpler; everywhere that called it has an NMDevice already anyway.

core: track autoconnect for removed software devices (rh #1005913)

2013-10-24T09:58:18+00:00

When an interface is manually disconnected NM remembers that, and prevents
automatic activation of the device.
However, software devices are removed when they are disconnected, and thus
the state of the device is lost. We need to track autoconnect outside the
device - hash table of interface names not allowed to activate automatically.

Without that the device would be auto-activated again and again, even if
explicitly disconnected.
Test case:
$ nmcli con add type bond ifname bb con-name bb-con
$ nmcli con add type bond-slave ifname em1 con-name b1-con master bb
$ nmcli dev disconnect bb

https://bugzilla.redhat.com/show_bug.cgi?id=1005913

core: add NMManager:primary-connection and :activating-connection

2013-08-28T15:01:13+00:00

Add properties to track the "primary" connection (ie, the active
connection with either the default route, or the route to the VPN with
the default route), and the active connection that is currently
activating, and likely to become the :primary-connection when it
completes.

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