Set-PveClusterSdnVnetsFirewallOptions
Set Firewall options.
API: PUT /cluster/sdn/vnets/{vnet}/firewall/options, Proxmox VE API viewer
Syntax
Section titled “Syntax”Set-PveClusterSdnVnetsFirewallOptions [-PveTicket <PveTicket>] [-Delete <string>] [-Digest <string>] [-Enable <bool>] [-LogLevelForward <string>] [-PolicyForward <string>] -Vnet <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. |
-Enable |
bool |
No | Enable/disable firewall rules. |
-LogLevelForward |
string |
No | Log level for forwarded traffic. Values: emerg, alert, crit, err, warning, notice, info, debug, nolog. |
-PolicyForward |
string |
No | Forward policy. Values: ACCEPT, DROP. |
-Vnet |
string |
Yes | The SDN vnet object identifier. |
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.