1. 28 Nov, 2018 1 commit
    • Ondřej Zajíček's avatar
      Nest: Do not hard-reset interface when preferred address is changed · e2ae0869
      Ondřej Zajíček authored
      Modify protocols to use preferred address change notification instead on
      depending on hard-reset of interfaces in that case, and remove hard-reset
      in that case. This avoids issue when e.g. IPv6 protocol restarts
      interface when IPv4 preferred address changed (as hard-reset is
      unavoidable and common for whole iface).
      
      The patch also fixes a bug when removing last address does not send
      preferred address change notification.
      e2ae0869
  2. 05 Nov, 2018 1 commit
  3. 11 Oct, 2018 1 commit
  4. 07 Feb, 2018 1 commit
  5. 16 Dec, 2017 1 commit
  6. 10 Dec, 2017 1 commit
  7. 08 Dec, 2017 1 commit
  8. 07 Dec, 2017 1 commit
  9. 17 Oct, 2017 1 commit
  10. 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
  11. 10 Aug, 2017 2 commits
  12. 01 Nov, 2016 1 commit
  13. 01 Feb, 2016 1 commit
  14. 21 Dec, 2015 1 commit
  15. 20 Dec, 2015 1 commit
  16. 12 Nov, 2015 1 commit
  17. 03 Nov, 2014 1 commit
    • Ondřej Zajíček's avatar
      Changes order of iface/addr/neigh event hooks. · f92e6ab3
      Ondřej Zajíček authored
      Now the order is:
      
      Up   -> iface, addr, neigh
      Down -> neigh, addr, iface
      
      It fixes the case when an iface appears, related static routes are
      activated and exported to OSPF before the iface notification and
      therefore forwarding addresses are not encoded in generated external
      LSAs.
      f92e6ab3
  18. 24 Nov, 2013 1 commit
  19. 16 Apr, 2013 1 commit
  20. 27 Dec, 2012 1 commit
    • Ondřej Zajíček's avatar
      Implements interface masks for choosing router id. · 79b4e12e
      Ondřej Zajíček authored
      Router ID could be automatically determined based of subset of
      ifaces/addresses specified by 'router id from' option. The patch also
      does some minor changes related to router ID reconfiguration.
      
      Thanks to Alexander V. Chernikov for most of the work.
      79b4e12e
  21. 23 Jan, 2012 2 commits
  22. 21 Jan, 2012 1 commit
  23. 01 Jan, 2012 1 commit
  24. 12 Dec, 2011 1 commit
  25. 01 May, 2011 1 commit
  26. 28 Mar, 2011 1 commit
    • Ondřej Zajíček's avatar
      Minor changes in addresses. · 52a43ae3
      Ondřej Zajíček authored
      Mainly changes IA_UNNUMBERED to IA_PEER and adds IA_HOST. Also do not
      show broadcast addr in show interfaces. Nobody cares for that.
      52a43ae3
  27. 22 Dec, 2010 1 commit
  28. 11 Nov, 2010 2 commits
  29. 19 Mar, 2010 1 commit
  30. 14 Mar, 2010 1 commit
  31. 27 Feb, 2010 1 commit
    • Ondřej Zajíček's avatar
      Better flushing of interfaces. · 53434e44
      Ondřej Zajíček authored
      When device protocol goes down, interfaces should be flushed
      asynchronously (in the same way like routes from protocols are flushed),
      when protocol goes to DOWN/HUNGRY.
      
      This fixes the problem with static routes staying in kernel routing
      table after BIRD shutdown.
      53434e44
  32. 29 May, 2009 1 commit
  33. 06 May, 2009 1 commit
    • Ondřej Zajíček's avatar
      A change in OSPF and RIP interface patterns. · 20e94fb8
      Ondřej Zajíček authored
      Allows to add more interface patterns to one common 'options'
      section like:
      
      interface "eth3", "eth4" { options common to eth3 and eth4 };
      
      Also removes undocumented and unnecessary ability to specify
      more interface patterns with different 'options' sections:
      
      interface "eth3" { options ... }, "eth4" { options ... };
      20e94fb8
  34. 22 Feb, 2003 1 commit
  35. 08 Nov, 2000 2 commits
  36. 05 Jun, 2000 1 commit