1. 16 Jan, 2017 33 commits
  2. 13 Jan, 2017 1 commit
  3. 12 Jan, 2017 5 commits
    • Beniamino Galvani's avatar
      libnm-core: fix documentation warnings · 334a8a54
      Beniamino Galvani authored
      libnm-core/nm-setting-8021x.c:658: Warning: NM: nm_setting_802_1x_set_ca_cert: unknown parameter 'value' in documentation comment, should be 'cert_path'
      libnm-core/nm-setting-8021x.c:1023: Warning: NM: nm_setting_802_1x_set_client_cert: unknown parameter 'value' in documentation comment, should be 'cert_path'
      libnm-core/nm-setting-8021x.c:1331: Warning: NM: nm_setting_802_1x_set_phase2_ca_cert: unknown parameter 'value' in documentation comment, should be 'cert_path'
      libnm-core/nm-setting-8021x.c:1702: Warning: NM: nm_setting_802_1x_set_phase2_client_cert: unknown parameter 'value' in documentation comment, should be 'cert_path'
      libnm-core/nm-setting-8021x.c:2027: Warning: NM: nm_setting_802_1x_set_private_key: unknown parameter 'value' in documentation comment, should be 'key_path'
      libnm-core/nm-setting-8021x.c:2374: Warning: NM: nm_setting_802_1x_set_phase2_private_key: unknown parameter 'value' in documentation comment, should be 'key_path'
      
      Fixes: 2b09cee6
      334a8a54
    • Thomas Haller's avatar
    • Dan Williams's avatar
      device/wwan: indicate whether IP iface/ifindex changed and simplify WwAN code · 8de7b8ed
      Dan Williams authored
      Replace some code in the WWAN device class that checks for a changed
      interface name with code that uses the new return value from
      nm_device_set_ip_iface(), which now checks whether the ip_ifindex
      changed too.
      
      https://mail.gnome.org/archives/networkmanager-list/2017-January/msg00010.html
      8de7b8ed
    • Thomas Haller's avatar
      device: avoid changing immutable properties during reapply · bf3b3d44
      Thomas Haller authored
      We allow to reapply a connection with different id, uuid, stable-id, autoconnect value.
      This is allowed for convenience, so that a user can reapply a connection that differs
      in these fields. But actually, these fields cannot be reapplied. That
      is, their new values are not considered and the old values are continued
      to be used.
      
      Thus, mangle the reapplied connection to use the original, actually used
      values.
      bf3b3d44
    • Thomas Haller's avatar
      device: allow reapplying a connection with differing stable-id · 304e2f56
      Thomas Haller authored
      The stable-id for one activation cannot actually change. This is also, because we cache it
      as priv->current_stable_id. Still, allow reapply with a differing stable-id for convenience.
      304e2f56
  4. 11 Jan, 2017 1 commit