1. 26 Jan, 2019 1 commit
  2. 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
  3. 12 Dec, 2018 1 commit
    • Ondřej Zajíček's avatar
      BGP: implement Adj-RIB-In · 682d3f7d
      Ondřej Zajíček authored
      The patch implements optional internal import table to a channel and
      hooks it to BGP so it can be used as Adj-RIB-In. When enabled, all
      received (pre-filtered) routes are stored there and import filters can
      be re-evaluated without explicit route refresh. An import table can be
      examined using e.g. 'show route import table bgp1.ipv4'.
      682d3f7d
  4. 04 Dec, 2018 1 commit
    • Jan Maria Matejka's avatar
      Terminology cleanup: The import_control hook is now called preexport. · 14375237
      Jan Maria Matejka authored
      Once upon a time, far far away, there were the old Bird developers
      discussing what direction of route flow shall be called import and
      export. They decided to say "import to protocol" and "export to table"
      when speaking about a protocol. When speaking about a table, they
      spoke about "importing to table" and "exporting to protocol".
      
      The latter terminology was adopted in configuration, then also the
      bird CLI in commit ea2ae6dd started to use it (in year 2009). Now
      it's 2018 and the terminology is the latter. Import is from protocol to
      table, export is from table to protocol. Anyway, there was still an
      import_control hook which executed right before route export.
      
      One thing is funny. There are two commits in April 1999 with just two
      minutes between them. The older announces the final settlement
      on config terminology, the newer uses the other definition. Let's see
      their commit messages as the git-log tool shows them (the newer first):
      
          commit 9e0e485e
          Author: Martin Mares <mj@ucw.cz>
          Date:   Mon Apr 5 20:17:59 1999 +0000
      
      	Added some new protocol hooks (look at the comments for better explanation):
      
      		make_tmp_attrs          Convert inline attributes to ea_list
      		store_tmp_attrs         Convert ea_list to inline attributes
      		import_control          Pre-import decisions
      
          commit 5056c559
          Author: Martin Mares <mj@ucw.cz>
          Date:   Mon Apr 5 20:15:31 1999 +0000
      
      	Changed syntax of attaching filters to protocols to hopefully the final
      	version:
      
      		EXPORT <filter-spec>    for outbound routes (i.e., those announced
      					by BIRD to the rest of the world).
      		IMPORT <filter-spec>    for inbound routes (i.e., those imported
      					by BIRD from the rest of the world).
      
      	where <filter-spec> is one of:
      
      		ALL                     pass all routes
      		NONE                    drop all routes
      		FILTER <name>           use named filter
      		FILTER { <filter> }     use explicitly defined filter
      
      	For all protocols, the default is IMPORT ALL, EXPORT NONE. This includes
      	the kernel protocol, so that you need to add EXPORT ALL to get the previous
      	configuration of kernel syncer (as usually, see doc/bird.conf.example for
      	a bird.conf example :)).
      
      Let's say RIP to this almost 19-years-old inconsistency. For now, if you
      import a route, it is always from protocol to table. If you export a
      route, it is always from table to protocol.
      
      And they lived happily ever after.
      14375237
  5. 20 Nov, 2018 1 commit
    • Ondřej Zajíček's avatar
      The MRT protocol · 863ecfc7
      Ondřej Zajíček authored
      The new MRT protocol is responsible for periodic RIB table dumps in the
      MRT format (RFC 6396). Also the existing code for BGP4MP MRT dumps is
      refactored and splitted between BGP to MRT protocols, will be more
      integrated into MRT in the future.
      
      Example:
      
      protocol mrt {
              table "*";
              filename "%N_%F_%T.mrt";
              period 60;
      }
      
      It is partially based on the old MRT code from Pavel Tvrdik.
      863ecfc7
  6. 31 Jul, 2018 1 commit
  7. 30 May, 2018 1 commit
    • Jan Maria Matejka's avatar
      Nest: Removing separate tmpa from route propagation · 13c0be19
      Jan Maria Matejka authored
      This is a fundamental change of an original (1999) concept of route
      processing inside BIRD. During import/export, there was a temporary
      ea_list created which was to be used instead of the another one inside
      the route itself.
      
      This led to some confusion, quirks, and strange filter code that handled
      extended route attributes. Dropping it now.
      
      The protocol interface has changed in an uniform way -- the
      `struct ea_list *attrs` argument has been removed from store_tmp_attrs(),
      import_control(), rt_notify() and get_route_info().
      13c0be19
  8. 29 May, 2018 1 commit
  9. 16 Jan, 2018 1 commit
  10. 10 Dec, 2017 1 commit
  11. 07 Dec, 2017 2 commits
  12. 19 Sep, 2017 1 commit
    • Ondřej Zajíček's avatar
      BGP: Shutdown communication (RFC 8203) · cd1d9961
      Ondřej Zajíček authored
      The patch implements BGP Administrative Shutdown Communication (RFC 8203)
      allowing BGP operators to pass messages related to BGP session
      administrative shutdown/restart. It handles both transmit and receive of
      shutdown messages. Messages are logged and may be displayed by show
      protocol all command.
      
      Thanks to Job Snijders for the basic patch.
      cd1d9961
  13. 12 Apr, 2017 1 commit
  14. 29 Mar, 2017 1 commit
  15. 26 Mar, 2017 1 commit
    • Ondřej Zajíček's avatar
      BGP: Support for routes with mixed-AF next hops · ef57b70f
      Ondřej Zajíček authored
      Covers IPv4/VPNv4 routes with IPv6 next hop (RFC 5549), IPv6 routes with
      IPv4 next hop (RFC 4798) and VPNv6 routes with IPv4 next hop (RFC 4659).
      Unfortunately it also makes next hop hooks more messy.
      
      Each BGP channel now could have two IGP tables, one for IPv4 next hops,
      the other for IPv6 next hops.
      ef57b70f
  16. 22 Mar, 2017 1 commit
    • Ondřej Zajíček's avatar
      BGP: Support for MPLS labels and VPN SAFI · 1e37e35c
      Ondřej Zajíček authored
      Basic support for SAFI 4 and 128 (MPLS labeled IP and VPN) for IPv4 and
      IPv6. Should work for route reflector, but does not properly handle
      originating routes with next hop self.
      
      Based on patches from Jan Matejka.
      1e37e35c
  17. 17 Mar, 2017 1 commit
  18. 23 Feb, 2017 1 commit
  19. 20 Feb, 2017 1 commit
  20. 19 Feb, 2017 1 commit
  21. 07 Feb, 2017 1 commit
  22. 24 Jan, 2017 1 commit
  23. 03 Jan, 2017 1 commit
  24. 20 Dec, 2016 1 commit
  25. 07 Dec, 2016 2 commits
  26. 25 Nov, 2016 1 commit
    • Ondřej Zajíček's avatar
      BGP: Fix memory leak in graceful restart code · ed1a908e
      Ondřej Zajíček authored
      Prefix and bucket tables are initialized when entering established state
      but not explicitly freed when leaving it (that is handled by protocol
      restart). With graceful restart, BGP may enter and leave established
      state multiple times without hard protocol restart causing memory leak.
      ed1a908e
  27. 01 Nov, 2016 1 commit
  28. 27 Oct, 2016 1 commit
  29. 03 Oct, 2016 1 commit
    • Ondřej Zajíček's avatar
      BGP: Support for large communities · 66dbdbd9
      Ondřej Zajíček authored
      Add support for large communities (draft-ietf-idr-large-community),
      96bit alternative to RFC 1997 communities.
      
      Thanks to Matt Griswold for the original patch.
      66dbdbd9
  30. 13 Apr, 2016 1 commit
    • Ondřej Zajíček's avatar
      BSD: Add the IPsec SA/SP database entries control · a7baa098
      Ondřej Zajíček authored
      Add code for manipulation with TCP-MD5 keys in the IPsec SA/SP database
      at FreeBSD systems. Now, BGP MD5 authentication (RFC 2385) keys are
      handled automatically on both Linux and FreeBSD.
      
      Based on patches from Pavel Tvrdik.
      a7baa098
  31. 18 Jul, 2015 1 commit
  32. 08 Jun, 2015 2 commits
  33. 29 Mar, 2015 1 commit
  34. 22 Feb, 2015 1 commit
  35. 21 Feb, 2015 1 commit
  36. 02 Oct, 2014 1 commit
  37. 20 Mar, 2014 1 commit
    • Ondřej Zajíček's avatar
      BGP graceful restart support. · 0c791f87
      Ondřej Zajíček authored
      Also significant core protocol state changes needed for that,
      global graceful restart recovery state and kernel proto support
      for recovery.
      0c791f87