1. 23 Nov, 2015 1 commit
  2. 21 Nov, 2015 5 commits
  3. 20 Nov, 2015 3 commits
  4. 26 Oct, 2015 1 commit
  5. 20 Oct, 2015 1 commit
    • Marcin Siodelski's avatar
      [3977] Name change requests are now generated when lease is reused. · 5de74693
      Marcin Siodelski authored
      This change triggered a lot of code refactoring for generating the
      NameChangeRequests. Long story short is that the functions responsible
      for generating NCRs from the lease information have been moved to
      the libdhcpsrv where they better fit and where they may be used
      by both allocation engine and the servers.
      5de74693
  6. 15 Oct, 2015 2 commits
  7. 13 Oct, 2015 2 commits
  8. 09 Oct, 2015 1 commit
  9. 08 Oct, 2015 1 commit
  10. 06 Oct, 2015 2 commits
  11. 25 Sep, 2015 1 commit
  12. 19 Sep, 2015 3 commits
  13. 18 Sep, 2015 1 commit
  14. 17 Sep, 2015 1 commit
  15. 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
  16. 08 Sep, 2015 2 commits
  17. 02 Sep, 2015 1 commit
  18. 25 Aug, 2015 1 commit
  19. 24 Aug, 2015 1 commit
    • Thomas Markwalder's avatar
      [2615] v4 clients may now release out-of-range leases · 6bffb344
      Thomas Markwalder authored
          Modified v4 server to not enforce subnet match when clients attempt
          to release an existing, but out-of-range lease.
      
          Added a battery of unit tests to verify proper v4 server behavior
          when clients attempt to renew or release out-of-range addresses.
      
      src/bin/dhcp4/dhcp4_messages.mes
       - deleted DHCP4_RELEAE_FILE_NO SUBNET as it is now obsolete
      
      src/bin/dhcp4/dhcp4_srv.cc
       -  Dhcpv4Srv::processRelease() - removed the check to make sure the
          release pertains to a configured subnet.  This allows clients to
          release leases after configuration changes rendered them out of
          range.
      
      src/bin/dhcp4/tests/Makefile.am
        - added out_of_range_unittest.cc
      
      src/bin/dhcp4/tests/out_of_range_unittest.cc
       - New file containing DHCPv4 tests for server behavior regarding
         renews and releases of "out of range" addresses.
      
      src/bin/dhcp4/tests/release_unittest.cc
       - TEST_F(ReleaseTest, releaseNoSubnet) - modified the test to
         verify that a client CAN release an out-of-range lease
      6bffb344
  20. 20 Aug, 2015 3 commits
  21. 12 Aug, 2015 2 commits
    • Thomas Markwalder's avatar
      [3997] Corrected DHCP6 server crash on exit when DDNS is enabled · ef1033c4
      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/dhcp6/dhcp6_messages.mes
          added DHCP6_SRV_D2STOP_ERROR log message
      
      src/bin/dhcp6/dhcp6_srv.cc
          Dhcpv6Srv::stopD2() - new method stops the NCR sender, causing it to
          unregister its WathSocket from IfaceMgr
      
          Dhcpv6Srv::~Dhcpv6Srv() - added call to Dhcpv6Srv::stopD2()
      
      src/bin/dhcp6/tests/dhcp6_process_tests.sh.in
          Enabled DNS updates in the CONFIG string.  This ensures the D2
          client will be started during system tests
      ef1033c4
    • 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
  22. 19 Jul, 2015 1 commit
  23. 09 Jul, 2015 1 commit
  24. 19 Jun, 2015 2 commits