1. 09 Jan, 2018 1 commit
  2. 16 Dec, 2017 1 commit
  3. 10 Dec, 2017 1 commit
  4. 08 Dec, 2017 1 commit
  5. 07 Dec, 2017 6 commits
  6. 10 Oct, 2017 4 commits
  7. 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
  8. 23 May, 2017 1 commit
  9. 29 Apr, 2017 1 commit
  10. 08 Mar, 2017 1 commit
  11. 20 Feb, 2017 1 commit
  12. 22 Dec, 2016 3 commits
  13. 15 Dec, 2016 1 commit
    • Ondřej Zajíček's avatar
      OSPF: Fix ECMP external merging · 7d95c445
      Ondřej Zajíček authored
      The variable nfa is not cleaned before each loop iteration and can have
      a wrong value of nfa.nhs_reuse from the previous step.
      
      Thanks to Bernardo Figueiredo for the bugreport and analysis.
      7d95c445
  14. 13 Dec, 2016 1 commit
    • Ondřej Zajíček's avatar
      OSPF: Fix net-summary origination combined with stubnet option · 9e7d3a78
      Ondřej Zajíček authored
      Stubnet nodes in OSPF FIB were removed during rt_sync(), but the pointer
      remained in top_hash_entry.nf, so net-summary LSA origination was
      confused, reported 'LSA ID collision' and net-summary LSAs were not
      originated properly.
      
      Thanks to Naveen Chowdary Yerramneni for bugreport and analysis.
      9e7d3a78
  15. 09 Nov, 2016 1 commit
    • Ondřej Zajíček's avatar
      Unit Testing for BIRD · 9b0a0ba9
      Ondřej Zajíček authored
       - Unit Testing Framework (BirdTest)
       - Integration of BirdTest into the BIRD build system
       - Tests for several BIRD modules
      
       Based on squashed Pavel Tvrdik's int-test branch, updated for
       current int-new branch.
      9b0a0ba9
  16. 08 Nov, 2016 1 commit
  17. 02 Nov, 2016 2 commits
  18. 01 Nov, 2016 1 commit
  19. 17 May, 2016 1 commit
  20. 12 May, 2016 1 commit
  21. 10 May, 2016 1 commit
  22. 08 Apr, 2016 1 commit
  23. 07 Apr, 2016 1 commit
  24. 23 Mar, 2016 2 commits
    • Ondřej Zajíček's avatar
      OSPF: Fix bogus LSA ID collisions between received and originated LSAs · 39a6b19d
      Ondřej Zajíček authored
      After restart, LSAs locally originated by the previous instance are
      received from neighbors. They are installed to LSA db and flushed. If
      export of a route triggers origination of a new external LSA before flush
      of the received one is complete, the check in ospf_originate_lsa() causes
      origination to fail (because en->nf is NULL for the old LSA and non-NULL
      for the new LSA). The patch fixes this by updating the en->nf for LSAs
      being flushed (as is already done for empty ones). Generally, en->nf
      field deserves some better description in the code.
      
      Thanks to Jigar Mehta for analyzing the problem.
      39a6b19d
    • Ondřej Zajíček's avatar
      OSPF: Fix reading from freed memory · a459f4df
      Ondřej Zajíček authored
      Thanks to Pavel Tvrdik for noticing it.
      a459f4df
  25. 25 Feb, 2016 1 commit
  26. 01 Feb, 2016 1 commit
  27. 11 Jan, 2016 1 commit
  28. 29 Dec, 2015 1 commit