1. 05 Jan, 2015 2 commits
  2. 19 Nov, 2014 2 commits
  3. 07 Nov, 2014 6 commits
    • Dan Williams's avatar
      iface-helper: add nm-iface-helper for dynamic configure-then-quit support · 5149fd12
      Dan Williams authored
      When quitting, the Manager asks each device to spawn the interface helper,
      which persists and manages dynamic address on the interface after NetworkManager
      is gone.  If the dynamic address cannot be maintaned, the helper quits and
      the interface's address may be removed when their lifetime runs out.
      To keep the helper as simple as possible, NetworkManager passes most of the
      configuration on the command-line, including some properties of the device's
      current state, which are necessary for the helper to maintain DHCP leases
      or IPv6 SLAAC addresses.
    • Dan Williams's avatar
    • Dan Williams's avatar
      dhcp: move D-Bus DHCP listener into separate class · 0b98dc43
      Dan Williams authored
      This simplifies the manager and ensures that only the clients
      that use D-Bus-based DHCP helpers need to care about them.
    • Dan Williams's avatar
      core: split signal/pidfile/option handling into separate source file · ee255036
      Dan Williams authored
      We'll use this from more than one spot.
    • Thomas Haller's avatar
      policy: add manager for default routes and support multiple default routes · e8824f6a
      Thomas Haller authored
      Up to now, NMPolicy would iterate over all devices to find the "best"
      device and assign the default route to that device.
      A better approach is to add a default route to *all* devices that
      are never-default=no. The relative priority is choosen according to
      the route metrics.
      If two devices receive the same metric, we want to prefer the device
      that activates first. That way, the default route sticks to the same
      device until a better device activates or the device deactivates.
      Hence, the order of activation is imporant in this case (as it is
      already now).
      Also, if several devices have identical metrics, increment their
      metrics so that every metric is unique.
      This makes the routing deterministic according to what we choose as best
      A special case is assumed devices. In this case we cannot adjust the metric
      in face of equal metrics.
      Add a new singleton class NMDefaultRouteManager that has a list of all
      devices and their default routes. The manager will order the devices by
      their priority and configure the routes using platform.
      Also update the metric for VPN connections. Later we will track VPN
      routes also via NMDefaultRouteManager. For now, fix the VPN metric because
      otherwise VPNs would always get metric 1024 (which is usually much larger then the
      device metrics).
      https://bugzilla.gnome.org/show_bug.cgi?id=735512Signed-off-by: Thomas Haller's avatarThomas Haller <thaller@redhat.com>
    • Dan Williams's avatar
      dhcp: add systemd-based "internal" DHCP client · d2dd3b2c
      Dan Williams authored
      We must also remove -Waggregate-return from m4/compiler-warnings.m4 because systemd
      uses aggregate return (correctly) in a couple cases, and we cannot keep single-level
      makefiles and override aggregate-return only for the systemd sub-library.
      This client currently only supports DHCPv4 because the base systemd code
      does not yet fully support DHCPv6.
  4. 22 Oct, 2014 3 commits
  5. 29 Sep, 2014 2 commits
  6. 11 Sep, 2014 13 commits
  7. 06 Aug, 2014 1 commit
  8. 01 Aug, 2014 2 commits
    • Dan Winship's avatar
      libnm: add NetworkManager.h, disallow including individual headers · d0b05b34
      Dan Winship authored
      Add NetworkManager.h, which includes all of the other NM header, and
      require all external users of libnm to use that rather than the
      individual headers.
      (An exception is made for nm-dbus-interface.h,
      nm-vpn-dbus-interface.h, and nm-version.h, which can be included
    • Dan Winship's avatar
      all: port everything to libnm · a7c4d53d
      Dan Winship authored
      Since the API has not changed at this point, this is mostly just a
      matter of updating Makefiles, and changing references to the library
      name in comments.
      NetworkManager cannot link to libnm due to the duplicated type/symbol
      names. So it links to libnm-core.la directly, which means that
      NetworkManager gets a separate copy of that code from libnm.so.
      Everything else links to libnm.
  9. 31 Jul, 2014 1 commit
  10. 30 Jul, 2014 1 commit
    • Dan Winship's avatar
      core: merge src/config, src/logging, src/posix-signals into src/ · 8aa3b985
      Dan Winship authored
      Some subdirectories of src/ encapsulate large chunks of functionality,
      but src/config/, src/logging/, and src/posix-signals/ are really only
      separated out because they used to be built into separate
      sub-libraries that were needed either for test programs, or to prevent
      circular dependencies. Since this is no longer relevant, simplify
      things by moving their files back into the main source directory.
  11. 23 Jul, 2014 2 commits
    • Dan Winship's avatar
      config: drop NMConfigDevice, use NMDevice directly · 7da97fc6
      Dan Winship authored
      NMConfigDevice was added because in the 0.9.8 days, when each subdir
      of src/ was compiled separately, it was impossible to make src/config/
      depend on src/devices/ because of circular dependencies.
      Since now everything gets compiled into a single libNetworkManager.la,
      this is no longer a problem, and so NMConfigDevice is just an
      unnecessary complication.
    • Dan Winship's avatar
      core: fix libndp linking · 4308a830
      Dan Winship authored
      We were linking libndp into the NetworkManager binary, but it ought to
      be marked as a dependency of libNetworkManager, in case a test
      exercises that code.
  12. 22 Jul, 2014 1 commit
  13. 15 Jul, 2014 2 commits
  14. 27 Jun, 2014 2 commits