1. 21 Nov, 2018 1 commit
  2. 05 Nov, 2018 1 commit
  3. 17 Jul, 2018 2 commits
  4. 23 Apr, 2018 1 commit
  5. 24 Mar, 2018 2 commits
  6. 21 Mar, 2018 2 commits
  7. 10 Oct, 2017 3 commits
  8. 13 Sep, 2017 1 commit
  9. 06 Sep, 2017 1 commit
    • Ondřej Zajíček's avatar
      Basic VRF support · 943478b0
      Ondřej Zajíček authored
      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.
      943478b0
  10. 30 Aug, 2017 2 commits
  11. 14 Mar, 2017 1 commit
  12. 23 Feb, 2017 1 commit
  13. 19 Feb, 2017 1 commit
  14. 02 Nov, 2016 2 commits
  15. 12 Oct, 2016 2 commits
  16. 11 Oct, 2016 12 commits
  17. 04 Oct, 2016 1 commit
  18. 29 Sep, 2016 1 commit
  19. 21 Sep, 2016 1 commit
  20. 19 Sep, 2016 1 commit
    • Ondřej Zajíček's avatar
      KRT: Add krt_scope attribute · 6e75d0d2
      Ondřej Zajíček authored
      Add a new route attribute, krt_scope, to expose the Linux kernel route
      scope. Constants from /etc/iproute2/rt_scopes (prefixed by "ips_") are
      expected to be used with the attribute. Both import and export are
      supported.
      
      Also, the patch fixes device route export to the kernel, by setting link
      scope automatically.
      6e75d0d2
  21. 15 Sep, 2016 1 commit
    • Ondřej Zajíček's avatar
      KRT: Add kernel metric protocol option · 4adcb9df
      Ondřej Zajíček authored
      Kernel routes with different metrics do not clash with each other,
      therefore using dedicated metric value is a reliable way to avoid
      overwriting routes from other sources (e.g. kernel device routes).
      
      Although kernel route metric could already be set as a route attribute by
      filters, that is not consistent with the way how Linux kernel handles
      route metric - not just a route attribute, but a part of a route key.
      4adcb9df