1. 16 Dec, 2018 1 commit
    • Ondřej Zajíček's avatar
      BGP: Extend 'next hop keep' and 'next hop self' options · 1cab2b4a
      Ondřej Zajíček authored
      Extend 'next hop keep' and 'next hop self' options to have boolean values
      (enabled / disabled) and also values 'ibgp'/ 'ebgp' to restrict it to
      routes received from IBGP / EBGP. This allows to have it enabled by
      default in some cases, matches features of other implementations, and
      allows to handle some strange cases like EBGP border router with 'next
      hop self' also doing IBGP route reflecting.
      
      Change default of 'next hop keep' to enabled for route servers, and
      'ibgp' for route reflectors.
      
      Update documentation for these options.
      1cab2b4a
  2. 14 Dec, 2018 1 commit
  3. 12 Dec, 2018 2 commits
  4. 11 Dec, 2018 1 commit
  5. 06 Dec, 2018 1 commit
    • Maria Matejka's avatar
      Custom route attributes · 265419a3
      Maria Matejka authored
      For local route marking purposes, local custom route attributes may be
      defined. These attributes are seamlessly stripped after export filter to
      every real protocol like Kernel, BGP or OSPF, they however pass through
      pipes. We currently allow at most 256 custom attributes.
      
      This should be much faster than currently used bgp communities
      for marking routes.
      265419a3
  6. 04 Dec, 2018 3 commits
  7. 21 Nov, 2018 1 commit
  8. 05 Nov, 2018 1 commit
  9. 24 Aug, 2018 1 commit
  10. 21 Aug, 2018 1 commit
  11. 07 Aug, 2018 1 commit
  12. 31 Jul, 2018 1 commit
  13. 26 Jun, 2018 1 commit
  14. 24 May, 2018 1 commit
    • Ondřej Zajíček's avatar
      Do not initialize route metrics in import_control hook · feae132e
      Ondřej Zajíček authored
      During route export, the receiving protocol often initialized route
      metrics to default value in its import_control hook before export filter
      was executed. This is inconsistent with the expectation that an export
      filter would process the same route as one in the routing table and it
      breaks setting these metrics before (e.g. for static routes directly in
      static protocol).
      
      The patch removes the initialization of route metrics in import_control
      hook, the default values are already handled in rt_notify hook called
      after export filters.
      
      The patch also changed the behavior of OSPF to keep metrics when a route
      is reannounced between OSPF instances (to be consistent with other
      protocols) and the behavior when both ospf_metric1 and ospf_metric2
      are specified (to have more expected behavior).
      feae132e
  15. 03 May, 2018 1 commit
    • Ondřej Zajíček's avatar
      Babel: Add option to randomize router ID · 70fab178
      Ondřej Zajíček authored
      When a Babel node restarts, it loses its sequence number, which can cause
      its routes to be rejected by peers until the state is cleared out by other
      nodes in the network (which can take on the order of minutes).
      
      There are two ways to fix this: Having stable storage to keep the sequence
      number across restarts, or picking a different router ID each time.
      
      This implements the latter, by introducing a new option that will cause
      BIRD to randomize a high 32 bits of router ID every time it starts up.
      This avoids the problem at the cost of not having stable router IDs in
      the network.
      
      Thanks to Toke Hoiland-Jorgensen for the patch.
      70fab178
  16. 03 Apr, 2018 2 commits
  17. 24 Mar, 2018 1 commit
  18. 21 Mar, 2018 1 commit
  19. 20 Mar, 2018 1 commit
  20. 17 Mar, 2018 2 commits
  21. 08 Mar, 2018 1 commit
  22. 23 Jan, 2018 1 commit
  23. 16 Jan, 2018 1 commit
  24. 09 Jan, 2018 1 commit
  25. 03 Jan, 2018 1 commit
  26. 21 Dec, 2017 1 commit
  27. 13 Dec, 2017 1 commit
  28. 10 Dec, 2017 2 commits
  29. 08 Dec, 2017 1 commit
  30. 07 Dec, 2017 2 commits
  31. 10 Oct, 2017 3 commits