1. 06 Oct, 2015 1 commit
  2. 17 Sep, 2015 1 commit
  3. 16 Sep, 2015 1 commit
    • Tomek Mrugalski's avatar
      [3981] Changes after review: · bd35732a
      Tomek Mrugalski authored
       - Explanation why are we not updating assigned-addresses
       - DHCP4_DECLINE_LEASE message reworded as suggested
       - processDecline method described properly
       - declineNonMatchingIPAddresses description updated
       - global declined-addresses statistic added and tested
       -
      bd35732a
  4. 08 Sep, 2015 1 commit
  5. 13 Aug, 2015 1 commit
  6. 12 Aug, 2015 1 commit
    • Thomas Markwalder's avatar
      [3997] Corrected DHCP4 server crash on exit when DDNS is enabled · 5e855328
      Thomas Markwalder authored
      Rather that stopping it explicitly, the server was relying D2ClientMgr
      to stop itself during its own destruction.  This was falling over during
      process wind-down because the IfaceMgr singletone was being destroyed before
      the D2ClientMgr instance.
      The server destructor now explicitly stops the D2ClientMgr.
      
      src/bin/dhcp4/dhcp4_messages.mes
          added DHCP4_SRV_D2STOP_ERROR log message
      
      src/bin/dhcp4/dhcp4_srv.cc
          Dhcpv4Srv::stopD2() - new method stops the NCR sender, causing it to
          unregister its WathSocket from IfaceMgr
      
          Dhcpv4Srv::~Dhcpv4Srv() - added call to Dhcpv4Srv::stopD2()
      
      src/bin/dhcp4/tests/dhcp4_process_tests.sh.in
          Enabled DNS updates in the CONFIG string.  This ensures the D2
          client will be started during system tests
      5e855328
  7. 08 Jul, 2015 1 commit
  8. 23 Jun, 2015 1 commit
  9. 11 Jun, 2015 1 commit
  10. 22 May, 2015 1 commit
  11. 18 May, 2015 1 commit
  12. 15 May, 2015 1 commit
  13. 12 May, 2015 1 commit
  14. 04 May, 2015 1 commit
  15. 13 Mar, 2015 2 commits
  16. 12 Mar, 2015 4 commits
  17. 10 Mar, 2015 2 commits
  18. 22 Jan, 2015 2 commits
  19. 20 Aug, 2014 1 commit
  20. 15 Jul, 2014 1 commit
  21. 02 Jul, 2014 1 commit
  22. 04 Jun, 2014 1 commit
    • Marcin Siodelski's avatar
      [3405] LeaseMgr is not started until server is configured. · 5eed3a0c
      Marcin Siodelski authored
      Starting lease manager in the server constructor implied the use of the
      default memfile for a short period until the server is configured. The
      default memfile configuration used the persistence (writing leases to disk)
      which in many cases required root privileges. This caused some unit tests
      to fail.
      5eed3a0c
  23. 21 May, 2014 1 commit
  24. 25 Mar, 2014 1 commit
  25. 19 Feb, 2014 1 commit
  26. 18 Feb, 2014 1 commit
  27. 14 Feb, 2014 1 commit
  28. 13 Feb, 2014 1 commit
  29. 06 Feb, 2014 1 commit
  30. 03 Feb, 2014 1 commit
  31. 13 Jan, 2014 1 commit
  32. 09 Jan, 2014 1 commit
  33. 08 Jan, 2014 1 commit
  34. 07 Jan, 2014 1 commit