Bug #13992
closed
Custom default state timeouts are not respected in the ruleset
Added by Anonymous almost 2 years ago.
Updated over 1 year ago.
Plus Target Version:
23.05
Description
When I change the timeouts:
UDP Single to 60
UDP Multiple to 300
And then check from the command line with pfctl -s timeouts
it still shows them at the defaults.
udp.single 30s
udp.multiple 60s
Even after a reboot they are not applied.
First noticed after upgrading to 23.01 that all my Sip phones starting dropping in and out.
The expected values do not get added to the rules.debug file so are not applied to pf.
set timeout { udp.single 60 udp.multiple 300 }
Setting timeouts via the Firewall Optimiazation Options field is still created and applied as expected in 23.01-REL.
set optimization conservative
set timeout { udp.first 300, udp.single 150, udp.multiple 900 }
- Project changed from pfSense Plus to pfSense
- Subject changed from State timeouts in the gui under system/advanced/firewall&nat or not being set in pf. to Custom state timeouts are not saved
- Category changed from Web Interface to Web Interface
- Target version set to 2.7.0
- Affected Plus Version deleted (
23.01)
- Plus Target Version set to 23.05
- Affected Version set to 2.7.0
- Affected Architecture deleted (
amd64)
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied provided patch and nothing changes. After reboot all works good and timeouts are saves.
So, reboot required after apply patch.
aleksei prokofiev wrote in #note-5:
Applied provided patch and nothing changes. After reboot all works good and timeouts are saves.
So, reboot required after apply patch.
You don't need to reboot, you just need to go to Status > Filter Reload and click Reload Filter. Or you can click Save on System > Advanced, Firewall & NAT Tab.
- Assignee set to Jim Pingle
- Subject changed from Custom state timeouts are not saved to Custom default state timeouts are not respected in the ruleset
- Category changed from Web Interface to Rules / NAT
Applied the patch and it's working fine here even without a reboot.
- Status changed from Feedback to Resolved
The patch fixes the issue. I've just run the Status > Filter Reload after applying the patch.
I am marking this ticket resolved.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by