1. 24 Mar, 2018 1 commit
  2. 21 Mar, 2018 1 commit
  3. 20 Mar, 2018 1 commit
  4. 17 Mar, 2018 2 commits
  5. 08 Mar, 2018 1 commit
  6. 23 Jan, 2018 1 commit
  7. 16 Jan, 2018 1 commit
  8. 09 Jan, 2018 1 commit
  9. 03 Jan, 2018 1 commit
  10. 21 Dec, 2017 1 commit
  11. 13 Dec, 2017 1 commit
  12. 10 Dec, 2017 2 commits
  13. 08 Dec, 2017 1 commit
  14. 07 Dec, 2017 2 commits
  15. 10 Oct, 2017 4 commits
  16. 13 Sep, 2017 1 commit
  17. 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
  18. 30 Aug, 2017 2 commits
  19. 09 Jun, 2017 1 commit
  20. 29 Apr, 2017 1 commit
  21. 26 Apr, 2017 2 commits
  22. 25 Apr, 2017 1 commit
    • Ondřej Zajíček's avatar
      Nest: Update of show route cmd · b2949999
      Ondřej Zajíček authored
      Some code cleanup, multiple bugfixes, allows to specify also channel
      for 'show route export'. Interesting how such apparenty simple thing
      like show route cmd has plenty of ugly corner cases.
      b2949999
  23. 12 Apr, 2017 1 commit
  24. 29 Mar, 2017 2 commits
  25. 22 Mar, 2017 1 commit
  26. 14 Mar, 2017 2 commits
  27. 13 Mar, 2017 1 commit
  28. 08 Mar, 2017 1 commit
  29. 23 Feb, 2017 1 commit
  30. 20 Feb, 2017 1 commit