You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
associated_rule_id gotten from /api/v2/firewall/nat/port_forwards
{
"code": 400,
"status": "bad request",
"response_id": "FIELD_INVALID_CHOICE",
"message": "Field `associated_rule_id` must be one of [, pass]",
"data": []
}.
To Reproduce
Steps to reproduce the behavior:
Go to pfsense api/documentation
Click on /api/v2/firewall/nat/port_forwards and execute
Get 'id' and 'associated_rule_id' of needed rule
Click on /api/v2/firewall/nat/port_forwards and execute
fill test json fields: id, associated_rule_id (because we cant go without it, but no reference about it in doc), disabled
See error
by the way everything is the same with python requests.
Expected behavior
not changing unnecessary fields.
if it really needed: using associated_rule_id from pfsense NAT rule or firewall rule id
Screenshots or Response
pfSense Version & Package Version:
pfSense Version: 2.7.2-RELEASE
Package Version v2.0.2
Affected Endpoints:
URL: /api/v2/firewall/nat/port_forwards
URL: /api/v2/firewall/nat/port_forward
Thanks in advance! Totaly cool pkg, by the way, really appreciate your work!
The text was updated successfully, but these errors were encountered:
This would be expected behavior as of right now. This endpoint currently only supports pass or an empty string (for unassociated filter rules) as the associated_rule_id:
If you added the port forward from the webConfigurator and set the 'Filter rule association' to 'Create a new associated filter rule', the endpoint will not accept the update until the associated_rule_id is changed to an option allowed by the REST API. You receive the error even with a partial update because the entire object still must be revalidated after any value changes to ensure there are no conflicts between existing values and changed values.
There is an open feature request (#275) to allow associated filter rules which should be picked up for v2.1.0. You can follow that issue for any updates.
Describe the bug
PATCH method on "/api/v2/firewall/nat/port_forward" , always getting error in "associated_rule_id" field.
associated_rule_id gotten from /api/v2/firewall/nat/port_forwards
To Reproduce
Steps to reproduce the behavior:
id
,associated_rule_id
(because we cant go without it, but no reference about it in doc),disabled
by the way everything is the same with python requests.
Expected behavior
not changing unnecessary fields.
if it really needed: using
associated_rule_id
from pfsense NAT rule or firewall ruleid
Screenshots or Response
pfSense Version & Package Version:
Affected Endpoints:
Thanks in advance! Totaly cool pkg, by the way, really appreciate your work!
The text was updated successfully, but these errors were encountered: