1. 28 May, 2013 1 commit
    • Dan Williams's avatar
      settings: implement ability to add connections without saving them to disk · 8a79fb1d
      Dan Williams authored
      We don't always want to immediately write new connections to disk, to
      facilitate "runtime" or "temporary" connections where an interface's
      runtime config isn't backed by on-disk config.  Also, just because
      an interface's configuration is changed doesn't necessarily mean
      that new configuration should be written to disk either.
      
      Add D-Bus methods for adding new connections and for updating existing
      connections that don't immediately save the connection to disk.
      
      Also add infrastructure to indicate to plugins that the new connection
      shouldn't be immediately saved if the connection was added with the
      new method.
      8a79fb1d
  2. 27 May, 2013 1 commit
  3. 24 May, 2013 3 commits
  4. 20 May, 2013 2 commits
  5. 15 May, 2013 1 commit
    • Dan Williams's avatar
      core: ensure newly-created master interfaces are ready for activation · 8bab0c82
      Dan Williams authored
      Reverts part of
      
      2226a00c
      core: add a "default-unmanaged" setting for devices
      
      Newly-created master interfaces are in the UNAVAILABLE state, but if
      they were created in response to a slave connection being activated,
      the master must be activated immediately too.  But a device cannot
      be activated unless it's in the DISCONNECTED state, so restore that
      state change.
      8bab0c82
  6. 08 May, 2013 1 commit
  7. 07 May, 2013 2 commits
    • Dan Winship's avatar
      core, libnm-glib: add NMDeviceGeneric · ce4f2a4b
      Dan Winship authored
      Add NMDeviceGeneric, to provide generic support for unknown device
      types, and create NMDeviceGenerics for those devices that NM
      previously was ignoring. Allow NMSettingGeneric connections to be
      activated on (managed) NMDeviceGenerics.
      ce4f2a4b
    • Dan Winship's avatar
      core: add a "default-unmanaged" setting for devices · 2226a00c
      Dan Winship authored
      Allow devices to declare themselves unmanaged-by-default, but tweak
      nm-manager and nm-policy to allow activating matching connections on
      those devices anyway.
      
      (This ensures that NM keeps its hands completely off the device unless
      the user explicitly asks it to do something with it.)
      2226a00c
  8. 23 Apr, 2013 1 commit
    • Dan Williams's avatar
      core: fix memory leak · ef151c3f
      Dan Williams authored
      get_virtual_iface_name() returns an allocated interface name which
      we must free; that wasn't being done when attempting to find the
      interface for which a virtual interface needs to be created.  Also
      throw in a cleanup for the given-device-doesn't-exist case just to
      make it clearer when the interface name is freed.
      ef151c3f
  9. 19 Apr, 2013 1 commit
    • Martin Pitt's avatar
      Use %NULL macro in doc strings · 57a9fb3c
      Martin Pitt authored
      Mass-converted "NULL" to "%NULL" in docstrings with
      
        find -name '*.c'| xargs sed -i '/^ \*.*[^%]NULL/ s/NULL\b/%NULL/g'
      57a9fb3c
  10. 08 Apr, 2013 7 commits
  11. 03 Apr, 2013 1 commit
  12. 20 Mar, 2013 1 commit
  13. 13 Mar, 2013 1 commit
    • Dan Winship's avatar
      core: simplify/rename nm_device_connection_match_config() · 971bab01
      Dan Winship authored
      nm_device_connection_match_config() sounded more generic than it
      really was; rename it to nm_device_find_assumable_connection(), which
      is what it really does.
      
      There was also a lot of redundancy/cut+paste in the subclass
      implementations of connection_match_config(); Improve things by moving
      the looping-over-connections code into NMDevice itself, and also doing
      the general-device-compatibility and IP-config checking there, leaving
      the device subclasses to just verify L2 properties. Which most of them
      aren't doing...
      
      https://bugzilla.gnome.org/show_bug.cgi?id=693684
      971bab01
  14. 12 Mar, 2013 1 commit
  15. 11 Mar, 2013 1 commit
  16. 26 Feb, 2013 1 commit
  17. 15 Feb, 2013 1 commit
    • Dan Winship's avatar
      core: Update device activation for :carrier-detect · feeafb8c
      Dan Winship authored
      Add a "need_carrier" argument to nm_device_is_available(), to allow
      distinguishing between "device is not available", "device is fully
      available", and "device is available except for not having carrier".
      
      Adjust various parts of NMDevice and NMManager to allow for the
      possibility of activating a connection with :carrier-detect = "no" on
      a device with no carrier, and to avoid auto-disconnecting devices with
      :carrier-detect = "on-activate".
      
      https://bugzilla.gnome.org/show_bug.cgi?id=688284
      feeafb8c
  18. 13 Feb, 2013 1 commit
    • Dan Winship's avatar
      all: remove pointless NULL checks · d04f2863
      Dan Winship authored
      g_malloc(), etc, never return NULL, by API contract. Likewise, by
      extension, no other glib function ever returns NULL due to lack of
      memory. So remove lots of unnecessary checks (the vast majority of
      which would have immediately crashed had they ever run anyway, since
      g_set_error(), g_warning(), and nm_log_*() all need to allocate
      memory).
      
      https://bugzilla.gnome.org/show_bug.cgi?id=693678
      d04f2863
  19. 06 Feb, 2013 1 commit
    • Dan Williams's avatar
      rfkill: set kernel WiFi rfkill state to cached state on startup · 240f47c8
      Dan Williams authored
      Like we do when the user sets the Wireless Enabled property at
      runtime, ensure the kernel's softblock state is synced with the
      user's WiFi enable preference at startup.  This helps compensate
      for BIOSes that don't save rfkill state over reboots and ensures
      consistency of between startup and runtime Wireless Enabled
      property behavior.
      
      Suggested by John G.
      240f47c8
  20. 04 Feb, 2013 3 commits
    • Dan Williams's avatar
      core: ensure IP interface removal doesn't remove the NMDevice · 62bae8ac
      Dan Williams authored
      Some devices (namely PPPoE (pppX), ADSL (nasX, pppX), and
      mobile broadband (pppX, bnepX)) create a kernel netdevice for IP
      communication (called the "IP interface" in NM) as part of the
      connection process and thus the IP interface lifetime does not
      correspond to the NMDevice lifetime.  For these devices we must
      ignore removal events for the IP interface name otherwise the
      NMDevice would be removed.
      
      Caused by 8cce42f2.
      
      For example, this bug caused the NMDeviceBt to be removed when
      a PAN connection's bnepX interface went down in response to a
      terminated Bluetooth connection, which of course means that
      you can't restart the PAN connection as your phone is no longer
      in the NM device list.
      62bae8ac
    • Dan Williams's avatar
      core: only manage those bridges created by NetworkManager (rh #905035) · 17338069
      Dan Williams authored
      Until we handle bridges non-destructively, only manage bridges
      created by NM.  When quitting write out a file listing all
      bridges created by NM and a timestamp, and when starting read
      that file and if the timestamp is within 30 minutes, manage
      any bridge that was listed in that file.  This scheme, while
      not foolproof (eg, if NM crashes), should ensure that NM can
      recognize bridges it created if it's restarted.  The file
      is stored in /run or /var/run, which is cleaned each restart,
      ensuring that the state does not persist across reboots.
      
      If an automatic or user-initiated activation request for
      a bridge NM does not manage is received, that request is
      denied.  Only if the bridge interface does not yet exist, or
      was present in the managed bridges file, will an
      NMDeviceBridge be created and activation be possible.
      17338069
    • Dan Williams's avatar
      core: don't allow auto-activation of a master that has been disconnected · 2dac2cf5
      Dan Williams authored
      The master-activation code was ignoring whether or not the master device
      was inhibiting automatic connections.
      2dac2cf5
  21. 09 Jan, 2013 1 commit
  22. 19 Dec, 2012 1 commit
    • Dan Williams's avatar
      core: fix crash on device deactivation after 'pending' branch merge · 94d6074e
      Dan Williams authored
      Since the manager now tracks active connections, it needs to hold
      a reference to the active connection objects too.  The active
      connection teardown code was changed to release that reference
      (_active_connection_cleanup()) but the creation code was never
      changed to remove the bits that pass ownership over the initial
      reference to the NMDevice.  Fix that.
      94d6074e
  23. 17 Dec, 2012 6 commits