update copyright year to current

[pve-docs.git] / pve-firewall.adoc

diff --git a/pve-firewall.adoc b/pve-firewall.adoc
index 5c8587748a06b9c3a54f850042a5919a77127320..bc9df0e6ca736eec01d9992648c99fb8ff9b069f 100644 (file)
--- a/pve-firewall.adoc
+++ b/pve-firewall.adoc
@@ -1,7 +1,8 @@
+[[chapter_pve_firewall]]

 ifdef::manvolnum[]
 ifdef::manvolnum[]

-PVE({manvolnum})
-================
-include::attributes.txt[]
+pve-firewall(8)
+===============
+:pve-toplevel:

 
 NAME
 ----
 
 NAME
 ----


@@ -9,7 +10,7 @@ NAME
 pve-firewall - PVE Firewall Daemon
 
 
 pve-firewall - PVE Firewall Daemon
 
 

-SYNOPSYS
+SYNOPSIS

 --------
 
 include::pve-firewall.8-synopsis.adoc[]
 --------
 
 include::pve-firewall.8-synopsis.adoc[]


@@ -18,14 +19,16 @@ include::pve-firewall.8-synopsis.adoc[]
 DESCRIPTION
 -----------
 endif::manvolnum[]
 DESCRIPTION
 -----------
 endif::manvolnum[]

-

 ifndef::manvolnum[]
 {pve} Firewall
 ==============
 ifndef::manvolnum[]
 {pve} Firewall
 ==============

-include::attributes.txt[]
+:pve-toplevel:

 endif::manvolnum[]
 endif::manvolnum[]

+ifdef::wiki[]
+:title: Firewall
+endif::wiki[]

 
 

-Proxmox VE Firewall provides an easy way to protect your IT
+{pve} Firewall provides an easy way to protect your IT

 infrastructure. You can setup firewall rules for all hosts
 inside a cluster, or define rules for virtual machines and
 containers. Features like firewall macros, security groups, IP sets
 infrastructure. You can setup firewall rules for all hosts
 inside a cluster, or define rules for virtual machines and
 containers. Features like firewall macros, security groups, IP sets


@@ -67,8 +70,8 @@ file system. So those files are automatically distributed to all
 cluster nodes, and the `pve-firewall` service updates the underlying
 `iptables` rules automatically on changes.
 
 cluster nodes, and the `pve-firewall` service updates the underlying
 `iptables` rules automatically on changes.
 

-You can configure anything using the GUI (i.e. Datacenter -> Firewall,
-or on a Node -> Firewall), or you can edit the configuration files
+You can configure anything using the GUI (i.e. *Datacenter* -> *Firewall*,
+or on a *Node* -> *Firewall*), or you can edit the configuration files

 directly using your preferred editor.
 
 Firewall configuration files contains sections of key-value
 directly using your preferred editor.
 
 Firewall configuration files contains sections of key-value


@@ -77,6 +80,7 @@ comments. Sections starts with a header line containing the section
 name enclosed in `[` and `]`.
 
 
 name enclosed in `[` and `]`.
 
 

+[[pve_firewall_cluster_wide_setup]]

 Cluster Wide Setup
 ~~~~~~~~~~~~~~~~~~
 
 Cluster Wide Setup
 ~~~~~~~~~~~~~~~~~~
 


@@ -139,6 +143,7 @@ To simplify that task, you can instead create an IPSet called
 firewall rules to access the GUI from remote.
 
 
 firewall rules to access the GUI from remote.
 
 

+[[pve_firewall_host_specific_configuration]]

 Host Specific Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Host Specific Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 


@@ -160,7 +165,7 @@ include::pve-firewall-host-opts.adoc[]
 
 This sections contains host specific firewall rules.
 
 
 This sections contains host specific firewall rules.
 

-
+[[pve_firewall_vm_container_configuration]]

 VM/Container Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 VM/Container Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 


@@ -196,10 +201,6 @@ Each virtual network device has its own firewall enable flag. So you
 can selectively enable the firewall for each interface. This is
 required in addition to the general firewall `enable` option.
 
 can selectively enable the firewall for each interface. This is
 required in addition to the general firewall `enable` option.
 

-The firewall requires a special network device setup, so you need to
-restart the VM/container after enabling the firewall on a network
-interface.
-

 
 Firewall Rules
 --------------
 
 Firewall Rules
 --------------


@@ -242,6 +243,7 @@ OUT ACCEPT # accept all outgoing packages
 ----
 
 
 ----
 
 

+[[pve_firewall_security_groups]]

 Security Groups
 ---------------
 
 Security Groups
 ---------------
 


@@ -266,7 +268,7 @@ Then, you can add this group to a VM's firewall
 GROUP webserver
 ----
 
 GROUP webserver
 ----
 

