Recent posts

#1
If you can help upstream that will most likely result in a fix. Sadly it will not emerge out of nowhere.

https://github.com/opnsense/ports/issues/258
#2
Opnsense 26.1.6_2

We are encountering the same issue after migrating from ISC DHCPv4 to Dnsmasq (on VM with 8GB RAM). For now we have enabled the 2GB swap file, hoping the issues can be contained until fix.
#3
26.1, 26,4 Series / Re: 26.1.6_2 - All traffic blo...
Last post by nero355 - Today at 05:53:06 PM
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 ?!

This topic started with a Firewall Rule issue and now there is something crashing ?!

QuoteI saw that there is a section related to DDNS, but in my case everything is managed via Docker with Nginx Proxy Manager;
even on ISC DHCP there is an option related to DDNS, but i have never enabled it.
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.

Is there any chance that some of your Docker stuff got upgraded too within the same timeframe and is causing issues now ?
Reason I am asking : A lot of people let something like WatchTower update/upgrade their Docker Containers completely automatically.
#4
OK, the problem is now solved.

You were right, the routing rule has to be added to the inbound interface. I already tried this in the first place but the any-destination did not work properly with my network configuration. So I tried it again with the correct settings and it worked.

Thanks for your help! :)
#5
26.1, 26,4 Series / Re: Port Forward / Destination...
Last post by nero355 - Today at 05:41:42 PM
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.
The docs could also show examples of common use cases which would make this more straightforward and reduce support questions like this.
Just read this : https://forum.opnsense.org/index.php?topic=51737.msg266041#msg266041

Does this apply to your question too ??
#6
General Discussion / Re: No IP from DuckDNS and Ded...
Last post by JamesFrisch - Today at 05:16:54 PM
Updated the script. Hope it works for you, I don't know how I could make it any simpler.
Let me know if I can help you with anything.
#7
Web Proxy Filtering and Caching / Re: Squid C-ICAP Error
Last post by grassi - Today at 05:13:23 PM
what's your c-icap setting in squid? Did you try to follow the manual, it states an ipv6 localhost adress I think. We had the issue that on the one side, it was set up to listen on ipv6, and the client connected on ipv4, and that didn't work.
#8
26.1, 26,4 Series / Re: 26.1.6_2 Destination NAT ...
Last post by OPNsense4ever - Today at 04:55:25 PM
Quote from: lmoore on Today at 02:29:46 AM
Quote 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.

Fantastic! This should be documented somewhere though. Is it written somewhere that I missed?

😁 Let me see if I can get my proverbial stuff together for a PR if not.
#9
General Discussion / Re: How do IPv6 Router Adverti...
Last post by mooh - Today at 04:22:34 PM
Thanks for explaining this again. It never occurred to me that you want to bypass the matter bridge feature of the Dirigera hub. That's why I was pointing out that you only need to connect to the border router (implying the matter bridging).

Assuming I finally understand the setup: Isn't this a multi-admin setup having the Dirigera and OpenHAB server controlling the Thread devices in parallel? This may have a negative impact on the battery life of any devices due to the additional communication. Wouldn't it be much easier to just add a Thread radio to the OpenHAB server and drop the Dirigera Hub, also removing the dependency of the OPNsense routing on the ULA prefixes used by the Dirigera hub?
#10
26.1, 26,4 Series / Re: 26.1.6_2 - All traffic blo...
Last post by thormir84 - Today at 04:18:34 PM
I 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. I saw that there is a section related to DDNS, but in my case everything is managed via Docker with Nginx Proxy Manager; even on ISC DHCP there is an option related to DDNS, but i have never enabled it.