Recent posts

#1
This is just for the final screenshot
#2
I noticed it is much more difficult to tell if a scheduled rule is active.

Perhaps in the new Rules system, when adding the column, it does not appear to pull in the icon asset corresponding to an Active/Enabled schedule on a rule.

It does still appear correctly on the classic rules system.

This happens in the current Business Edition OPNsense 26.4.1p2-amd64

as well as Community Edition OPNsense 26.1.11_10-amd64

Attached are screenshots, one of a Business Edition fully migrated to the new Rules system, and the last two are of the same Community Edition node, viewing classic rules in the New Rules system, and a view directly from the WAN interface rule in the classic view.
#3
26.7 Series / Re: how to apply a schedule to...
Last post by sleek3177 - Today at 02:00:28 AM
It sure does, Thanks.
I must have overlooked that a thousand times.
#4
26.7 Series / Re: how to apply a schedule to...
Last post by gpb - Today at 01:41:48 AM
When editing the rule, turn on Advanced and it will show as an option.
#5
26.7 Series / how to apply a schedule to a f...
Last post by sleek3177 - Today at 12:55:51 AM
I can't seem to find the way to apply a schedule to a firewall rule.
I have created an alias for the relevant IPs under Firewall>Aliases. I have created a schedule under Firewall>Settings>Schedules.

When I try to create a rule, I don't see anyplace to associate the schedule with the rule.
Am I doing something incorrectly?
#6
General Discussion / Re: Problem with ping on one e...
Last post by drosophila - Today at 12:05:04 AM
It probably is connected to your other issue, there seems to be some cruft in your config that creates a race condition for the IP config, and there seems to be a rules issue that may come from the same source. You could check the firewall live view if those ICMP replies are blocked. Also, your route configuration may be borked and have entries that blackhole these ICMP responses.

Like that a disabled but configured route blocks automatic generation of any route with an identical target network. IOW, if you configure a disabled static route to blackhole 192.168.0.0/16 and have this range on your LAN, then the LAN will get no route at all. This simple case is obviously not what you have, but there may be similar routing configurations left over, depending on the complexity of your set-up.

You could attempt a config export, followed by a config clear and a config import. Unless the remains are stored in the config file they should be gone after this withot affecting the intended configuration.
#7
26.7 Series / Re: Post Update to 26.7.1_1, K...
Last post by Monviech (Cedrik) - July 31, 2026, 11:09:16 PM
You probably have a faulty client polluting your leases.

https://github.com/opnsense/core/pull/10294
#8
26.7 Series / Re: CrowdSec remediation block...
Last post by SonicJoe - July 31, 2026, 10:44:35 PM
Possibly related to this: https://github.com/opnsense/src/issues/303

Edited to link correct issue

#9
Hardware and Performance / Deciso DEC-850v1 thermal senso...
Last post by N0b0dy1985 - July 31, 2026, 10:18:34 PM
On the Deciso DEC-850v1 (AMD Epyc 3201, Netboard A20) I'm trying to figure out which module or driver OPNsense is loading for the thermal sensors. Does anyone know? Does the plugin hwprobe have this info?

Edit, got it thanks anyway!
#10
26.7 Series / Post Update to 26.7.1_1, KeaDH...
Last post by stauf - July 31, 2026, 09:58:34 PM
Is anyone else seeing this?  I had a similar problem in the past and people added in the ability to delete a DHCP entry from the table.  Things have been stable for a few months now and, all of a sudden, after updating to 26.7.1_1, my address pool is getting exhausted.  Normally, I am only using 2-3 addresses in a pool of 30+.  These "declined" entries have a lifetime of 600 (instead of the default lifetime of 4000 which all of my "real" entries are set to).  I'll have to try to do a wireshark trace to find out if anything sending out DHC requests on my network, but I am not aware of any new devices on my network or any config changes.  As far as I know, the only recent change was updating to 26.7.1_1.

Luckily, it appears that my static pool is not being erroneously over-ridden (like it was last time) so, as long as I have static entries for the devices I want on the network (or existing dynamic entries), it is working fine.

What does "declined" mean as a "state" in the KeaDHCP Lease table?  If OpnSense declined a DHCP request, why burn an entry in the Lease table?  Even if it is for a shorter amount of time.