The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: step/para
Context English State
Then start the <acronym>DHCP</acronym> service:
Debugging <acronym>PXE</acronym> Problems
Once all of the services are configured and started, <acronym>PXE</acronym> clients should be able to automatically load FreeBSD over the network. If a particular client is unable to connect, when that client machine boots up, enter the <acronym>BIOS</acronym> configuration menu and confirm that it is set to boot from the network.
This section describes some troubleshooting tips for isolating the source of the configuration problem should no clients be able to <acronym>PXE</acronym> boot.
Use the <package>net/wireshark</package> package or port to debug the network traffic involved during the <acronym>PXE</acronym> booting process, which is illustrated in the diagram below.
<acronym>PXE</acronym> Booting Process with <acronym>NFS</acronym> Root Mount
_ external ref='advanced-networking/pxe-nfs' md5='__failed__'
Client broadcasts a <literal>DHCPDISCOVER</literal> message.
The <acronym>DHCP</acronym> server responds with the <acronym>IP</acronym> address, <literal>next-server</literal>, <literal>filename</literal>, and <literal>root-path</literal> values.
The client sends a <acronym>TFTP</acronym> request to <literal>next-server</literal>, asking to retrieve <literal>filename</literal>.
The <acronym>TFTP</acronym> server responds and sends <literal>filename</literal> to client.
The client executes <literal>filename</literal>, which is <citerefentry><refentrytitle>pxeboot</refentrytitle><manvolnum>8</manvolnum></citerefentry>, which then loads the kernel. When the kernel executes, the root file system specified by <literal>root-path</literal> is mounted over <acronym>NFS</acronym>.
On the <acronym>TFTP</acronym> server, read <filename>/var/log/xferlog</filename> to ensure that <filename>pxeboot</filename> is being retrieved from the correct location. To test this example configuration:
<prompt>#</prompt> <userinput>tftp</userinput>
tftp&gt; <userinput>get FreeBSD/install/boot/pxeboot</userinput>
Received 264951 bytes in 0.1 seconds
The <literal>BUGS</literal> sections in <citerefentry><refentrytitle>tftpd</refentrytitle><manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>tftp</refentrytitle><manvolnum>1</manvolnum></citerefentry> document some limitations with <acronym>TFTP</acronym>.
Make sure that the root file system can be mounted via <acronym>NFS</acronym>. To test this example configuration:
<prompt>#</prompt> <userinput>mount -t nfs /mnt</userinput>
<personname> <firstname>Aaron</firstname> <surname>Kaplan</surname> </personname> <contrib>Originally Written by </contrib>
<personname> <firstname>Tom</firstname> <surname>Rhodes</surname> </personname> <contrib>Restructured and Added by </contrib>
<personname> <firstname>Brad</firstname> <surname>Davis</surname> </personname> <contrib>Extended by </contrib>
<acronym>IPv6</acronym> is the new version of the well known <acronym>IP</acronym> protocol, also known as <acronym>IPv4</acronym>. <acronym>IPv6</acronym> provides several advantages over <acronym>IPv4</acronym> as well as many new features:
Its 128-bit address space allows for 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses. This addresses the <acronym>IPv4</acronym> address shortage and eventual <acronym>IPv4</acronym> address exhaustion.
Routers only store network aggregation addresses in their routing tables, thus reducing the average space of a routing table to 8192 entries. This addresses the scalability issues associated with <acronym>IPv4</acronym>, which required every allocated block of <acronym>IPv4</acronym> addresses to be exchanged between Internet routers, causing their routing tables to become too large to allow efficient routing.
Address autoconfiguration (<link xlink:href="">RFC2462</link>).
Mandatory multicast addresses.
Built-in <acronym>IPsec</acronym> (<acronym>IP</acronym> security).
Simplified header structure.
Support for mobile <acronym>IP</acronym>.
<acronym>IPv6</acronym>-to-<acronym>IPv4</acronym> transition mechanisms.
FreeBSD includes the <link xlink:href=""></link> <acronym>IPv6</acronym> reference implementation and comes with everything needed to use <acronym>IPv6</acronym>. This section focuses on getting <acronym>IPv6</acronym> configured and running.


No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: step/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
books/handbook.pot, string 11165