Replies: 3 comments
-
|
Use |
Beta Was this translation helpful? Give feedback.
-
|
Hi, In contrast, when creating the exact same rule through the GUI, the rule is correctly created in a disabled state in the Firewall Rules. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, The issue is that when creating the associated firewall rule, the disabled value is not passed, which causes the rule to always be created as enabled, regardless of the Port Forward rule state. The proposed fix is:
`if ($rule_q->exists()) { |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Does pfSense REST API v2 support creating a NAT port forward with Filter Rule Association (i.e. automatically generating and linking the firewall rule) just like the GUI option “Add associated filter rule”?
If so, how should the API request be structured?
If not, what is the recommended way to programmatically achieve the same behavior?
Beta Was this translation helpful? Give feedback.
All reactions