DHCP Server for Windows » uwe

V2.10.5

uwe — Fri, 30 Jan 2026 05:36:21 +0000

V2.10.5.0 released 30/1/2026. All versions update for Windows 32-Bit, Windows 64-Bit, Raspberry 32-bit and Raspberry 64-bit. This release includes bug fixes with respect to pxeboot features. It effects the TFTP server function and some special options such as OPTIONHEX.

V2.10.4

uwe — Sun, 21 Dec 2025 06:58:34 +0000

V2.10.4.0 released 21/12/2025. All versions update for Windows 32-Bit, Windows 64-Bit, Raspberry 32-bit and Raspberry 64-bit. This release includes the following bug fixes: NAK message includes service id and HTTP head with correct content-length.

V2.10.3

uwe — Tue, 29 Jul 2025 07:44:55 +0000

V2.10.3.0 released 29/07/2025. All versions update for Windows 32-Bit, Windows 64-Bit, Raspberry 32-bit and Raspberry 64-bit. This release includes bug fixes with respect to class A/B networks under Linux and allows blanks in IPPOOL definitions in the INI file.

V2.10.2

uwe — Sun, 22 Jun 2025 07:05:23 +0000

V2.10.2.0 released 22/06/2025. All versions update for Windows 32-Bit, Windows 64-Bit, Raspberry 32-bit and Raspberry 64-bit. This release includes bug fixes with respect to INI file settings with blanks not always recognized.

V2.10.1

uwe — Sat, 03 May 2025 07:13:37 +0000

V2.10.1.0 released 03/05/2025. All versions update for Windows 32-Bit, Windows 64-Bit, Raspberry 32-bit and Raspberry 64-bit. This release includes the following:

64-bit version for raspberry
Copy-Option feature (see here)
Smaller bug fixes

The download is available after a donation is made.

V2.10.0

uwe — Tue, 17 Sep 2024 07:14:52 +0000

V2.10.0.0 released 17/9/2024. All versions update for Windows 32-Bit, Windows 64-Bit and Raspberry. This release includes the following:

IgnoreRequestedAddress (see here)
Improved tracing information
Display Hostname and IP address in tray balloon message
Wizard does not add 0.0.0.0 as a router anymore
Smaller bug fixes

The download is available after a donation is made.

IgnoreRequestedAddress

uwe — Tue, 17 Sep 2024 07:12:33 +0000

Changes how the DHCP Server interprets the requested address submitted from a client.

