1. 15 Nov, 2013 7 commits
    • Dan Winship's avatar
      core: add o.fd.NM.Settings.LoadConnections · 51c6269d
      Dan Winship authored
      Add a D-Bus method to reload connection files specified by
      filename, and implement it in the ifcfg-rh and keyfile backends.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=709830
      51c6269d
    • Dan Winship's avatar
      devices: use disable_ipv6 as appropriate · 65737d9e
      Dan Winship authored
      Set and clear disable_ipv6 on devices as needed to ensure that:
      
        1) devices never get IPv6 link local addresses until they are
           actually activated
      
        2) devices always lose their IPv6 link local addresses when they are
           deactivated
      
        3) slaves never get IPv6 link local addresses at all
      
      https://bugzilla.gnome.org/show_bug.cgi?id=700414
      https://bugzilla.redhat.com/show_bug.cgi?id=1004255
      65737d9e
    • Dan Winship's avatar
      devices: enable/disable kernel IPv6 autoconf at the appropriate times · 7496cc3d
      Dan Winship authored
      Set accept_ra and use_tempaddr to "0" when managing a device (and
      restore them to their original values after unmanaging it) to ensure
      that calling nm_device_bring_up() on a managed device won't ever cause
      kernel IPv6 autoconf to happen. Remove some other redundant accept_ra
      setting.
      
      Fix up the deconfigure case of dispose() to clear the device's IP6
      config as well as its IP4 config.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=700414
      7496cc3d
    • Dan Winship's avatar
      devices: clean up accept_ra/use_tempaddr handling · 29dc6d1e
      Dan Winship authored
      update_accept_ra_path() and update_ip6_privacy_save() were freeing
      their path variables if they failed to read the existing values, but
      if this ever actually happened it would cause problems later since
      other code assumed that the variables were always set. Use
      "priv->ip6_accept_ra_save = -1", etc, instead to indicate that the
      value couldn't be read (and so shouldn't be restored later).
      
      Merge the accept_ra and use_tempaddr code save/restore code together,
      since they're always called together.
      
      Fix the accept_ra-restoring code to correctly handle an original value
      of "2".
      
      Call update_ip6_properties_paths() from nm_device_set_ip_iface()
      rather than act_stage3_ip6_config_start(), since set_ip_iface() is
      when the paths actually change. Also, split the default-value-saving
      code out into a separate function, since we only care about doing that
      at construct time; if the IP6 property paths change later (because
      iface != ip_iface), then we don't need to save and restore the values
      on the ip_iface, since the interface will go away when we're done with
      it.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=700414
      29dc6d1e
    • Dan Winship's avatar
      devices: rename ip6_privacy_tempaddr_* vars to match sysctl · ee2b50fc
      Dan Winship authored
      Rename ip6_privacy_tempaddr_path and ip6_privacy_tempaddr_save to
      ip6_use_tempaddr_*, to match the sysctls, for consistency with the
      accept_ra variables.
      ee2b50fc
    • Dan Winship's avatar
      devices: "deactivate" devices when going from UNMANAGED->UNAVAILABLE · 46295e8f
      Dan Winship authored
      We used to call nm_device_deactivate() when moving a device from
      UNMANAGED to UNAVAILABLE (unless we were assuming the existing
      connection), but this got lost when default-unmanaged was added. Fix
      it to do this again, so the device will be in a known-clean state when
      it is activated.
      46295e8f
    • Dan Winship's avatar
      core: remove redundant sysctl utilities · 7bc7da83
      Dan Winship authored
      NMDevice was still using the old sysctl functions from
      NetworkManagerUtils rather than the new NMPlatform ones. Fix it, and
      remove the old functions.
      7bc7da83
  2. 14 Nov, 2013 7 commits
  3. 13 Nov, 2013 12 commits
  4. 12 Nov, 2013 4 commits
  5. 11 Nov, 2013 5 commits
  6. 09 Nov, 2013 1 commit
  7. 08 Nov, 2013 4 commits
    • Dan Williams's avatar
      merge: better take-over of existing connections on NM startup (bgo #702488) · 465458a2
      Dan Williams authored
      Read more state of connections that exist before NM starts, and take those
      connections over more effectively.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=702488
      465458a2
    • Dan Williams's avatar
      core: don't deactivate assumed connections when quitting · f4139112
      Dan Williams authored
      If an assumed bridge/bond/team/whatever happened to be in the process
      of activating (perhaps it had no recognized slaves and was waiting for
      them to continue with IP configuration) when NM quits, don't deactivate
      the device and blow away the assumed configuration.
      f4139112
    • Dan Winship's avatar
      core: NMManager:state fixes for assumed connections, etc · 6b7ebc0e
      Dan Winship authored
      Don't set NMManager:state to CONNECTING when assuming a connection,
      since it's not actually "connecting".
      
      If there are active connections, but none has the default route, then
      the global state should be CONNECTED_LOCAL, not CONNECTED_GLOBAL.
      
      Also tweak the semantics of CONNECTING/DISCONNECTING slightly; we only
      set state to CONNECTING when connecting a new connection if we are not
      already CONNECTED_GLOBAL, and we only set it to DISCONNECTING if we
      will be DISCONNECTED afterward.
      6b7ebc0e
    • Dan Williams's avatar
      core: don't up devices during IP configuration stages · 0e2457d7
      Dan Williams authored
      Assumed connections shouldn't require touching the device, and the
      device should was already set IFF_UP during stage2 (which is
      skipped for assumed connections).  Instead, what the code was really
      trying to do, was to ensure tha the IP interface the device was
      going to use was up.
      
      The only cases where the IP interface might *not* be up after stage2
      is where the IP interface is different than the device's interface,
      like for Bluetooth, ADSL, WWAN, and PPPoE.  Move the call to
      nm_platform_link_set_up() into nm_device_set_ip_iface() which all
      those device types will call.
      
      Thus, only the device types that really need to up their IP interface
      will do so, but other devices (including when activating assumed
      connections) that don't need to do this, won't do it.
      0e2457d7