From owner-svn-doc-all@FreeBSD.ORG Fri Feb 14 03:48:49 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A38C3181; Fri, 14 Feb 2014 03:48:49 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8E5DB18D7; Fri, 14 Feb 2014 03:48:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s1E3mnVM017834; Fri, 14 Feb 2014 03:48:49 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s1E3mntF017833; Fri, 14 Feb 2014 03:48:49 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201402140348.s1E3mntF017833@svn.freebsd.org> From: Warren Block Date: Fri, 14 Feb 2014 03:48:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43920 - head/en_US.ISO8859-1/books/handbook/advanced-networking X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 03:48:49 -0000 Author: wblock Date: Fri Feb 14 03:48:49 2014 New Revision: 43920 URL: http://svnweb.freebsd.org/changeset/doc/43920 Log: Whitespace-only fixes, translators please ignore. Slightly modified patch supplied by Allan Jude. Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Fri Feb 14 02:33:56 2014 (r43919) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Fri Feb 14 03:48:49 2014 (r43920) @@ -4,7 +4,10 @@ $FreeBSD$ --> - + + Advanced Networking @@ -89,9 +92,14 @@ Gateways and Routes - - CoranthGryphonContributed - by + + + + Coranth + Gryphon + + Contributed by + @@ -2264,10 +2272,18 @@ freebsdap 00:11:95:c3:0d:ac 1 Bluetooth - PavLucistnikWritten - by -
pav@FreeBSD.org
- + + + Pav + Lucistnik + + Written by + +
+ pav@FreeBSD.org +
+ + @@ -2404,8 +2420,8 @@ Name: Pav's T39 If an inquiry is performed on a remote Bluetooth device, it will find the computer as - your.host.name (ubt0). The name assigned to the - local device can be changed at any time. + your.host.name (ubt0). The name assigned to + the local device can be changed at any time. The Bluetooth system provides a point-to-point connection between two Bluetooth units, or a point-to-multipoint @@ -3397,86 +3413,86 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault loadbalance roundrobin - &os; provides the &man.lagg.4; interface which can be used - to aggregate multiple network interfaces into one virtual - interface in order to provide failover and link aggregation. - Failover allows traffic to continue to flow even if an - interface becomes available. Link aggregation works best on - switches which support LACP, as this - protocol distributes traffic bi-directionally while responding - to the failure of individual links. - - The aggregation protocols supported by the lagg interface - determine which ports are used for outgoing traffic and - whether or not a specific port accepts incoming traffic. The - following protocols are supported by &man.lagg.4;: - - - - failover - - This mode sends and receives traffic only through - the master port. If the master port becomes - unavailable, the next active port is used. The first - interface added to the virtual interface is the master - port and all subsequently added interfaces are used as - failover devices. If failover to a non-master port - occurs, the original port becomes master once it - becomes available again. - - + &os; provides the &man.lagg.4; interface which can be used + to aggregate multiple network interfaces into one virtual + interface in order to provide failover and link aggregation. + Failover allows traffic to continue to flow even if an + interface becomes available. Link aggregation works best on + switches which support LACP, as this + protocol distributes traffic bi-directionally while responding + to the failure of individual links. + + The aggregation protocols supported by the lagg interface + determine which ports are used for outgoing traffic and + whether or not a specific port accepts incoming traffic. The + following protocols are supported by &man.lagg.4;: + + + + failover + + This mode sends and receives traffic only through + the master port. If the master port becomes + unavailable, the next active port is used. The first + interface added to the virtual interface is the master + port and all subsequently added interfaces are used as + failover devices. If failover to a non-master port + occurs, the original port becomes master once it + becomes available again. + + - - fec / loadbalance - - &cisco; Fast ðerchannel; (FEC) - is found on older &cisco; switches. It provides a - static setup and does not negotiate aggregation with the - peer or exchange frames to monitor the link. If the - switch supports LACP, that should be - used instead. - - + + fec / loadbalance + + &cisco; Fast ðerchannel; (FEC) + is found on older &cisco; switches. It provides a + static setup and does not negotiate aggregation with the + peer or exchange frames to monitor the link. If the + switch supports LACP, that should be + used instead. + + - - lacp - - The &ieee; 802.3ad Link Aggregation Control Protocol - (LACP) negotiates a set of - aggregable links with the peer into one or more Link - Aggregated Groups (LAGs). Each - LAG is composed of ports of the same - speed, set to full-duplex operation, and traffic is - balanced across the ports in the - LAG with the greatest total speed. - Typically, there is only one LAG - which contains all the ports. In the event of changes - in physical connectivity, - LACP will quickly converge to a new - configuration. - - LACP balances outgoing traffic - across the active ports based on hashed protocol header - information and accepts incoming traffic from any active - port. The hash includes the Ethernet source and - destination address and, if available, the - VLAN tag, and the - IPv4 or IPv6 - source and destination address. - - + + lacp + + The &ieee; 802.3ad Link Aggregation Control Protocol + (LACP) negotiates a set of + aggregable links with the peer into one or more Link + Aggregated Groups (LAGs). Each + LAG is composed of ports of the same + speed, set to full-duplex operation, and traffic is + balanced across the ports in the + LAG with the greatest total speed. + Typically, there is only one LAG + which contains all the ports. In the event of changes + in physical connectivity, + LACP will quickly converge to a new + configuration. + + LACP balances outgoing traffic + across the active ports based on hashed protocol header + information and accepts incoming traffic from any active + port. The hash includes the Ethernet source and + destination address and, if available, the + VLAN tag, and the + IPv4 or IPv6 + source and destination address. + + - - roundrobin - - This mode distributes outgoing traffic using a - round-robin scheduler through all active ports and - accepts incoming traffic from any active port. Since - this mode violates Ethernet frame ordering, it should be - used with caution. - - - + + roundrobin + + This mode distributes outgoing traffic using a + round-robin scheduler through all active ports and + accepts incoming traffic from any active port. Since + this mode violates Ethernet frame ordering, it should be + used with caution. + + + Configuration Examples @@ -4234,12 +4250,19 @@ cd /usr/src/etc; make distribution PXE Booting with an <acronym>NFS</acronym> Root File - System + System - CraigRodrigues + + + Craig + Rodrigues + +
rodrigc@FreeBSD.org
- Written by + + Written by + @@ -4325,7 +4348,7 @@ cd /usr/src/etc; make distribution Rebuild the &os; kernel and userland (): + linkend="makeworld"/>): &prompt.root; cd /usr/src &prompt.root; make buildworld @@ -4980,16 +5003,31 @@ redirect_port tcp 192.168.0.3:80 80IPv6 - AaronKaplanOriginally - Written by + + + Aaron + Kaplan + + Originally Written by + - TomRhodesRestructured - and Added by + + + Tom + Rhodes + + Restructured and Added by + - BradDavisExtended - by + + + Brad + Davis + + Extended by + @@ -5011,26 +5049,26 @@ redirect_port tcp 192.168.0.3:80 80 - Running out of addresses. For years the use of - RFC1918 private address space (10.0.0.0/8, 172.16.0.0/12, and - 192.168.0.0/16) and NAT - has slowed down the exhaustion. Even though, there are - very few remaining IPv4 addresses. The Internet - Assigned Numbers Authority (IANA) has - issued the last of the available major blocks to the - Regional Registries. Once each Regional Registry runs - out, there will be no more available and switching to - IPv6 will be critical. + Running out of addresses. For years the use of + RFC1918 private address space (10.0.0.0/8, 172.16.0.0/12, and + 192.168.0.0/16) and NAT + has slowed down the exhaustion. Even though, there are + very few remaining IPv4 addresses. The Internet + Assigned Numbers Authority (IANA) has + issued the last of the available major blocks to the + Regional Registries. Once each Regional Registry runs + out, there will be no more available and switching to + IPv6 will be critical. - Every block of IPv4 addresses allocated required - routing information to be exchanged between many routers - on the Internet, and these routing tables were getting - too large to allow efficient routing. + Every block of IPv4 addresses allocated required + routing information to be exchanged between many routers + on the Internet, and these routing tables were getting + too large to allow efficient routing. @@ -5059,7 +5097,7 @@ redirect_port tcp 192.168.0.3:80 80 Address autoconfiguration (RFC2462). + xlink:href="http://www.ietf.org/rfc/rfc2462.txt">RFC2462). @@ -5096,7 +5134,7 @@ redirect_port tcp 192.168.0.3:80 80 KAME.net + xlink:href="http://www.kame.net">KAME.net @@ -5146,7 +5184,7 @@ redirect_port tcp 192.168.0.3:80 80128 bits unspecified Equivalent to 0.0.0.0 in + class="ipaddress">0.0.0.0 in IPv4. @@ -5155,7 +5193,7 @@ redirect_port tcp 192.168.0.3:80 80128 bits loopback address Equivalent to 127.0.0.1 in + class="ipaddress">127.0.0.1 in IPv4. @@ -5324,10 +5362,11 @@ redirect_port tcp 192.168.0.3:80 80 ipv6_enable="YES" - - - <acronym>IPv6</acronym> Client Static - Configuration + + + + <acronym>IPv6</acronym> Client Static + Configuration To statically assign the IPv6 address, @@ -5471,22 +5510,22 @@ redirect_port tcp 192.168.0.3:80 80 - - Application Use of <acronym>IPv6</acronym> + + Application Use of <acronym>IPv6</acronym> - Currently IPv6 support for many - applications and services is very good, though for some - software it still needs work. For authoritative - information about the support of - IPv6, please consult the Official - Documentation for the software in question. - - Web, DNS and Mail applications - and servers have the best support for - IPv6 because they are the most common - use case. Other applications may have varying degrees - of IPv6 support. - + Currently IPv6 support for many + applications and services is very good, though for some + software it still needs work. For authoritative information + about the support of IPv6, please consult + the Official Documentation for the software in + question. + + Web, DNS and Mail applications and + servers have the best support for IPv6 + because they are the most common use case. Other applications + may have varying degrees of IPv6 + support. +