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

wwan: disconnect modem signals when disposing NMDeviceModem

2014-03-21T22:54:10+00:00

devices: send ARPs when configuring static IPv4 addresses (rh #1073447)

2014-03-21T13:26:19+00:00

After applying a configuration with static IPv4 addresses, call
/sbin/arping to announce the new addresses to the host's neighbors.
(Basic idea copied from Fedora ifup-eth.)

core: improve ifname matching of existing x generated connections (rh #1077743)

2014-03-21T08:24:13+00:00

DEVICE="ens3"
ONBOOT=yes
NETBOOT=yes
UUID="23466771-f5fa-4ca9-856f-eaf4a8e20c3f"
BOOTPROTO=none
IPADDR="10.0.0.2"
PREFIX="24"
GATEWAY="10.0.0.1"
HWADDR="52:54:00:12:34:56"
TYPE=Ethernet
NAME="ens3"

This ifcfg file results in connection.interface-name=ens3.
However, device-generated connection didn't set interface-name property.

Fix that by setting interface-name property when generating a connection. Also
allow matching connections if interface-name is not set in a connection.

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

core: export ActiveConnection before handing it to the device (bgo #723783)

2014-03-21T00:26:40+00:00

The AC doesn't get a D-Bus path until it's exported, but that happens after
it's handed to the Device it will be activated on.  The Device emits a
PropertyChanged event when it's handed the AC, but it ignores ACs that
aren't exported yet.  Thus when activating, the Device doesn't emit the
AC's path at all in the ActiveConnection property because it's NULL.

Fix that by exporting the AC immediately before starting activation
with it.

Second, move the notification of the Device.ActiveConnection property
to be emitted along with the state change to PREPARE instead of long
before it.  While we don't guarantee signal ordering in general, this
seems like a more correct ordering.

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

core: warn if multiple plugins for the same type are installed

2014-03-19T18:56:47+00:00

If we find multiple plugins for the same type (eg, because the user
previously installed the "atm" and "bt" plugins, and didn't delete
them), log a warning.

devices: rename "atm" plugin to "adsl", and "bt" to "bluetooth"

2014-03-19T18:56:47+00:00

The atm/adsl plugin really is a generic ATM plugin but (a) it needs a
bit of work to do IPoATM rather than just PPPoATM and PPPoEoATM, and
(b) most people currently using NM's ATM support are using DSL devices
not actual ATM cards anyway, and have no idea what "ATM" even means.
If we add the necessary IPoATM support later we can rename the plugin
back to -atm

core: emit PropertyChanged signal for ActiveConnection when disconnecting

2014-03-18T20:37:37+00:00

devices: change log message when "deactivating" device on startup

2014-03-18T20:29:04+00:00

nm_device_deactivate() is used when deactivating a device, but also
when initializing it when it is first managed. Rename it to
nm_device_cleanup(), and use a different log message ("preparing
device") in the NM_DEVICE_STATE_REASON_NOW_MANAGED case.

core: add debug logging when setting IP[46]Config instance of a NMDevice

2014-03-17T19:38:23+00:00

Signed-off-by: Thomas Haller

core: fix auto-activation of ignore-carrier devices when carrier appears (rh #1076592)

2014-03-17T15:34:53+00:00

If a device had its carrier ignored, and did not have a carrier on startup,
then NetworkManager would not re-check autoconnect connections when the
device's carrier appeared.  Because ignore-carrier devices are always
in DISCONNECTED state when they are managed, the nm-device.c::carrier_changed()
code essentially did nothing when the carrier appeared.  It needs to
also trigger an auto-activation recheck signal when the carrier appears
to ensure that now-valid connections (like those that require DHCP or
IPv6) can be auto-activated.