** Beta testers needed for DHCPatriot 6.2.0 **

• DHCPv6 captive portal authentication.
• RFC 6939 (DHCPv6 option 79) support. If present, mac address is recorded with the DHCPv6 session.
• Sticky assigments to DHCPv6 clients.
• Re-written authentication client (RADIUS and Built-in) to support IPv6 specific IP addresses and RADIUS options.

** Beta testers needed for DHCPatriot 6.2.0 **

1. A problem was discovered and corrected where if a customer was configured with any kind of static ip (sticky or otherwise) their option 82 information would not be recorded.
2. Prefix delegations previously would not have been able to take advantage of services such as NTP on the DHCPatriot system. This has been corrected such that local firewall has been opened for these services for delegated prefix.
3. A problem that caused it to be impossible to preview the login screen while logged into the DHCPatriot via IPv6 has been corrected.
4. A problem was found when certain types of edits were made to sticky IP addresses for authenticated devices where the old device would still be configured for the sticky IP. This problem has been corrected.
5. A problem where Standard DHCP Reports -> View Address Usage would not show the "Total Dynamic" line for certain networks has been corrected.
6. Possible fix implemented for hangs on reboot that crop up occasionally on DHCPatriot devices (especially during software updates).
7. Now, if "DHCP One Lease Per Client Flag" is disabled in "System Configuration -> General Setup", the DHCPatriot system will no longer truncate an existing session in the GUI when a new lease for a different IP is obtained.
8. A problem was found where sending a mac address in any other format other than xx:xx:xx:xx:xx:xx via the API resulted in the user device being authenticated but not added to the DHCP server using the new authenticated method. This has been corrected.

1. Previously `Auth DHCP Config -> Exclude IP Address` did not expose the `Limit Displayed Entries` box. This made searching within the list impossible. This has been resolved. The box now appears and searching of this list is possible.
2. Filesystem trim support is now triggered on boot in addition to once daily.
3. Swappiness is now reduced to 5% on boot.
4. Trim is now activated on the boot flash in model 2013-1 and newer DHCPatriot systems which contain such flash.
5. Comma Separated Value (CSV) exporter will have commas stripped from the fields as this can obviously cause a problem for comma separated value files if there are rogue commas in the file.
6. Performance module from the upper right has been hidden on virtual systems. This due to our inability to predict the hardware available in a virtual environment.
7. Moderate performance bug in Usage Graphs data collection found and repaired.
8. Disabled subnets ip counts now removed from total available IPs. Previously it made no impact on the counts of available addresses or the warnings about networks being full.
9. Sessions will now move with a subnet if a subnet is moved to a different shared network or a different type of DHCP (such as auth -> standard). Some times in the past, a subnet would be moved. Sessions would continue. But they would disappear because they were still tied to the old shared network that wasn`t their home anymore. The sessions would show up in search sessions, but not in the counts on view address usage and the graphs. They still won`t immediately show up even now, but as they renew, the count will become correct.
10. Preliminary support has been added for temperature monitoring. In a future release, the data will be added to SNMP output and server status web administration interface function.
11. On certain systems, syslogd can have a tendency to not restart properly after log rotation. This seems to be limited to VMware systems. To counteract this, detection and starting of failed syslog has been implemented.
12. A problem was fixed in the Built-in Authentication where a response couldn`t be obtained if the user was suspended. This could allow the user to stay online when they shouldn`t have been. This has been corrected.
13. A new backend feature has been added such that authenticated devices are added and removed directly from the DHCP server. This means that a DHCP server restart is no longer required when user devices are authenticated or get suspended. This will result in greater DHCP server availability than is present prior to 6.1.0. Please note that this is a rather substantial change in operation of the DHCPatriot and as such there could be some unknown bugs present. If any are discovered, we will get a patch out as soon as possible.
14. Standard DHCP Actions -> Known Client will now automatically translate any single quote ` to a back-tick ` to avoid problems with queries as the entries are used during DHCP actions.
15. Standard DHCP Actions -> Static IP Assignment will now automatically translate any single quote ` to a back-tick ` to avoid problems with queries as the entries are used during DHCP actions.
16. API: The API log messages have been enhanced. More descriptive log messages for API actions and failed logins / errors and the like are now available. These can be searched by going to System Configuration -> System Logs and selecting index for the Daemon and entering *API* in the Search Text box. In certain instances, this may impact returned error messages for the API. Please ensure that your API scripts still work after updating.
17. API: The Known Client API calls previously did not properly restart the DHCP server when performing actions. This has been corrected.
18. User Admin Restriction fix implemented. Previously, if you had an auth network selected but no standard, it showed you all standard networks. Also, if you had a standard network selected but no auth, it showed you all auth networks. This behavior has been corrected. Now, if you have at least one from one of the types selected but no other, all of the non-selected networks are hidden regardless of whether they are auth or standard. This makes this feature behave as was intended and per the descriptive text of the feature. Network restrictions are a convenience to hide networks which a particular administrator has no interest in (such as might be the case if multiple companies are sharing a DHCPatriot system). It is located and configured in System Configuration -> Administrators on the web administration interface.
19. VRRP for IPv6 has been added. Set this up under System Configuration -> General Setup in box 14. The IPv6 addresses of the DHCPatriot devices as well as the VRRP address must all be in the same subnet.
20. Corrected various spelling errors in response messages.
21. API: The Deny MAC Address list can now be added to and removed from via a new API function. To Add:
    https://patriot.network1.net/cli/? username=apiuser&password=apipass&function=DenyMacAddress&action=ADD&mac=00:00:00:00:00:01¬e=A%20TEST%20OF%20API%20DENY%20MAC %20ADD
    To Remove:
    https://patriot.network1.net/cli/?username=apiuser&password=apipass&function=DenyMacAddress&action=REMOVE&mac=00:00:00:00:00:01
