Tweet
Important changes in NxFilter v4.7.4.2.
It appears that there are OS-level restrictions on binding to 0.0.0.0 in Windows 11 and possibly other Windows versions. When NxFilter is installed on Windows 11, it may fail to start correctly due to binding issues on UDP/53 for DNS and UDP/67 for DHCP.
To address this, if the DNS server cannot bind to 0.0.0.0, NxFilter now automatically retries binding to a single IP using the Block Redirection IP.
For DHCP, we discovered the same issue during development and have since initialized the DHCP Listen IP to a single IP on Windows. However, this approach introduces another issue on Linux. Linux requires binding to 0.0.0.0 in order to receive broadcast packets, and even if users manually bind DHCP to 0.0.0.0, the Server Identifier creates another conflict.
Our solution is to separate the Server Identifier from the Listen IP. On Linux, the DHCP Listen IP is now initialized to 0.0.0.0, while the Server Identifier is set to the actual interface IP.
To address this, if the DNS server cannot bind to 0.0.0.0, NxFilter now automatically retries binding to a single IP using the Block Redirection IP.
For DHCP, we discovered the same issue during development and have since initialized the DHCP Listen IP to a single IP on Windows. However, this approach introduces another issue on Linux. Linux requires binding to 0.0.0.0 in order to receive broadcast packets, and even if users manually bind DHCP to 0.0.0.0, the Server Identifier creates another conflict.
Our solution is to separate the Server Identifier from the Listen IP. On Linux, the DHCP Listen IP is now initialized to 0.0.0.0, while the Server Identifier is set to the actual interface IP.