1. 06 Oct, 2017 1 commit
  2. 04 Oct, 2017 1 commit
    • RAdv: Support for more specific routes (RFC 4191) · 2a95e633
      The patch implements Default Router Preferences and More-Specific Routes
      (RFC 4191) for RAdv protocol, allowing to announce router preference and
      more specific routes in router advertisements. Routes can be exported to
      RAdv like to regular routing protocols.
      Some cleanups, bugfixes and other changes done by Ondrej Zajicek.
      Michal 'vorner' Vaner authored
  3. 20 Sep, 2017 1 commit
  4. 19 Sep, 2017 2 commits
  5. 13 Sep, 2017 1 commit
  6. 12 Sep, 2017 2 commits
  7. 06 Sep, 2017 1 commit
    • Basic VRF support · 943478b0
      Add basic VRF (virtual routing and forwarding) support. Protocols can be
      associated with VRFs, such protocols will be restricted to interfaces
      assigned to the VRF (as reported by Linux kernel) and will use sockets
      bound to the VRF. E.g., different multihop BGP instances can use diffent
      kernel routing tables to handle BGP TCP connections.
      The VRF support is preliminary, currently there are several limitations:
      - Recent Linux kernels (4.11) do not handle correctly sockets bound
      to interaces that are part of VRF, so most protocols other than multihop
      BGP do not work. This will be fixed by future kernel versions.
      - Neighbor cache ignores VRFs. Breaks config with the same prefix on
      local interfaces in different VRFs. Not much problem as single hop
      protocols do not work anyways.
      - Olock code ignores VRFs. Breaks config with multiple BGP peers with the
      same IP address in different VRFs.
      - Incoming BGP connections are not dispatched according to VRFs.
      Breaks config with multiple BGP peers with the same IP address in
      different VRFs. Perhaps we would need some kernel API to read VRF of
      incoming connection? Or probably use multiple listening sockets in
      int-new branch.
      - We should handle master VRF interface up/down events and perhaps
      disable associated protocols when VRF goes down. Or at least disable
      associated interfaces.
      - Also we should check if the master iface is really VRF iface and
      not some other kind of master iface.
      - BFD session request dispatch should be aware of VRFs.
      - Perhaps kernel protocol should read default kernel table ID from VRF
      iface so it is not necessary to configure it.
      - Perhaps we should have per-VRF default table.
      Ondřej Zajíček authored
  8. 05 Sep, 2017 1 commit
  9. 04 Sep, 2017 3 commits
  10. 30 Aug, 2017 4 commits
  11. 22 Aug, 2017 1 commit
  12. 10 Aug, 2017 2 commits
  13. 09 Aug, 2017 5 commits
  14. 19 Jun, 2017 1 commit
  15. 31 May, 2017 1 commit
  16. 30 May, 2017 1 commit
  17. 25 May, 2017 1 commit
  18. 23 May, 2017 1 commit
  19. 18 May, 2017 1 commit
  20. 17 May, 2017 4 commits
  21. 16 May, 2017 4 commits
  22. 14 Mar, 2017 1 commit
    • Some autoconf cleanups · 7a855725
      The patch allows to use autoreconf, replaces some long obsolete
      constructs and does some other minor cleanups. Also, the file
      configure.in is renamed to configure.ac, as the old name has been
      deprecated for a long time.
      Thanks to Ruben Kerkhof for the patchset.
      Ondřej Zajíček authored