remove web interface section

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

diff --git a/pve-network.adoc b/pve-network.adoc
index 7221a871bc9a7388298a3dc9b863e390a132c906..bbaf0bc9e4fabc24d0562be19e0cfe21882aa616 100644 (file)
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -15,14 +15,14 @@ VLANs (IEEE 802.1q) and network bonding, also known as "link
 aggregation". That way it is possible to build complex and flexible
 virtual networks.
 
 aggregation". That way it is possible to build complex and flexible
 virtual networks.
 

-Debian traditionally uses the 'ifup' and 'ifdown' commands to
-configure the network. The file '/etc/network/interfaces' contains the
-whole network setup. Please refer to to manual page ('man interfaces')
+Debian traditionally uses the `ifup` and `ifdown` commands to
+configure the network. The file `/etc/network/interfaces` contains the
+whole network setup. Please refer to to manual page (`man interfaces`)

 for a complete format description.
 
 NOTE: {pve} does not write changes directly to
 for a complete format description.
 
 NOTE: {pve} does not write changes directly to

-'/etc/network/interfaces'. Instead, we write into a temporary file
-called '/etc/network/interfaces.new', and commit those changes when
+`/etc/network/interfaces`. Instead, we write into a temporary file
+called `/etc/network/interfaces.new`, and commit those changes when

 you reboot the node.
 
 It is worth mentioning that you can directly edit the configuration
 you reboot the node.
 
 It is worth mentioning that you can directly edit the configuration


@@ -30,6 +30,7 @@ file. All {pve} tools tries hard to keep such direct user
 modifications. Using the GUI is still preferable, because it
 protect you from errors.
 
 modifications. Using the GUI is still preferable, because it
 protect you from errors.
 

+

 Naming Conventions
 ~~~~~~~~~~~~~~~~~~
 
 Naming Conventions
 ~~~~~~~~~~~~~~~~~~
 


@@ -52,7 +53,7 @@ Default Configuration using a Bridge
 
 The installation program creates a single bridge named `vmbr0`, which
 is connected to the first ethernet card `eth0`. The corresponding
 
 The installation program creates a single bridge named `vmbr0`, which
 is connected to the first ethernet card `eth0`. The corresponding

-configuration in '/etc/network/interfaces' looks like this:
+configuration in `/etc/network/interfaces` looks like this:

 
 ----
 auto lo
 
 ----
 auto lo


@@ -87,13 +88,13 @@ TIP: Some providers allows you to register additional MACs on there
 management interface. This avoids the problem, but is clumsy to
 configure because you need to register a MAC for each of your VMs.
 
 management interface. This avoids the problem, but is clumsy to
 configure because you need to register a MAC for each of your VMs.
 

-You can avoid the problem by "routing" all traffic via a single
+You can avoid the problem by ``routing'' all traffic via a single

 interface. This makes sure that all network packets use the same MAC
 address.
 
 interface. This makes sure that all network packets use the same MAC
 address.
 

-A common scenario is that you have a public IP (assume 192.168.10.2
+A common scenario is that you have a public IP (assume `192.168.10.2`

 for this example), and an additional IP block for your VMs
 for this example), and an additional IP block for your VMs

-(10.10.10.1/255.255.255.0). We recommend the following setup for such
+(`10.10.10.1/255.255.255.0`). We recommend the following setup for such

 situations:
 
 ----
 situations:
 
 ----


@@ -118,8 +119,8 @@ iface vmbr0 inet static
 ----
 
 
 ----
 
 

-Masquerading (NAT) with iptables
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Masquerading (NAT) with `iptables`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 
 In some cases you may want to use private IPs behind your Proxmox
 host's true IP, and masquerade the traffic using NAT:
 
 In some cases you may want to use private IPs behind your Proxmox
 host's true IP, and masquerade the traffic using NAT: