1. 24 Jan, 2019 1 commit
  2. 14 Dec, 2018 1 commit
  3. 04 Dec, 2018 2 commits
  4. 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
  5. 25 Oct, 2018 1 commit
  6. 01 Oct, 2018 1 commit
  7. 18 Sep, 2018 1 commit
    • Jan Maria Matejka's avatar
      No more warnings ... · d4cebc6b
      Jan Maria Matejka authored
      no more warnings
      No more warnings over me
      And while it is being compiled all the log is black and white
      Release BIRD now and then let it flee
      
      (use the melody of well-known Oh Freedom!)
      d4cebc6b
  8. 22 Aug, 2018 1 commit
    • Jan Maria Matejka's avatar
      Lib: recursive printf · 64c5ad58
      Jan Maria Matejka authored
      Use like this:
      
      void func(const char *msg, va_list args) {
        ...
        bvsnprintf(buf, len, "file %s, line %d: %V (foo %d, bar %d)", file, line, msg, &args, foo, bar);
        ...
      }
      64c5ad58
  9. 28 Jul, 2018 1 commit
    • Ondřej Zajíček's avatar
      BSD: Use MSG_DONTROUTE for unicast packets on FreeBSD · 318acb0f
      Ondřej Zajíček authored
      BSD systems cannot use SO_DONTROUTE, because it does not work properly
      with multicast packets (perhaps it tries to find iface based on multicast
      group address). But we can use MSG_DONTROUTE sendmsg() flag for unicast
      packets. Works on FreeBSD, is ignored on OpenBSD and is broken on NetBSD
      (i guess due to integrated routing table and ARP table).
      318acb0f
  10. 27 Jun, 2018 1 commit
  11. 26 Jun, 2018 1 commit
  12. 29 May, 2018 1 commit
  13. 16 May, 2018 1 commit
  14. 13 Feb, 2018 1 commit
    • Ondřej Zajíček's avatar
      Add support for source-specific IPv6 routes to BIRD core · be17805c
      Ondřej Zajíček authored
      This patch adds support for source-specific IPv6 routes to BIRD core.
      This is based on Dean Luga's original patch, with the review comments
      addressed. SADR support is added to network address parsing in confbase.Y
      and to the kernel protocol on Linux.
      
      Currently there is no way to mix source-specific and non-source-specific
      routes (i.e., SADR tables cannot be connected to non-SADR tables).
      
      Thanks to Toke Hoiland-Jorgensen for the original patch.
      Minor changes by Ondrej Santiago Zajicek.
      be17805c
  15. 07 Feb, 2018 1 commit
  16. 10 Jan, 2018 1 commit
  17. 14 Dec, 2017 1 commit
  18. 13 Dec, 2017 1 commit
  19. 12 Dec, 2017 2 commits
  20. 10 Dec, 2017 3 commits
  21. 07 Dec, 2017 10 commits
  22. 12 Sep, 2017 1 commit
  23. 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
  24. 23 May, 2017 1 commit
  25. 19 May, 2017 1 commit
  26. 16 May, 2017 2 commits