From 001495909b0c11e21723671f541cae66912a40f4 Mon Sep 17 00:00:00 2001 From: Laine Stump Date: Wed, 9 Jan 2019 18:45:49 -0500 Subject: [PATCH] docs: add forgotten mentions of forward mode "open" MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit A couple places in the docs didn't get updated when the forward mode "open" was added. Signed-off-by: Laine Stump Reviewed-by: Daniel P. Berrangé --- docs/formatnetwork.html.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/formatnetwork.html.in b/docs/formatnetwork.html.in index 363a72bbc9..156cfae4ec 100644 --- a/docs/formatnetwork.html.in +++ b/docs/formatnetwork.html.in @@ -107,13 +107,13 @@ may also be connected to the LAN. When defining a new network with a <forward> mode of - "nat" or "route" (or an isolated network with + "nat", "route", or "open" (or an isolated network with no <forward> element), libvirt will automatically generate a unique name for the bridge device if none is given, and this name will be permanently stored in the network configuration so that that the same name will be used every time the network is started. For these types of networks - (nat, routed, and isolated), a bridge name beginning with the + (nat, route, open, and isolated), a bridge name beginning with the prefix "virbr" is recommended (and that is what is auto-generated), but not enforced. Attribute stp specifies if Spanning Tree Protocol -- 2.47.2