-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.4.3 Features & Fixes #248
Conversation
…upported since API v1.3.0.
This is blocked until pfSense Plus 22.05-RELEASE is fully released and tested. |
…pport for GET requests to /api/v1/interface/apply to check interface apply status.
Development Build 0pfSense 2.5:
pfSense 2.6:
pfSense 22.01:
pfSense-2.5-pkg-API-1.4_3dev_0.zip |
…php helper script.
Development Build 1pfSense 2.5:
pfSense 2.6:
pfSense 22.01:
pfSense-2.5-pkg-API-1.4_3dev_1.zip |
…for POST requests to /api/v1/interface/apply and slightly reworded the description.
…ices/openvpn/csc endpoint as /api/v1/openvpn/csc.
Development Build 2pfSense 2.5:
pfSense 2.6:
pfSense 22.01:
pfSense 22.05:
pfSense-2.5-pkg-API-1.4_3dev_2.zip |
async
property to POST requests to /api/v1/interface/apply to apply interfaces in the background (Applying many interfaces at once results in 504 gateway timeout #254)async
property to POST requests to /api/v1/services/unbound/apply to apply Unbound in the background (Applying many Unbound host overrides results in 504 gateway timeout #255)local-port
values to be set as port ranges in /api/v1/firewall/nat/port_forward. (/api/v1/firewall/nat/port_forward allows port range on localport field #253)Changes staged for v1.4.3 already merged into master:
allowed_interfaces
field asavailable_interfaces