1. 30 Oct, 2020 8 commits
  2. 29 Oct, 2020 9 commits
  3. 28 Oct, 2020 5 commits
  4. 27 Oct, 2020 13 commits
  5. 26 Oct, 2020 1 commit
  6. 23 Oct, 2020 4 commits
    • Antonio Cardace's avatar
      l3cfg: fix typo in test · 983798d9
      Antonio Cardace authored
      Signed-off-by: Antonio Cardace's avatarAntonio Cardace <acardace@redhat.com>
      983798d9
    • Thomas Haller's avatar
      l3cfg: merge branch 'th/l3cfg-13' · b4ced8b9
      Thomas Haller authored
      !657
      b4ced8b9
    • Thomas Haller's avatar
      l3cfg: add support for IPv4 link local addresses (ipv4ll) to NML3Cfg · 17269b05
      Thomas Haller authored
      NML3Cfg already handles IPv4 ACD. IPv4LL is just a small additional
      layer on top of that, so it makes sense that it also is handled by
      NML3Cfg.
      
      Also, the overall goal is that multiple NMDevice and NMVpnConnection
      instances can cooperate independently. So if multiple "users" enable
      IPv4LL on an interface, then we should only run it once. This is
      achieved by NML3IPv4LL's API where users register what they want,
      and NML3IPv4LL figures out what that means as a whole.
      
      Also, we thus will no longer need to use sd_ipv4ll/n-ipv4ll, because
      we implement it ourself.
      17269b05
    • Thomas Haller's avatar
      l3cfg: combine NML3AcdAddrTrackInfo and AcdTrackData · 3caf419d
      Thomas Haller authored
      On the one hand, we want to keep the private fields internal. On the
      other hand, we want to directly expose the NML3AcdAddrTrackInfo, so
      that the user can access them without copying or calling a function.
      
      Previously, there was some union ugliness and some padding involved.
      That was probably correct, but lets solve this somewhat nicer by
      having the private fields in a "_priv" struct and use NML3AcdAddrTrackInfo
      throughout.
      3caf419d