1. 09 Nov, 2018 1 commit
  2. 23 Oct, 2018 1 commit
  3. 26 Sep, 2018 1 commit
  4. 24 Sep, 2018 1 commit
  5. 18 Sep, 2018 3 commits
  6. 16 Sep, 2018 1 commit
    • Christof Schulze's avatar
      FIX: NO SUCH DEVICE when adding routes · da50f2a3
      Christof Schulze authored
      When adding unreachable routes and setting the RTNH_F_ONLINK flag, a
      device is required to be specified. In Linux kernel 4.16 support for
      this flag was added. Until now it was ignored.
      If RTNH_F_ONLINK is specified while the device is missing, newer kernels
      will respond with No such device.
      The result is:
      * spam in the log file
      * missing routes for both ipv4 and ipv6
      da50f2a3
  7. 29 Jun, 2018 1 commit
    • Juliusz Chroboczek's avatar
      Fix (non-exploitable) buffer-overflow in packet parser. · 8cbc75db
      Juliusz Chroboczek authored
      The check for a TLV going beyond the end of the packet was off by two.
      A malformed packet could possibly cause babeld to read two octets beyond
      the end of the read buffer.
      
      While technically a buffer overflow, this is most probably not
      exploitable, since it is a read-only overflow.  At worst, it would
      cause two octets of garbage to be parsed and treated as valid data.
      8cbc75db
  8. 12 May, 2018 1 commit
  9. 11 May, 2018 1 commit
  10. 07 Apr, 2018 1 commit
  11. 23 Feb, 2018 1 commit
  12. 31 Jan, 2018 3 commits
  13. 29 Jan, 2018 2 commits
  14. 23 Jan, 2018 1 commit
  15. 22 Jan, 2018 8 commits
  16. 11 Aug, 2017 1 commit
    • Juliusz Chroboczek's avatar
      Send requests when we lose a route. · 97cb759d
      Juliusz Chroboczek authored
      When we lose a route and have no feasible alternate, we should send requests
      straight away rather than waiting for a periodic update.  If we have an
      unfeasible route, send according to that route and resend, otherwise do
      a multicast.
      97cb759d
  17. 25 Jul, 2017 1 commit
  18. 20 Jul, 2017 9 commits
  19. 23 May, 2017 2 commits