Arguably the most important new feature in this build is the floating IP support implemented with Virtual Router Redundancy Protocol (VRRP). This is the last piece of the puzzle in making the DHCPatriot completely high availability.

Previously, the router would need to be changed to force authentication traffic to one DHCPatriot device or the other in the case of outage. Using VRRP allows a third IP address to “float” between the two devices. This allows the router to be configured to force authentication traffic to this third IP address. The IP address never goes down as long as at least one DHCPatriot device is functional.

Other enhancements in this version include: Searchable Option 82 information that is stored with the sessions; Template based configuration of static address definitions in standard DHCP for quick configuration of ONT networks, for example; Optional protection of the authentication page against automated clients via a simple math problem; Checking stored credentials against the RADIUS server during an un-suspend operation; Optionally send RADIUS ALIVE (interim-update) packets upon DHCP client lease renewal; Optional RADIUS forwarding to external devices that need a RADIUS accounting stream.

Patch notes for this release:

1. Floating IP (VRRP) implemented. It is now possible to add a third IP address to the DHCPatriot system that will float between the two devices. This IP address should be used with the captive portal page and possibly as the destination address when administrating the machine. Restrictions to using VRRP are that the DHCPatriot system devices must both be in the same subnet and the floating IP must be in that same subnet as well.
   
2. Optional simple page for protecting the database from being accessed by pre-auth / unauthenticated automated clients such as Weatherbug. This page asks a simple math problem before proceeding to the actual authentication page for pre-auth users. The page has no images and no database access. Automated clients such as Weatherbug will not answer the question and proceed to the login page. Continue reading →

This is a maintenance with bug fixes only. Only DHCPatriot systems experiencing the bugs repaired in this release will receive this software. All of the fixes from this release will of course be in version 5.3.0.

Release notes:

1. Added hardware support for the 2013-1 model of DHCPatriot system.
2. Gave space on startup to launching programs so that they don`t all launch simultaneously. This should help with some freeze-up on startup problems.
3. Added diagnostic software that will allow us to access hardware information in the field.
   Continue reading →

DHCPatriot update 5.2.0 has been released. Patch notes for this release.

1. It is now possible to add fully qualified domain names to the DHCPatriot
2. Force lower case usernames now works from the admin form. Previously it only worked from the customer facing authentication page.
3. ISC DHCP version 4.2.4-P1 is now the core dhcp server. This release contains bug fixes as well as some refinements.
4. Sticky IP notes are now possible. Notes can be included with a sticky IP assignment so that it can be remembered why it was done.
5. Exclude IP notes are now possible. Notes can be included with an excluded IP so that it can be remembered why it was done.
   Continue reading →

DHCPatriot update 5.1.2 has been released. Patch notes for this release.

1. Added firewall rules to place a limit on the number of connections that can be opened by a single client machine to the web authentication page. The limit is 20 hits in 10 seconds. It works like this: once a client opens his 20th connection in 10 seconds, he cannot open anymore. If he continues to try during the time that he cannot open more connections, this counts as well. The client machine will need to wait and not open any more connetions until 10 seconds has passed. It is unlikely that clients with a virus infection opening large amounts of web page ports will be able to get to the authentication page.
2. Changed MaxRequestsPerChild to 1024 from 0 in the web server. This will allow running servers to exit after serving a certain number of pages as per manufacturer recommendation.
3. Removed text wrapping from all textareas to prevent inconsistancies with visual wrap versus storage of actual data.
   Continue reading →