1. 16 Sep, 2014 1 commit
  2. 20 Aug, 2014 1 commit
  3. 28 Jul, 2014 1 commit
  4. 22 Jul, 2014 2 commits
  5. 15 Jul, 2014 1 commit
  6. 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
  7. 27 May, 2014 1 commit
  8. 21 May, 2014 1 commit
  9. 13 May, 2014 1 commit
  10. 10 May, 2014 1 commit
  11. 19 Feb, 2014 1 commit
    • Tomek Mrugalski's avatar
      [3322] Changes after review: · 8174421f
      Tomek Mrugalski authored
       - Unit-tests for DHCPv4 now use configure() method.
       - Typo fixed in DHCPv6 unit-tests.
       - Removed, updated comments in cfgmgr
       - Guide updated
      8174421f
  12. 18 Feb, 2014 1 commit
  13. 13 Feb, 2014 2 commits
  14. 06 Feb, 2014 2 commits
    • Tomek Mrugalski's avatar
      [3274] Changes after review: · f2c1e775
      Tomek Mrugalski authored
       - Copyright years updated
       - Minor corrections in BINDX Guide
       - dhcp4.spec relay structure description updated.
       - new unit-test for DHCPv4 client classification added
       - new unit-test for DHCPv6 client classification added
       - fixed Doxygen errors
       - comments for CfgMgr::getSubnet{4,6} updated
      f2c1e775
    • Marcin Siodelski's avatar
      [3242] Addressed review comments. · f22c490b
      Marcin Siodelski authored
      f22c490b
  15. 04 Feb, 2014 1 commit
  16. 03 Feb, 2014 1 commit
  17. 31 Jan, 2014 1 commit
    • Marcin Siodelski's avatar
      [3242] Adjusted unit tests to use correct subnets. · a435b27f
      Marcin Siodelski authored
      This change was necessary, because the recent changes to DHCPv4 imply that
      subnet is selected for directly connected clients by matching the IPv4
      address of the interface on which the message is received, with the
      configured subnet.
      a435b27f
  18. 14 Jan, 2014 1 commit
  19. 13 Jan, 2014 1 commit
  20. 08 Jan, 2014 1 commit
  21. 07 Jan, 2014 1 commit
  22. 03 Jan, 2014 2 commits
  23. 02 Jan, 2014 1 commit
  24. 30 Dec, 2013 1 commit
  25. 13 Dec, 2013 2 commits
  26. 29 Nov, 2013 1 commit
  27. 24 Oct, 2013 1 commit
  28. 23 Oct, 2013 2 commits
  29. 22 Oct, 2013 2 commits
  30. 11 Oct, 2013 3 commits
  31. 10 Oct, 2013 1 commit