Set-PveClusterFirewallOptions
Set Firewall options.
API: PUT /cluster/firewall/options, Proxmox VE API viewer
Syntax
Section titled “Syntax”Set-PveClusterFirewallOptions [-PveTicket <PveTicket>] [-Delete <string>] [-Digest <string>] [-Ebtables <bool>] [-Enable <int>] [-LogRatelimit <string>] [-PolicyForward <string>] [-PolicyIn <string>] [-PolicyOut <string>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Delete |
string |
No | A list of settings you want to delete. |
-Digest |
string |
No | Prevent changes if current configuration file has a different digest. This can be used to prevent concurrent modifications. |
-Ebtables |
bool |
No | Enable ebtables rules cluster wide. |
-Enable |
int |
No | Enable or disable the firewall cluster wide. |
-LogRatelimit |
string |
No | Log ratelimiting settings. |
-PolicyForward |
string |
No | Forward policy. Values: ACCEPT, DROP. |
-PolicyIn |
string |
No | Input policy. Values: ACCEPT, REJECT, DROP. |
-PolicyOut |
string |
No | Output policy. Values: ACCEPT, REJECT, DROP. |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.