2.3 firewall rule state entry bug

xbipin

in 2.3 when u try to add max state value for match rules u get a php error, the part where it says u cant do that for match rules is fine

The following input errors were detected:

    The maximum state entries (advanced option) can only be specified for Pass type rules.

Warning: explode() expects parameter 2 to be string, array given in /usr/local/www/firewall_rules_edit.php on line 1208 Call Stack: 0.0013 133980 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.9376 1183020 2\. explode() /usr/local/www/firewall_rules_edit.php:1208

jimp

I can't seem to reproduce this as-is. What did you have selected exactly on the rule? That line is complaining about the interface selection. What was selected there?

Was this a new rule, or editing an existing rule?

heper

@jimp:

I can't seem to reproduce this as-is. What did you have selected exactly on the rule? That line is complaining about the interface selection. What was selected there?

Was this a new rule, or editing an existing rule?

can be reproduced like this:
-create floating rule

set to "match'
-select at least 1 interface
fill in a max state value (works on others input violations aswel)
hit save

https://redmine.pfsense.org/issues/6175
PR needs to be looked at closely for bugs

xbipin

i was editing a floating rule with the following things in it

match
apply immediately
LAN interface
direction in
ipv4
tcp/udp
source lan ip alias
destination invert match with remote server ip alias
in/out pipe for traffic shaping

these r the things set in the rule

heper

@xbipin it was fixed by Jorge M. Oliveira & steve_b

please confirm by gitsync or waiting for the next round of snapshots
https://redmine.pfsense.org/issues/6175