libvirt/tests/networkxml2xmlin/empty-allow-ipv6.xml

<network ipv6='yes'>
  <name>empty</name>
  <uuid>81ff0d90-c91e-6742-64da-4a736edb9a9c</uuid>
  <bridge name='virbr7' />
  <mac address='52:54:00:17:3F:47'/>
</network>
network: allow guest to guest IPv6 without gateway definition This patch adds the capability for virtual guests to do IPv6 communication via a virtual network interface with no IPv6 (gateway) addresses specified. This capability has always been enabled by default for IPv4, but disabled for IPv6 for security concerns, and because it requires the ip6tables command to be operational (which isn't the case on a system with the ipv6 module completely disabled). This patch adds a new attribute "ipv6" at the toplevel of a <network> object. If ipv6='yes', the extra ip6tables rules required to permite inter-guest communications are added when the network is started. If it is 'no', or not present, those rules will not be added; thus the default behavior doesn't change, so there should be no compatibility issues with any existing installations. Note that virtual guests cannot communication with the virtualization host via this interface, because the following kernel tunable has been set: net.ipv6.conf.<bridge_interface_name>.disable_ipv6 = 1 This assures that the bridge interface will not have an IPv6 link-local (fe80::) address. To control this behavior so that it is not enabled by default, the parameter ipv6='yes' on the <network> statement has been added. Documentation related to this patch has been updated. The network schema has also been updated. 2012-12-04 00:13:36 +08:00			`<network ipv6='yes'>`
			`<name>empty</name>`
			`<uuid>81ff0d90-c91e-6742-64da-4a736edb9a9c</uuid>`
			`<bridge name='virbr7' />`
			`<mac address='52:54:00:17:3F:47'/>`
			`</network>`