1. 01 Jun, 2018 5 commits
  2. 31 May, 2018 18 commits
  3. 30 May, 2018 2 commits
  4. 29 May, 2018 11 commits
  5. 28 May, 2018 4 commits
    • Aleksander Morgado's avatar
      policy: don't block connection if device is gone · d97eab6c
      Aleksander Morgado authored
      If the active connection is deactivated because the device is gone,
      don't block autoconnection. Otherwise, whenever the device comes
      back (e.g. maybe it was reset in the middle of a connection attempt),
      the autoconnection logic won't be triggered, as the settings are still
      I'm able to reproduce this by performing a WWAN modem reset in the
      middle of a connection attempt.
    • Thomas Haller's avatar
      clients/tests: run nmcli commands in parallel · baaab522
      Thomas Haller authored
      Most nmcli calls from clients/tests don't change the server's state.
      Hence, they can easily run in parallel.
      Run tests in parallel. No longer handle one nmcli invocation after the other.
      Instead, spawn groups of processes in parallel, and track the pending jobs.
      Only at certain synchronization points we call self.async_wait() to
      wait for all previous jobs to complete.
      This reduces the test time on my machine from 7 to 3 seconds. Arguably,
      that matters less during a full `make check -j 8`, because the entire
      set of tests anyway takes longer than 7 seconds. So when running the
      entire test suite, the machine is kept busy anyway. It matters however
      for manual invocations.
    • Thomas Haller's avatar
    • Thomas Haller's avatar
      all: add stable-id specifier "${DEVICE}" · eb821ead
      Thomas Haller authored
      Add new stable-id specifier "${DEVICE}" to explicitly declare that the
      connection's identity differs per-device.
      Note that for settings like "ipv6.addr-gen-mode=stable" we already hash
      the interface's name. So, in combination with addr-gen-mode, using this
      specifier has no real use. But for example, we don't do that for
      Point being, in various context we possibly already include a per-device
      token into the generation algorithm. But that is not the case for all
      contexts and uses.
      Especially the DHCPv4 client identifier is supposed to differ between interfaces
      (according to RFC). We don't do that by default with "ipv4.dhcp-client-id=stable",
      but with "${DEVICE}" can can now be configured by the user.
      Note that the fact that the client-id is the same accross interfaces, is not a
      common problem, because profiles are usually restricted to one device via