diff --git a/docs/formatnetwork.html.in b/docs/formatnetwork.html.in index 49206dda19..a3a5ced3e1 100644 --- a/docs/formatnetwork.html.in +++ b/docs/formatnetwork.html.in @@ -33,7 +33,7 @@
- <network> + <network ipv6='yes'> <name>default</name> <uuid>3e3fce45-4f53-4fa7-bb32-11f34168b82b</uuid> ...@@ -52,6 +52,12 @@ The format must be RFC 4122 compliant, eg
3e3fce45-4f53-4fa7-bb32-11f34168b82b
.
If omitted when defining/creating a new network, a random
UUID is generated. Since 0.3.0
+ ipv6='yes'
ipv6='yes'
enables
+ a network definition with no IPv6 gateway addresses specified
+ to have guest-to-guest communications. For further information,
+ see the example below for the example with no gateway addresses.
+ Since 1.0.1+ A valid network definition can contain no IPv4 or IPv6 addresses. Such a definition + can be used for a "very private" or "very isolated" network since it will not be + possible to communicate with the virtualization host via this network. However, + this virtual network interface can be used for communication between virtual guest + systems. This works for IPv4 and (Since 1.0.1) IPv6. + However, the new ipv6='yes' must be added for guest-to-guest IPv6 + communication. +
+ ++ <network ipv6='yes'> + <name>nogw</name> + <uuid>7a3b7497-1ec7-8aef-6d5c-38dff9109e93</uuid> + <bridge name="virbr2" stp="on" delay="0" /> + <mac address='00:16:3E:5D:C7:9E'/> + </network>+