2.5.1 -> 2.6.0dev -> 2.5.2RC schedules syntax error

[4o4rh]

When i went from 2.5.1 -> 2.6.0 schedules were working.

I had to reinstall and recover previous config last night, and so i went to 2.5.2RC but i am now receiving the below on what were previously good schedules.

There were error(s) loading the rules: /tmp/rules.debug:490: syntax error - The line in question reads [490]: pass in quick on $VLAN_22_VOIP $GWGW_GRP_WAN1_FAILOVER inet proto { tcp udp } from $HOST_SVR_VOIP to $BYPASS_VPN_VOIP tracker 1610264323 keep state schedule "5d66db51b3fbc" label "USER_RULE: Pass ORANGE gigaset VOIP_SIP_RTP Out Ports"

[jimp]

Can you share the schedules configuration and the config.xml for that failing rule as well?

[jimp]

Disregard, we were able to reproduce and locate the cause:

https://redmine.pfsense.org/issues/12040

You can wait for the next build or apply the commit IDs from my comment there using the system patches package.

Thanks for letting us know!

[4o4rh]

@jimp I have pulled those patches and schedules are working now. I did get a system crash on first boot afterwards though, but seems ok for now.

[jimp]

What was in the crash report?

Does it crash if you reboot it again?

[4o4rh]

@jimp seems alright after second boot. thanks again jim

[4o4rh]

@jimp errors are gone, but schedule doesn't work.
my schedule blocks the voip calls between 12 - 6am.
but they are not blocking right now (2.30am), although the ui indicates they should be.

i have tried edit/save the schedule again and verified it does cut traffic...let's see if i get another robo call in the night

[jimp]

From the tests I've run so far it looks like schedules are working OK here for me.

Nothing major changed in how the schedules operate in general, the only part that changed was how the labels for the schedules are set in the ruleset, and as far as I see that's working both ways (in and out of scheduled times, the rules are as expected).

[jimp]

I did find an issue with killing the states when the schedule transitions, and committed a fix for it:

https://github.com/pfsense/pfsense/commit/2afcd4527d4b245c7968bf7ac6b6c505259fe6c9

You could make that change manually or apply it via the system patches package.

[4o4rh]

@jimp said in 2.5.1 -> 2.6.0dev -> 2.5.2RC schedules syntax error:

killing the states when the schedule transitions

Thanks again Jim. I've added that one too. I went in and did edit/save for each of the schedules last night.
Schedule did turn off after i did that, will see if it kicks in tonight.