1. 26 Jun, 2018 2 commits
  2. 13 Jun, 2018 1 commit
  3. 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
  4. 29 May, 2018 1 commit
  5. 12 Apr, 2018 1 commit
  6. 16 Jan, 2018 2 commits
  7. 09 Jan, 2018 1 commit
  8. 02 Jan, 2018 2 commits
  9. 13 Dec, 2017 1 commit
  10. 10 Dec, 2017 1 commit
  11. 08 Dec, 2017 4 commits
  12. 07 Dec, 2017 5 commits
  13. 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
  14. 12 Sep, 2017 2 commits
  15. 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
  16. 16 May, 2017 1 commit
  17. 12 Apr, 2017 2 commits
  18. 29 Mar, 2017 2 commits
  19. 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
  20. 23 Mar, 2017 1 commit
  21. 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
  22. 17 Mar, 2017 1 commit
  23. 14 Mar, 2017 2 commits
  24. 24 Feb, 2017 1 commit
  25. 23 Feb, 2017 1 commit
  26. 20 Feb, 2017 1 commit