Source string Read only

(itstool) path: listitem/para
30/300
Context English State
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 192.168.0.1</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 192.168.0.1:/b/tftpboot/FreeBSD/install /mnt</userinput>
<acronym>IPv6</acronym>
<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="http://www.ietf.org/rfc/rfc2462.txt">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="http://www.kame.net/">http://www.kame.net/</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.
Background on <acronym>IPv6</acronym> Addresses
There are three different types of <acronym>IPv6</acronym> addresses:
Unicast
A packet sent to a unicast address arrives at the interface belonging to the address.
Anycast
These addresses are syntactically indistinguishable from unicast addresses but they address a group of interfaces. The packet destined for an anycast address will arrive at the nearest router interface. Anycast addresses are only used by routers.
Multicast
These addresses identify a group of interfaces. A packet destined for a multicast address will arrive at all interfaces belonging to the multicast group. The <acronym>IPv4</acronym> broadcast address, usually <systemitem class="ipaddress">xxx.xxx.xxx.255</systemitem>, is expressed by multicast addresses in <acronym>IPv6</acronym>.
When reading an <acronym>IPv6</acronym> address, the canonical form is represented as <systemitem>x:x:x:x:x:x:x:x</systemitem>, where each <literal>x</literal> represents a 16 bit hex value. An example is <systemitem>FEBC:A574:382B:23C1:AA49:4592:4EFE:9982</systemitem>.
Often, an address will have long substrings of all zeros. A <literal>::</literal> (double colon) can be used to replace one substring per address. Also, up to three leading <literal>0</literal>s per hex value can be omitted. For example, <systemitem>fe80::1</systemitem> corresponds to the canonical form <systemitem>fe80:0000:0000:0000:0000:0000:0000:0001</systemitem>.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: listitem/para
Flags
read-only
Source string location
book.translate.xml:65535
String age
a year ago
Source string age
a year ago
Translation file
books/handbook.pot, string 11175