1. 10 Aug, 2015 5 commits
  2. 24 Jul, 2015 1 commit
    • Dan Winship's avatar
      introspection: trivial fixes · d040fd18
      Dan Winship authored
      Add some missing files to libnmdbus.la. Add missing name-fixing
      annotations to the XML to make all generated NMDBus types match the
      names of their corresponding NM types.
  3. 10 Jun, 2015 1 commit
  4. 09 Jun, 2015 2 commits
  5. 13 May, 2015 1 commit
  6. 06 May, 2015 1 commit
    • Dan Williams's avatar
      vlan: don't fail if parent isn't found at construct time for existing devices · cd3df12c
      Dan Williams authored
      For existing devices, depending on the order that netlink sends interfaces to
      us, the parent may be found after the VLAN interface and not be available when
      the VLAN interface is constructed.  Instead of failing construction, when a
      NMDeviceVlan has no parent keep it unavailable for activation.  Then have
      the Manager notify existing devices when a new device is found, and let
      NMDeviceVlan find the parent later and become available via that mechanism.
      This doesn't apply to VLANs created by NM itself, because the kernel requires
      a parent ifindex when creating a VLAN device.  Thus this fix only applies to
      VLANs created outside NetworkManager, or existing when NM starts up.
  7. 29 Apr, 2015 1 commit
  8. 20 Apr, 2015 1 commit
  9. 13 Apr, 2015 1 commit
  10. 08 Apr, 2015 1 commit
  11. 24 Feb, 2015 1 commit
  12. 24 Nov, 2014 1 commit
  13. 07 Nov, 2014 1 commit
    • Dan Winship's avatar
      libnm-core, libnm, core: add AddressData and RouteData properties · d16905df
      Dan Winship authored
      Add AddressData and RouteData properties to NMSettingIPConfig and
      NMIP[46]Config. These are like the existing "addresses" and "routes"
      properties, but using strings and containing additional attributes,
      like NMIPAddress and NMIPRoute.
      This only affects the D-Bus representations; there are no API changes
      to NMSettingIP{,4,6}Config or NMIP{4,6}Config as a result of this; the
      additional information is just added to the existing 'addresses' and
      'routes' properties.
      NMSettingIP4Config and NMSettingIP6Config now always generate both
      old-style data ('addresses', 'address-labels', 'routes') and new-style
      data ('address-data', 'gateway', 'route-data') when serializing to
      D-Bus, for backward compatibility. When deserializing, they will fill
      in the 'addresses' and 'routes' properties from the new-style data if
      it is present (ignoring the old-style data), or from the old-style
      data if the new-style isn't present.
      The daemon-side NMIP4Config and NMIP6Config always emit changes for
      both 'Addresses'/'Routes' and 'AddressData'/'RouteData'. The
      libnm-side classes initially listen for changes on both properties,
      but start ignoring the 'Addresses' and 'Routes' properties once they
      know the daemon is also providing 'AddressData' and 'RouteData'.
  14. 27 Oct, 2014 1 commit
    • Dan Williams's avatar
      core: autoconnect fixes for default-unmanaged devices and property notification · d147c265
      Dan Williams authored
      Previously the only thing preventing default-unmanaged devices from
      being auto-activated was luck and the fact that they didn't have any
      available connections when in the UNMANAGED state.  That's no longer
      true, so we must be more explicit about their behavior.
      Furthermore it makes no sense to allow default-unmanaged devices
      to set priv->autoconnect=TRUE since that is never supposed to
      happen, so enforce that both in NM itself and if the change
      request comes in over the D-Bus interface.
      Lastly, internal priv->autoconnect=TRUE changes never emitted a
      property change notification, meaning the NMPolicy would never
      schedule an autoconnect check if the device's priv->autoconnect
      was set to TRUE as a result of re-activating or waking from sleep.
  15. 23 Oct, 2014 1 commit
    • Allison Lortie's avatar
      core: add PrimaryConnectionType property to NMManager (bgo #739080) · 07dba254
      Allison Lortie authored
      This will provide an extremely easy way for applications to find out
      what type of connection the system is currently using.  They might want
      to do this to avoid using data if a phone is on a 3G connection, for
      Having this as a separate property provides at least two advantages:
       1) it reduces code complexity for those wanting only this one simple
          piece of information
       2) we could allow access to this property (but nothing else) to
          privilege-separated applications in the future
      This patch adds the missing nm_active_connection_get_connection_type()
      which was in the header file but never actually implemented.
  16. 22 Oct, 2014 1 commit
    • Dan Winship's avatar
      libnm-core, core: move NMManagerError to nm-errors · 862d4efe
      Dan Winship authored
      Move the definition of NMManagerError to nm-errors, register it with
      D-Bus, and verify in the tests that it maps correctly.
      consistency. NM_MANAGER_ERROR_UNMANAGED_DEVICE is dropped since that
      name doesn't really describe the one place it was previously used in.
      NM_MANAGER_ERROR_SYSTEM_CONNECTION is dropped because it was't being
      it can be replaced with an NM_CONNECTION_ERROR.
      NM_MANAGER_ERROR_AUTOCONNECT_NOT_ALLOWED is turned into the more
      Also, remove the <tp:possible-errors> sections from nm-manager.xml,
      since they were completely out of date.
  17. 05 Oct, 2014 1 commit
  18. 26 Sep, 2014 1 commit
  19. 18 Sep, 2014 1 commit
    • Dan Winship's avatar
      libnm: port to GDBus · 6793a32a
      Dan Winship authored
      Port libnm-core/libnm to GDBus.
      The NetworkManager daemon continues to use dbus-glib; the
      previously-added connection hash/variant conversion methods are now
      moved to NetworkManagerUtils (along with a few other utilities that
      are now only needed by the daemon code).
  20. 05 Sep, 2014 1 commit
  21. 23 Jul, 2014 1 commit
    • Dan Williams's avatar
      ppp: add IPv6 support · 75fa46bd
      Dan Williams authored
      Add support for IPv6 to the pppd plugin and return the interface identifiers
      to NetworkManager.  Use those to construct the IPv6LL addresses for the
      PPP interface and the peer.
  22. 22 Jul, 2014 1 commit
  23. 15 Jul, 2014 1 commit
  24. 12 May, 2014 1 commit
  25. 07 May, 2014 2 commits
    • Dan Williams's avatar
      wwan: disable autoconnect if the given SIM PIN was wrong · d0430941
      Dan Williams authored
      If the given PIN was wrong, we really don't want to try that PIN
      again automatically because it might lock the SIM.  To ensure that
      doesn't happen, disable autoconnect so that the user must manually
      request reconnection.
      (this doesn't fix auto-connect-with-a-wrong-PIN completely, as
      autoconnect is reset when resuming from sleep, but it's a start)
    • Dan Williams's avatar
      wwan: use modem states instead of enabled/connected properties · 60804250
      Dan Williams authored
      Determining when the NMDeviceModem is available and when different
      connections are available is easier if the modem's state is tracked,
      instead of using the separate Enabled and Connected properties.
      These properties could not accurately represent the SIM lock state
      and prevented NetworkManager from making the modem available for
      auto-activation when locked, even if a PIN was available.
      In this new scheme, the NMDeviceModem is UNAVAILABLE when the
      ModemManager modem state is FAILED, UNKNOWN, or INITIALIZING.  It
      transitions to the NM DISCONNECTED state when the modem has finished
      initializing and has not failed.
      Once the NMDeviceModem is in DISCONNECTED state it can be activated
      even if the SIM is locked and a PIN is required; the PIN will be
      requested when starting activation, either from the connection itself
      or via a secrets request.  This makes auto-activation of WWAN
      connections possible.
      This also allows us to consolidate code dealing with modem enable/disable
      into the base NMModem class using the modem state, and to log more modem
      information for debugging purposes.
  26. 25 Apr, 2014 1 commit
  27. 03 Apr, 2014 1 commit
  28. 06 Mar, 2014 1 commit
    • Dan Winship's avatar
      platform, devices: add support for vxlan devices · 42df06e5
      Dan Winship authored
      Since vxlan is new-ish, and vxlan IPv6 support in particular has only
      been in the kernel since 3.11, we include our own copy of the vxlan
      netlink constants rather than depending on the installed headers.
  29. 05 Mar, 2014 1 commit
  30. 27 Jan, 2014 1 commit
  31. 23 Jan, 2014 4 commits