We are introducing an integrated DHCP server for NxFilter.

[jahastech]

Starting with version 4.7.2.2, NxFilter includes a built-in DHCP server. If you'd like to try it out, download nxfilter-4.7.2.2-dhcp.zip on our download page, https://nxfilter.org/p4/download/

To install it, follow the standard installation guide for NxFilter zip package, https://tutorial.nxfilter.org/a-inst...-linux.php#usz

If you already have NxFilter v4.7.2.2 installed, you can simply update the GUI by overwriting '/nxfilter/guipack' directory with the contents from the zip file.

GUI walkthrough is here: https://tutorial.nxfilter.org/gui-dhcp.php

* The DHCP server must be bound to a single IP address, and that IP address must be associated with a wired network interface.

[jahastech]

The Denied MAC feature has been added by v4.7.2.4. The following is from our tutorial:

The Denied MAC feature blocks specific devices from receiving an IP address from the DHCP server. When a MAC address is added to this list, any device using it will be explicitly denied DHCP service. This feature is useful for blocking unauthorized or suspicious devices from accessing the network.

[jahastech]

Easier User Identification with NxFilter's Built-in DHCP Server

NxFilter supports many ways to identify users on the network. Some methods are simple. The easiest is to associate IP addresses with users. Or you can create user accounts with passwords and have users log in through the NxFilter login page (also called a captive portal).

There are also more advanced methods, such as integrating with Active Directory, using 802.1X Wi-Fi authentication, or installing a login agent on the user’s device. These require more setup and technical knowledge.

In our experience, many users — especially those running smaller networks — prefer simpler methods like IP association or a captive portal.

But these simpler methods have limitations:

• IP-based association doesn’t work when IP addresses change. It only works with static IPs.
• Login page redirection doesn’t work with HTTPS, and users must log in manually, which can disrupt their experience.

Now, with NxFilter’s built-in DHCP server, things get much easier. When a device connects to the network, NxFilter receives its MAC address and hostname from the DHCP request. You can associate this information with a user — no agent, no login page, no external server required.

Once a MAC address or hostname is linked to a user in the NxFilter GUI, NxFilter will continue to recognize that user even if their IP address changes.

This allows you to apply user-based network policies simply and consistently — with minimal setup and no interruption for users.

NxFilter gives you flexible options — and now, an easier one.

[support200]

NxFilter version 4.7.2.6 has been released. You can now associate MAC addresses and hostnames detected by the DHCP service with a user. To find out more: https://tutorial.nxfilter.org/k-user...on-by-dhcp.php

[jahastech]

Starting with version 4.7.3.1, NxFilter supports DHCP clustering. This allows you to configure a backup DHCP server for automatic failover within a NxFilter cluster. To find out more, read https://tutorial.nxfilter.org/k-dhcp-clustering.php

[jahastech]

You can set the Server Identifier independently from the Listen IP starting from v4.7.4.2.

On Windows, both the Listen IP and the Server Identifier are initialized to a single IP address of the actual network interface.

On other operating systems, including Linux, the Listen IP is initialized to 0.0.0.0 to receive broadcast packets, while the Server Identifier is initialized to the actual interface IP.

These behaviors follow OS-level restrictions.