<![CDATA[Rule Schedule re-activation not working correctly]]>I have a rule that passes voip ports and addresss for my providers from the hours 06:00 - 23:59. This worked fine under 2.45 -> 2.5.2

Since i upgraded to 2.60 and then to 22.01 If i reboot pfsense, or i don't enable the schedule the 3 providers register succesfully.
I can reset the voip devices multiple times and the 3 providers will register.

When the schedule kicks in, the http and the voip services are disconnected.
at 06:00 when the schedule kicks in again, the http works and one of the providers register, but 2 others fail to register.

If i reset the device, the 2 still don't register. But if i reboot so the schedule has not blocked the rules, then all services register

If i packet capture everything on the voip vlan, i don't see any errors.
if i packet capture the wan interface i don't see the gigaset or voiptalk registration traffic.

I have disabled suricata and only have pfblockerng enabled (tried to disable but no difference)

]]>https://forum.netgate.com/topic/172541/rule-schedule-re-activation-not-working-correctlyRSS for NodeMon, 18 May 2026 18:55:14 GMTTue, 31 May 2022 07:07:29 GMT60<![CDATA[Reply to Rule Schedule re-activation not working correctly on Sat, 04 Jun 2022 06:15:23 GMT]]>@gwaitsi i was wrong. the http rule switches off and on correctly, but the rules for 5060 and the voip providers after 6am, only one of the 3 providers re-registers. i don't understand what can be blocking the other 2, it should to work on 2.5.2

]]>https://forum.netgate.com/post/1045200https://forum.netgate.com/post/1045200Sat, 04 Jun 2022 06:15:23 GMT<![CDATA[Reply to Rule Schedule re-activation not working correctly on Fri, 03 Jun 2022 06:36:37 GMT]]>@gwaitsi must have been corrupt xml i guess.
i turned off the rules, created a new rules from the blocked transaction, edited that rule to have the same conditions as the former rule and it seems to be working.

]]>https://forum.netgate.com/post/1045028https://forum.netgate.com/post/1045028Fri, 03 Jun 2022 06:36:37 GMT<![CDATA[Reply to Rule Schedule re-activation not working correctly on Wed, 01 Jun 2022 13:34:36 GMT]]>@gwaitsi I have a rule that passes voip ports and addresss for my providers from the hours 06:00 - 23:59. This worked fine under 2.45 -> 2.5.2

Since i upgraded to 2.60 and then to 22.01
If i reboot pfsense, or i don't enable the schedule the 3 providers register succesfully.
I can reset the voip devices multiple times and the 3 providers will register.

When the schedule kicks in, the http and the voip services are disconnected.
at 06:00 when the schedule kicks in again, the http works and one of the providers register, but 2 other fail to register.

If i reset the device, the 2 still don't register. But if i reboot so the schedule has not blocked the rules, then all services register

]]>https://forum.netgate.com/post/1044796https://forum.netgate.com/post/1044796Wed, 01 Jun 2022 13:34:36 GMT<![CDATA[Reply to Rule Schedule re-activation not working correctly on Wed, 01 Jun 2022 13:34:21 GMT]]>@gwaitsi So there seems to be a defect here.

When a scheduler is used, it is showing the rules as s:5d66db51b3fbc (1653986728) and is not using the scheduler Description for the rule.

When the schedule is removed, it is using the description of the rule itself. ** seems this issue is fixed in the 22.05 developments snapshots.

]]>https://forum.netgate.com/post/1044765https://forum.netgate.com/post/1044765Wed, 01 Jun 2022 13:34:21 GMT<![CDATA[Reply to Rule Schedule re-activation not working correctly on Tue, 31 May 2022 09:01:05 GMT]]>@gwaitsi i tried cloning the rules and deleting the original rules. the reason i did that

The log was showing the rule as
s:5d66db51b3fbc (1653986728)

After i cloned and removed the old rule, the log now shows as
(1610264323)

Interestingly, the rules saved/cloned under 22.01 are not showing the rule description in the logs.

but the original rules are.

]]>https://forum.netgate.com/post/1044567https://forum.netgate.com/post/1044567Tue, 31 May 2022 09:01:05 GMT