-
+[[pve_firewall_ip_aliases]]

 IP Aliases
 ----------
 
 IP Aliases
 ----------
 


@@ -304,7 +306,7 @@ explicitly assign the local IP address
 local_network 1.2.3.4 # use the single ip address
 ----
 
 local_network 1.2.3.4 # use the single ip address
 ----
 

-
+[[pve_firewall_ip_sets]]

 IP Sets
 -------
 
 IP Sets
 -------
 


@@ -352,7 +354,7 @@ Traffic from these IPs is dropped by every host's and VM's firewall.
 ----
 
 
 ----
 
 

-[[ipfilter-section]]
+[[pve_firewall_ipfilter_section]]

 Standard IP set `ipfilter-net*`
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Standard IP set `ipfilter-net*`
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 


@@ -362,7 +364,7 @@ with a source IP not matching its interface's corresponding ipfilter set will
 be dropped.
 
 For containers with configured IP addresses these sets, if they exist (or are
 be dropped.
 
 For containers with configured IP addresses these sets, if they exist (or are

-activated via the general `IP Filter` option in the VM's firewall's 'options'
+activated via the general `IP Filter` option in the VM's firewall's *options*

 tab), implicitly contain the associated IP addresses.
 
 For both virtual machines and containers they also implicitly contain the
 tab), implicitly contain the associated IP addresses.
 
 For both virtual machines and containers they also implicitly contain the


@@ -458,68 +460,6 @@ NFQUEUE=0
 ----
 
 
 ----
 
 

-Avoiding `link-local` Addresses on `tap` and `veth` Devices
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-With IPv6 enabled by default every interface gets a MAC-derived link local
-address. However, most devices on a typical {pve} setup are connected to a
-bridge and so the bridge is the only interface which really needs one.
-
-To disable a link local address on an interface you can set the interface's
-`disable_ipv6` sysconf variable. Despite the name, this does not prevent IPv6
-traffic from passing through the interface when routing or bridging, so the
-only noticeable effect will be the removal of the link local address.
-
-The easiest method of achieving this setting for all newly started VMs is to
-set it for the `default` interface configuration and enabling it explicitly on
-the interfaces which need it. This is also the case for other settings such as
-`forwarding`, `accept_ra` or `autoconf`.
-
-Here's a possible setup:
-----
-# /etc/sysconf.d/90-ipv6.conf
-
-net.ipv6.conf.default.forwarding = 0
-net.ipv6.conf.default.proxy_ndp = 0
-net.ipv6.conf.default.autoconf = 0
-net.ipv6.conf.default.disable_ipv6 = 1
-net.ipv6.conf.default.accept_ra = 0
-
-net.ipv6.conf.lo.disable_ipv6 = 0
-----
-
-----
-# /etc/network/interfaces
-(...)
-# Dual stack:
-iface vmbr0 inet static
-    address 1.2.3.4
-    netmask 255.255.255.128
-    gateway 1.2.3.5
-iface vmbr0 inet6 static
-    address fc00::31
-    netmask 16
-    gateway fc00::1
-    accept_ra 0
-    pre-up echo 0 > /proc/sys/net/ipv6/conf/$IFACE/disable_ipv6
-
-# With IPv6-only 'pre-up' is too early and 'up' is too late.
-# Work around this by creating the bridge manually
-iface vmbr1 inet manual
-    pre-up ip link add $IFACE type bridge
-    up echo 0 > /proc/sys/net/ipv6/conf/$IFACE/disable_ipv6
-iface vmbr1 inet6 static
-    address fc00:b:3::1
-    netmask 96
-    bridge_ports none
-    bridge_stp off
-    bridge_fd 0
-    bridge_vlan_aware yes
-    accept_ra 0
-(...)
-----
-
-

 Notes on IPv6
 -------------
 
 Notes on IPv6
 -------------
 


@@ -543,11 +483,11 @@ As for the link local addresses required for NDP, there's also an ``IP Filter''
 (`ipfilter: 1`) option which can be enabled which has the same effect as adding
 an `ipfilter-net*` ipset for each of the VM's network interfaces containing the
 corresponding link local addresses.  (See the
 (`ipfilter: 1`) option which can be enabled which has the same effect as adding
 an `ipfilter-net*` ipset for each of the VM's network interfaces containing the
 corresponding link local addresses.  (See the

-<<ipfilter-section,Standard IP set `ipfilter-net*`>> section for details.)
+<<pve_firewall_ipfilter_section,Standard IP set `ipfilter-net*`>> section for details.)

 
 
 
 

-Ports used by Proxmox VE
-------------------------
+Ports used by {pve}
+-------------------

 
 * Web interface: 8006
 * VNC Web console: 5900-5999
 
 * Web interface: 8006
 * VNC Web console: 5900-5999