Rules don't seem to commit until I reboot

[gavpop]

I'm creating some firewall rules with NAT'ing.
This is on a brand new 2.4.3 release of PFSense.
No matter what I do, rules don't seem to commit until after I've rebooted the firewall.

I've reset the states.
I've watched the filter reload - no errors.

Here is one of my rules...

NAT -

Firewall -

I'm at a loss.

[SammyWoo]

@gavpop Don't know the details but I wouldn't be surprised, sometimes rules have dependencies. Stuff have to reset/restart from a known state.

[Gertjan]

@gavpop said in Rules don't seem to commit until I reboot:

ere is one of my rules...
NAT -
Firewall -
I'm at a loss.

When creating a NAT rule, something like :

(see the second one - deactivated, but valid)

the related firewall rule is created automatically.
This image
in front of the rule is important !! This means the two are linked-related.

The auto-created related firewall rule (third one) :

[Derelict]

@gavpop said in Rules don't seem to commit until I reboot:

I'm creating some firewall rules with NAT'ing.
This is on a brand new 2.4.3 release of PFSense.
No matter what I do, rules don't seem to commit until after I've rebooted the firewall.

I've reset the states.
I've watched the filter reload - no errors.

Here is one of my rules...

NAT -

Firewall -

I'm at a loss.

If you look at OP's ruleset you will see that he is port forwarding WAN Address port 9987 to 192.0.0.60 port 443. The firewall rule passes destination 192.0.0.60 port 9987. That should be passing the post-NAT address and port, or 192.0.0.60 port 443.

No idea what rebooting had to do with anything. That would never work.