How to enable/disable existing firewall rules?

[winstonw]

Hello. Thank you for creating this awesome project.

How do I enable/disable an existing fw rule via pfsense-api?
I tried to make a PUT request to /api/v1/firewall/rule with payloads:
'{"tracker": "#######", "disable": false}' or
'{"tracker": "#######", "disable": true}'

Nothing changed on the pfSense web UI after successful requests.

Did I misunderstood anything?

[jaredhendrickson13]

Looks like you are using disable in your request body instead of disabled. Here's an example curl request I just used for disabling an existing firewall rule:

curl -s -k -u admin:pfsense -X PUT https://localhost/api/v1/firewall/rule -d '{"tracker": 1714079391, "disabled": true}'

After running, the rule now shows as disabled:

[winstonw]

My bad. I misread the property name from GET request result as "disable". The api now works as expected. Thank you.

[magtimmermans]

How will this work on V2?

This seems not work:
curl --location --request PATCH 'http:///api/v2/firewall/rule'
--header 'X-API-Key: '
--header 'Content-Type: application/json'
--data-raw '{
"id": 9,
"disabled": false
}'

result:
{
"code": 400,
"status": "bad request",
"response_id": "MODEL_REQUIRES_ID",
"message": "Field id is required.",
"data": []
}

[jaredhendrickson13]

The disabled field works the same as v1 with the exception of it being a PATCH request instead of PUT. However, the error you're getting suggests that the API is not receiving your request body at all. Looks like you're making the request using http? If so and your pfSense instance is using HTTPS, you must use HTTPS to make the API request. Otherwise, the HTTP redirect will strip the original request of its original method and request body.

[magtimmermans]

Thanks that seems the issue. I overlook this.