Quote from: thormir84 on Today at 04:18:34 PMI did further tests and took a look at the configuration options of Kea DHCP, and i confirm that the crash occurs when i activate the service.What kind of crash ?!
QuoteI saw that there is a section related to DDNS, but in my case everything is managed via Docker with Nginx Proxy Manager;KEA DDNS is meant for Hostname DNS Registration in combination with Unbound as the DNS Server because initially it only worked for a Static DHCP IP Address Mapping based on the MAC Address and not for a regular Dynamic DHCP IP Address.
even on ISC DHCP there is an option related to DDNS, but i have never enabled it.
Quote from: e97 on April 25, 2026, 01:25:14 AMIf the Destination Port shows : Single Port or Range and accepts the same value that would remove the confusion.Just read this : https://forum.opnsense.org/index.php?topic=51737.msg266041#msg266041
The docs could also show examples of common use cases which would make this more straightforward and reduce support questions like this.
Quote from: lmoore on Today at 02:29:46 AMQuote from: OPNsense4ever on April 26, 2026, 11:47:58 PMWhat should be used for Redirect Target Port? The first port in the range? 1630? any?
In your case you would enter 1630, which is the base port number for the range.
Connections arriving within you port range of 1630-1641 will be redirected to ports 1630-1641 at the redirected address.
If you set your Redirect Target Port to 20630, the connections arriving within the port range of 1630-1641, will be redirected to 20630-20641.
If you wanted to use multiple but not sequential ports, you would set up a Port Alias with the port numbers and use the Port Alias in the Destination Port and Redirect Target Port fields.
[Edit] Using "any" simply redirects to the port numbers within the range.