22. A new area has been added to configure permissions for the various functions available on the DHCPatriot system web administration interface. We called this Set App Permissions and it can be found under the System Configuration menu. This can be used to adjust the permission levels so that custom administrator levels can be created hiding / showing certain things to various administrator levels according to requirements.
23. DHCPv6 Option 18 and Option 37 are now supported on the DHCPatriot system. They are only supported in the case that they are ASCII text strings (as was the case with option 82 support in DHCPv4). These options will be recorded with the DHCPv6 sessions.
24. DHCPv6 sessions are now being recorded in the database.
25. DHCPv6 sessions are now searchable in DHCPv6 (IPv6) -> Search Sessions. You can search by Client DUID, IP Address (which will also search delegated prefix), options 18 and 37, date/time and show only online devices. Additional parameters shown (Username and MAC Address) are not yet relevant and there for future development. The search results look similar to those available in DHCPv4.
26. A new DHCPv4 setting has been exposed. The One Lease Per Client flag can now be toggled in System Configuration -> General Setup. This flag has always been there and is thus enabled by default. The DHCP server is instructed to allow only one IP Address per client. If a client requests a new lease, the previous lease is released. In 99% of situations this is the desired behavior. Recently, we have encountered a situation with a customer where multiple IP addresses per client is desired. Thus we have exposed this setting. If disabled, a client will be able to obtain and use multiple IP addresses simultaneously.
27. Extra DHCP settings for DHCPv6 have been added to System Configuration -> General Setup. This works in a similar manner to the extra settings for DHCP except on DHCPv6 instead of DHCPv4.
28. A problem was corrected where, under certain rare circumstances, stop time could be one second less than start time causing session time sent to the radius server to be -1 which resulted in session time appearing to be the largest possible positive unsigned 32 bit integer from the RADIUS server`s perspective. session time will now be adjusted to 0 in this case.
29. View Address Usage now appears in DHCPv6 complete with the ability to click the subnet and see a list of users in the subnet. Graphs are not yet present and will appear in a future version.
30. It is now possible to disable subnets in DHCPv6. This works much the same as it does in DHCPv4. The only difference being that Prefix delegations are dependent on a subnet, and so if a subnet is disabled, all of the prefix delegations dependent on that subnet will also show disabled in view address usage.
31. Prefix Delegation has been split off from Dynamic Subnet allocations in DHCPv6. This allows multiple Prefix Delegation pools to be setup per subnet. Access Prefix Delegations in the DHCPv6 (IPv6) -> Prefix Delegation menu item. At time of install of 6.1.x, any prefix delegation pools that are setup with a subnet will be moved to this area.