--- docs/formatnetwork.html.in | 102 +++++++++++++++++++++++--------------------- 1 files changed, 53 insertions(+), 49 deletions(-) diff --git a/docs/formatnetwork.html.in b/docs/formatnetwork.html.in index 93b0ebe..f9421c3 100644 --- a/docs/formatnetwork.html.in +++ b/docs/formatnetwork.html.in @@ -184,55 +184,59 @@ <code>dhcp</code> or <code>tftp</code> element. <span class="since">Since 0.3.0; IPv6, multiple addresses on a single network, <code>family</code>, and <code>prefix</code> since 0.8.7</span> - <dl> - <dt><code>tftp</code></dt><dd>Immediately within - the <code>ip</code> element there is an optional <code>tftp</code> - element. The presence of this element and of its attribute - <code>root</code> enables TFTP services. The attribute specifies - the path to the root directory served via TFTP. <code>tftp</code> is not - supported for IPv6 addresses, and can only be specified on a single IPv4 address - per network. - <span class="since">Since 0.7.1</span> - </dd> - <dt><code>dhcp</code></dt> - <dd>Also within the <code>ip</code> element there is an - optional <code>dhcp</code> element. The presence of this element - enables DHCP services on the virtual network. It will further - contain one or more <code>range</code> elements. The - <code>dhcp</code> element is not supported for IPv6, and - is only supported on a single IP address per network for IPv4. - <span class="since">Since 0.3.0</span> - <dl> - <dt><code>range</code></dt> - <dd>The <code>start</code> and <code>end</code> attributes on the - <code>range</code> element specify the boundaries of a pool of - IPv4 addresses to be provided to DHCP clients. These two addresses - must lie within the scope of the network defined on the parent - <code>ip</code> element. <span class="since">Since 0.3.0</span> - </dd> - <dt><code>host</code></dt> - <dd>Within the <code>dhcp</code> element there may be zero or more - <code>host</code> elements; these specify hosts which will be given - names and predefined IP addresses by the built-in DHCP server. Any - such element must specify the MAC address of the host to be assigned - a given name (via the <code>mac</code> attribute), the IP to be - assigned to that host (via the <code>ip</code> attribute), and the - name to be given that host by the DHCP server (via the - <code>name</code> attribute). <span class="since">Since 0.4.5</span> - </dd><dt><code>bootp</code></dt><dd>The optional <code>bootp</code> - element specifies BOOTP options to be provided by the DHCP server. - Two attributes are supported: <code>file</code> is mandatory and - gives the file to be used for the boot image; <code>server</code> is - optional and gives the address of the TFTP server from which the boot - image will be fetched. <code>server</code> defaults to the same host - that runs the DHCP server, as is the case when the <code>tftp</code> - element is used. The BOOTP options currently have to be the same - for all address ranges and statically assigned addresses.<span - class="since">Since 0.7.1 (<code>server</code> since 0.7.3).</span> - </dl> - </dd> - </dd> - </dl> + <dl> + <dt><code>tftp</code></dt> + <dd>Immediately within + the <code>ip</code> element there is an optional <code>tftp</code> + element. The presence of this element and of its attribute + <code>root</code> enables TFTP services. The attribute specifies + the path to the root directory served via TFTP. <code>tftp</code> is not + supported for IPv6 addresses, and can only be specified on a single IPv4 address + per network. + <span class="since">Since 0.7.1</span> + </dd> + + <dt><code>dhcp</code></dt> + <dd>Also within the <code>ip</code> element there is an + optional <code>dhcp</code> element. The presence of this element + enables DHCP services on the virtual network. It will further + contain one or more <code>range</code> elements. The + <code>dhcp</code> element is not supported for IPv6, and + is only supported on a single IP address per network for IPv4. + <span class="since">Since 0.3.0</span> + <dl> + <dt><code>range</code></dt> + <dd>The <code>start</code> and <code>end</code> attributes on the + <code>range</code> element specify the boundaries of a pool of + IPv4 addresses to be provided to DHCP clients. These two addresses + must lie within the scope of the network defined on the parent + <code>ip</code> element. <span class="since">Since 0.3.0</span> + </dd> + <dt><code>host</code></dt> + <dd>Within the <code>dhcp</code> element there may be zero or more + <code>host</code> elements; these specify hosts which will be given + names and predefined IP addresses by the built-in DHCP server. Any + such element must specify the MAC address of the host to be assigned + a given name (via the <code>mac</code> attribute), the IP to be + assigned to that host (via the <code>ip</code> attribute), and the + name to be given that host by the DHCP server (via the + <code>name</code> attribute). <span class="since">Since 0.4.5</span> + </dd> + <dt><code>bootp</code></dt> + <dd>The optional <code>bootp</code> + element specifies BOOTP options to be provided by the DHCP server. + Two attributes are supported: <code>file</code> is mandatory and + gives the file to be used for the boot image; <code>server</code> is + optional and gives the address of the TFTP server from which the boot + image will be fetched. <code>server</code> defaults to the same host + that runs the DHCP server, as is the case when the <code>tftp</code> + element is used. The BOOTP options currently have to be the same + for all address ranges and statically assigned addresses.<span + class="since">Since 0.7.1 (<code>server</code> since 0.7.3).</span> + </dd> + </dl> + </dd> + </dl> </dd> </dl> -- 1.7.3.4 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list