]> git.proxmox.com Git - pve-docs.git/commit
projects / pve-docs.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4371b2f) | patch
Add a paragraph to explain how network models match use cases
authorEmmanuel Kasper <e.kasper@proxmox.com>
Mon, 9 Oct 2017 09:08:38 +0000 (11:08 +0200)
committerFabian Grünbichler <f.gruenbichler@proxmox.com>
Tue, 10 Oct 2017 08:56:01 +0000 (10:56 +0200)
commit052130090ec7b76091a27c5f00927067dbd51e52
tree8e80fbfa20973c82a60b83f10e0a85a7f62b18a6tree
parent4371b2fe70f612f1a0e838dc1d76f04623734934commit | diff
Add a paragraph to explain how network models match use cases

Also :
 * explain more clearly when PVE switched to persistent device naming. (5.0)
 * use eno1 instead of eno0 everywhere when refering to the first onboard device
 * use IP addresses from the range IPv4 Address Blocks for Documentation
 (rfc5737) instead of private IPv4 addresses when giving examples of public IPs
pve-network.adoc diff | blob | blame | history
PVE Documentation