2.4.3 upgrade and rules applying not working
-
Hi
i've just upgraded to 2.4.3 from 2.4.2
now when i change a rule and apply it, i need to reboot the pfsense to make it work
what's happening ?
does anyone have the same issue ?
-
I'm having sort of the same issue whereas I create a new rule, reload the filter and get this notification
/var/db/notices_lastmsg.txt:4:22:38:51 There were error(s) loading the rules: /tmp/rules.debug:166: unknown protocol tcp4 - The line in question reads [166]: pass in quick on $WAN reply-to ( bce0 1.2.3.4 ) inet proto tcp4 from any to 1.2.3.4 tracker 1523226536 keep state label "USER_RULE: OpenVPN wizard"
I have not tried to reboot the pfsense itself as its running on an enterprise grade server which takes time to reboot and I'm too lazy to explain the outage to my wife :P
-
Edit that rule, change protocol from any to TCP and save.
There is a bug in the OpenVPN wizard that is creating an invalid rule.
-
Edit that rule, change protocol from any to TCP and save.
There is a bug in the OpenVPN wizard that is creating an invalid rule.
That worked, thanks!
-
Hi
i've just upgraded to 2.4.3 from 2.4.2
now when i change a rule and apply it, i need to reboot the pfsense to make it work
what's happening ?
does anyone have the same issue ?
Here's the error :
There were error(s) loading the rules: /tmp/rules.debug:24: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [24]: table persist file "/etc/bogonsv6"
-
Yeah. That is completely different.
-
Tricky situation
-
if increase the maximum entries size from 200k to 400k, then rules modification and filters reload work without need of reboot
-
BUT, then i lose all my bandwidht, cominf from 140Mb/s to 1Mb/s
-
if i use back 200k instead of 400k, then i have the bug for filter reload, but my bandwidht is back to 140mb/s !!!
-
-
I can't see how maximum states is linked to bandwidth. They should operate exactly the same until a threshold condition is reached.
