pve-docs/pve-firewall-rules-opts.adoc

`--dest` `<string>` ::

Restrict packet destination address. This can refer to a single IP address, an IP set ('+ipsetname') or an IP alias definition. You can also specify an address range like '20.34.101.207-201.3.9.99', or a list of IP addresses and networks (entries are separated by comma). Please do not mix IPv4 and IPv6 addresses inside such lists.

`--dport` `<string>` ::

Restrict TCP/UDP destination port. You can use service names or simple numbers (0-65535), as defined in '/etc/services'. Port ranges can be specified with '\d+:\d+', for example '80:85', and you can use comma separated list to match several ports or ranges.

`--icmp-type` `<string>` ::

Specify icmp-type. Only valid if proto equals 'icmp' or 'icmpv6'/'ipv6-icmp'.

`--iface` `<string>` ::

Network interface name. You have to use network configuration key names for VMs and containers ('net\d+'). Host related rules can use arbitrary strings.

`--log` `<alert | crit | debug | emerg | err | info | nolog | notice | warning>` ::

Log level for firewall rule.

`--proto` `<string>` ::

IP protocol. You can use protocol names ('tcp'/'udp') or simple numbers, as defined in '/etc/protocols'.

`--source` `<string>` ::

Restrict packet source address. This can refer to a single IP address, an IP set ('+ipsetname') or an IP alias definition. You can also specify an address range like '20.34.101.207-201.3.9.99', or a list of IP addresses and networks (entries are separated by comma). Please do not mix IPv4 and IPv6 addresses inside such lists.

`--sport` `<string>` ::

Restrict TCP/UDP source port. You can use service names or simple numbers (0-65535), as defined in '/etc/services'. Port ranges can be specified with '\d+:\d+', for example '80:85', and you can use comma separated list to match several ports or ranges.
update generated docs 2017-10-19 10:30:23 +03:00			`--dest` `<string>` ::
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update static/schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2022-04-04 15:16:48 +03:00			`Restrict packet destination address. This can refer to a single IP address, an IP set ('+ipsetname') or an IP alias definition. You can also specify an address range like '20.34.101.207-201.3.9.99', or a list of IP addresses and networks (entries are separated by comma). Please do not mix IPv4 and IPv6 addresses inside such lists.`
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update generated docs 2017-10-19 10:30:23 +03:00			`--dport` `<string>` ::
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update static/schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2022-04-04 15:16:48 +03:00			`Restrict TCP/UDP destination port. You can use service names or simple numbers (0-65535), as defined in '/etc/services'. Port ranges can be specified with '\d+:\d+', for example '80:85', and you can use comma separated list to match several ports or ranges.`
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update static and schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2020-11-24 16:31:57 +03:00			`--icmp-type` `<string>` ::

update static/schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2023-05-18 14:30:43 +03:00			`Specify icmp-type. Only valid if proto equals 'icmp' or 'icmpv6'/'ipv6-icmp'.`
update static and schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2020-11-24 16:31:57 +03:00
update generated docs 2017-10-19 10:30:23 +03:00			`--iface` `<string>` ::
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update static/schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2022-04-04 15:16:48 +03:00			`Network interface name. You have to use network configuration key names for VMs and containers ('net\d+'). Host related rules can use arbitrary strings.`
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
run make update Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2019-04-04 18:17:19 +03:00			`--log` `<alert \| crit \| debug \| emerg \| err \| info \| nolog \| notice \| warning>` ::

			`Log level for firewall rule.`

update generated docs 2017-10-19 10:30:23 +03:00			`--proto` `<string>` ::
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update static/schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2022-04-04 15:16:48 +03:00			`IP protocol. You can use protocol names ('tcp'/'udp') or simple numbers, as defined in '/etc/protocols'.`
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update generated docs 2017-10-19 10:30:23 +03:00			`--source` `<string>` ::
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update static/schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2022-04-04 15:16:48 +03:00			`Restrict packet source address. This can refer to a single IP address, an IP set ('+ipsetname') or an IP alias definition. You can also specify an address range like '20.34.101.207-201.3.9.99', or a list of IP addresses and networks (entries are separated by comma). Please do not mix IPv4 and IPv6 addresses inside such lists.`
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update generated docs 2017-10-19 10:30:23 +03:00			`--sport` `<string>` ::
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00
update static/schema information Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2022-04-04 15:16:48 +03:00			`Restrict TCP/UDP source port. You can use service names or simple numbers (0-65535), as defined in '/etc/services'. Port ranges can be specified with '\d+:\d+', for example '80:85', and you can use comma separated list to match several ports or ranges.`
auto-generate firewall rule options 2016-03-31 10:53:19 +03:00