[Settings]
IgnoreRequestedAddress=1        ; Default: 0 (don't ignore)

If IgnoreRequestedAddress is set to 0 (default): The DHCP server will take the requested address from an unknown client into account when selecting an address to offer, matching the requested address as long as it is free and inside the IP pool.

If IgnoreRequestedAddress is set to 1: The DHCP server will ignore unknown clients suggestion on IP address. Leading to the DHCP server not taking the client request for a specific IP address in account when selection an address to offer the client.

This behavior might not be fully confirmative with the DHCP specification and is not recommended in general usage. But might be useful in special cases.

This feature was an added in V2.10.0.0.

V2.9.4.1

uwe — Sun, 18 Aug 2024 06:27:02 +0000

V2.9.4.1 released 18/8/2024. This release includes a native Visual Studio 2022 compilation for Windows 64-bit (dhcpsrv64.exe) and an updated version to a common code base for Windows 32-bit and Raspberry.

The download is available after a donation is made.

How to run external scripts from the HTTP server?

uwe — Sun, 11 Aug 2024 07:38:19 +0000

External scripts are a great way to enhance the HTTP server with specific features. This is supported in the Raspberry Pi Version V2.9.4.0 only, for now.

The external script can be actually any executable, but the most obvious is to run a bash script. Here is an example:

#!/bin/bash
echo ""
echo ""
echo "Hello Script"
echo ""

Place this file into your wwwroot folder name it say “script01″ and make it an executable with the chmod command from the command line:

cd /usr/local/etc/dhcpsrv/wwwroot
chmod +x script01

It is assumed that the HTTP Server function is enabled and reachable by an url such as http://raspberry. To execute script01 and see the resulting page enter http://raspberry/script01 into the address line of your browser and you will see the Hello Script page. If that is not the case then please check the HTTP server configuration.

In case you don’t want to return HTML code from your script but for example some JSON structure then this can be done as well. This a bash script that returns a JSON structure:

#!/bin/bash
DATA="{\"valid\":true}"
# write to stdout the HTTP response
DATESTRING=$(date "+%a, %d %b %Y %H:%M:%S %Z")
printf "HTTP/1.1 200 OK\r\n"
printf "Date: %s\r\n" "$DATESTRING"
printf "Last-Modified: %s\r\n" "$DATESTRING"
printf "Server: %s\r\n" "dhcpsrv"
printf "Content-Type: %s\r\n" "application/json"
printf "Content-Length: %s\r\n" "${#DATA}"
printf "\r\n"
printf "%s" "$DATA"

As you can see the big difference is that in case of something else than a , the full header needs to be included into the output of the bash script. Let’s paste the above into a bash script02 file and make that executable as well with chmod, then your browser will display the JSON output when directed to the url http://raspberry/script02.

The examples so far were HTTP GET use cases. Now let’s take a look at POST requests. POST requests differ from GET requests in extra data supplied from the client app running in the browser. This extra data is usually a list of key/value pairs as they are coming from an HTML form. The DHCP server integrated HTTP function writes that extra data into a temporary file and that filename is supplied as a parameter to the external script. Here is an example on how to deal with that:

#!/bin/bash
saveIFS=$IFS
IFS='=&'

declare -A post

if [ -f "$1" ]; then
 # construct the associative array for POST_STRING
 POST_STRING="$(<"$1")"
 parm=($POST_STRING)
 for ((i=0; i<${#parm[@]}; i+=2))
 do
    post[${parm[i]}]=${parm[i+1]}
 done
fi

IFS=$saveIFS

# do something with the post data e.g. ${post["firstname"]}

printf "HTTP/1.1 301 Moved Permanently\r\n"
printf "Date: %s\r\n" "$DATESTRING"
printf "Last-Modified: %s\r\n" "$DATESTRING"
printf "Server: %s\r\n" "dhcpsrv"
printf "Location: %s\r\n" "post.html"
printf "\r\n"

We see two important things here:

The post data is read from the file supplied as a argument $1 into a param array splitted by ‘=’ and ‘&’. The param array is only there to construct an associative array with the name “post”. That in turn can be used by the script to perform the required action on that data.
The returning result text from the script is now a redirect header. This is part of the post-redirect-get pattern commonly used together with POST requests. In this case the redirection target is post.html and obviously can be anything else.

We save the above script as “script03″ in the wwwroot folder and call that script from a post request such as in the following example HTML post.html:



 
 
 
  
   First name:
   


   Last name:

This HTML code presents a form with two entry fields “First name” and “Last name”. Those will show up in the script03 as ${post[“firstname”]} and ${post[“lastname”]} and can be used to perform whatever that script needs to do.

QUERY data is supported as well, as they are supplied as part of the URL such as “http://raspberry/script04?key1=value1&key2=value2″. An enhanced version of script03 (called script04) can make use of the query data as follows:

#!/bin/bash
saveIFS=$IFS
IFS='=&'

declare -A post
declare -A query

# construct the associative array for QUERY_STRING
parm=($QUERY_STRING)
for ((i=0; i<${#parm[@]}; i+=2))
do
 query[${parm[i]}]=${parm[i+1]}
done

if [ -f "$1" ]; then
 # construct the associative array for POST_STRING
 POST_STRING="$(<"$1")"
 parm=($POST_STRING)
 for ((i=0; i<${#parm[@]}; i+=2))
 do
    post[${parm[i]}]=${parm[i+1]}
 done
fi

IFS=$saveIFS

# do something with the post data e.g. ${post["firstname"]} or ${query["key1"]}

printf "HTTP/1.1 301 Moved Permanently\r\n"
printf "Date: %s\r\n" "$DATESTRING"
printf "Last-Modified: %s\r\n" "$DATESTRING"
printf "Server: %s\r\n" "dhcpsrv"
printf "Location: %s\r\n" "post.html"
printf "\r\n"

The scripts executed this way run with the privilege of the dhcpsrv executable. Usually root privileges in case of systemctl based installation as described here. Handle with care!

Does the integrated HTTP Server support POST?

uwe — Sun, 11 Aug 2024 07:35:53 +0000

Yes, POST requests are supported since V2.9.4.0 on Raspberry Pi version only for now. It works in a CGI like manner and is described in detail here.