projects
/
pve-docs.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
61105e4
)
pve-network.adoc: vlan - s/Nic/NIC/
author
Dietmar Maurer
<dietmar@proxmox.com>
Mon, 12 Feb 2018 05:50:11 +0000
(06:50 +0100)
committer
Dietmar Maurer
<dietmar@proxmox.com>
Mon, 12 Feb 2018 05:50:11 +0000
(06:50 +0100)
pve-network.adoc
patch
|
blob
|
blame
|
history
diff --git
a/pve-network.adoc
b/pve-network.adoc
index 424af01a529fc1d64c6e056f5979d4bb1ac3458e..243ab88ad58349907d3562df5e0bd25c184f2c26 100644
(file)
--- a/
pve-network.adoc
+++ b/
pve-network.adoc
@@
-356,7
+356,7
@@
Each VLAN network is identified by a number often called 'tag'.
Network packages are then 'tagged' to identify which virtual
network they belong to.
-One or more VLANs can be used at any network device (N
ic
, Bond, Bridge).
+One or more VLANs can be used at any network device (N
IC
, Bond, Bridge).
VLANs can be configured in several ways. Here, only the most common ones get
described. We assume a network infrastructure based on Linux Kernel Networking
(opposed to, e.g., Open vSwitch).