From owner-svn-doc-all@FreeBSD.ORG Tue Apr 1 23:24:54 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE166151; Tue, 1 Apr 2014 23:24:54 +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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8ABCA7B; Tue, 1 Apr 2014 23:24:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s31NOs6B040222; Tue, 1 Apr 2014 23:24:54 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s31NOsUN040221; Tue, 1 Apr 2014 23:24:54 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404012324.s31NOsUN040221@svn.freebsd.org> From: Dru Lavigne Date: Tue, 1 Apr 2014 23:24:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44415 - 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: Tue, 01 Apr 2014 23:24:54 -0000 Author: dru Date: Tue Apr 1 23:24:54 2014 New Revision: 44415 URL: http://svnweb.freebsd.org/changeset/doc/44415 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems 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 Tue Apr 1 23:03:08 2014 (r44414) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Tue Apr 1 23:24:54 2014 (r44415) @@ -489,10 +489,10 @@ static_routes="internalnet2" route_internalnet2="-net 192.168.2.0/24 192.168.1.2" The static_routes configuration - variable is a list of strings separated by a space, where - each string references a route name. The variable - route_internalnet2 contains the static - route for that route name. + variable is a list of strings separated by a space, where each + string references a route name. The variable + route_internalnet2 + contains the static route for that route name. Using more than one string in static_routes creates multiple static @@ -2009,7 +2009,8 @@ wpa_pairwise=CCMP TKIP for more details. It is possible to see the stations associated with the - AP using ifconfig wlan0 list + AP using ifconfig + wlan0 list sta. @@ -2143,7 +2144,8 @@ freebsdap 00:11:95:c3:0d:ac 1 Debugging messages can be enabled in the 802.11 protocol support layer using &man.wlandebug.8;. On a &os; system prior to &os; 9.1, this program can be found in - /usr/src/tools/tools/net80211. + /usr/src/tools/tools/net80211. For example, to enable console messages related to scanning for access points and the 802.11 protocol handshakes required to arrange communication: @@ -2151,9 +2153,9 @@ freebsdap 00:11:95:c3:0d:ac 1 &prompt.root; wlandebug -i ath0 +scan+auth+debug+assoc net.wlan.0.debug: 0 => 0xc80000<assoc,auth,scan> - Many useful statistics are maintained by - the 802.11 layer and wlanstats, found - in /usr/src/tools/tools/net80211, + Many useful statistics are maintained by the 802.11 + layer and wlanstats, found in /usr/src/tools/tools/net80211, will dump this information. These statistics should display all errors identified by the 802.11 layer. However, some errors are identified in the device drivers @@ -3211,7 +3213,7 @@ bridge0: flags=8843<UP,BROADCAST,RUNN beginning # symbol: begemotSnmpdModulePath."bridge" = "/usr/lib/snmp_bridge.so" - + Other configuration settings, such as community names and access lists, may need to be modified in this file. See &man.bsnmpd.1; and &man.snmp.bridge.3; for more information. @@ -3329,16 +3331,17 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault &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 as long as at least one - aggregated network interface has an established link. Link aggregation works best on - switches which support LACP, as this - protocol distributes traffic bi-directionally while responding - to the failure of individual links. + Failover allows traffic to continue to flow as long as at least + one aggregated network interface has an established link. 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;: + 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;: @@ -4905,74 +4908,71 @@ route_hostD="192.168.173.4 hatm0 0 102 l (CARP) allows multiple hosts to share the same IP address and Virtual Host ID (VHID) in order to provide high - availability for one or more services. This means that one or more - hosts can fail, and the - other hosts will transparently take over so that users do not see a service + availability for one or more services. This means + that one or more hosts can fail, and the other hosts will + transparently take over so that users do not see a service failure. - - In - addition to the shared IP address, each host - has its own IP address for management and - configuration. All of the machines that share an - IP address have the same - VHID. The VHID for each - virtual IP address must be unique across - the broadcast domain of the network interface. + + In addition to the shared IP address, + each host has its own IP address for + management and configuration. All of the machines that share an + IP address have the same + VHID. The VHID for each + virtual IP address must be unique across the + broadcast domain of the network interface. High availability using CARP is built into &os;, though the steps to configure it vary slightly depending upon the &os; version. This section provides the same example configuration for versions before and equal to or after - &os; 10. + &os; 10. - This example - configures failover support with three hosts, all with unique - IP addresses, but providing the same web - content. It has two different masters named - hosta.example.org and - hostb.example.org, with - a shared backup named - hostc.example.org. + This example configures failover support with three hosts, + all with unique IP addresses, but providing + the same web content. It has two different masters named + hosta.example.org and + hostb.example.org, with a shared backup + named hostc.example.org. These machines are load balanced with a Round Robin - DNS configuration. The master and backup - machines are configured identically except for their hostnames - and management IP addresses. These servers - must have the same configuration and run the same services. - When the failover occurs, requests to the service on the - shared IP address can only be answered - correctly if the backup server has access to the same content. - The backup machine has two additional CARP - interfaces, one for each of the master content server's - IP addresses. When a failure occurs, the - backup server will pick up the failed master machine's - IP address. + DNS configuration. The master and backup + machines are configured identically except for their hostnames + and management IP addresses. These servers + must have the same configuration and run the same services. + When the failover occurs, requests to the service on the shared + IP address can only be answered correctly if + the backup server has access to the same content. The backup + machine has two additional CARP interfaces, + one for each of the master content server's + IP addresses. When a failure occurs, the + backup server will pick up the failed master machine's + IP address. Using <acronym>CARP</acronym> on &os; 10 and Later - Enable boot-time support for CARP by adding an entry for the - carp.ko kernel module in - /boot/loader.conf: + Enable boot-time support for CARP by + adding an entry for the carp.ko kernel + module in /boot/loader.conf: carp_load="YES" - + To load the module now without rebooting: - + &prompt.root; kldload carp For users who prefer to use a custom kernel, include the following line in the custom kernel configuration file and - compile the kernel as described in - : + compile the kernel as described in : device carp - The hostname, management IP address and subnet mask, - shared IP address, and VHID are all set by - adding entries to /etc/rc.conf. This - example is for + The hostname, management IP address and + subnet mask, shared IP address, and + VHID are all set by adding entries to + /etc/rc.conf. This example is for hosta.example.org: hostname="hosta.example.org" @@ -4982,12 +4982,11 @@ ifconfig_em0_ The next set of entries are for hostb.example.org. Since it represents a second master, it uses a different shared - IP address and - VHID. However, the passwords specified with - must be identical as - CARP will only listen to and accept - advertisements from machines with the correct - password. + IP address and VHID. + However, the passwords specified with + must be identical as CARP will only listen + to and accept advertisements from machines with the correct + password. hostname="hostb.example.org" ifconfig_em0="inet 192.168.1.4 netmask 255.255.255.0" @@ -4995,15 +4994,15 @@ ifconfig_em0_ The third machine, hostc.example.org, is configured to - handle failover from either master. This - machine is configured with two CARP + handle failover from either master. This machine is + configured with two CARP VHIDs, one to handle the virtual IP address for each of the master hosts. - The CARP - advertising skew, , is set to ensure that the backup host - advertises later than the master, since - controls the order of precedence when there are multiple - backup servers. + The CARP advertising skew, + , is set to ensure that the backup + host advertises later than the master, since + controls the order of precedence when + there are multiple backup servers. hostname="hostc.example.org" ifconfig_em0="inet 192.168.1.5 netmask 255.255.255.0" @@ -5030,8 +5029,8 @@ ifconfig_em0_ &prompt.root; ifconfig em0 vhid 1 state backup - Once the configuration is complete, either restart networking or reboot - each system. High availability is now + Once the configuration is complete, either restart + networking or reboot each system. High availability is now enabled. CARP functionality can be controlled @@ -5050,31 +5049,31 @@ ifconfig_em0_ CARP device must first be created and referred to in the configuration. - Enable boot-time support for CARP by loading the - if_carp.ko kernel module in + Enable boot-time support for CARP by + loading the if_carp.ko kernel module in /boot/loader.conf: if_carp_load="YES" To load the module now without rebooting: - + &prompt.root; kldload carp For users who prefer to use a custom kernel, include the following line in the custom kernel configuration file and - compile the kernel as described in - : + compile the kernel as described in : device carp - Next, on each host, create a CARP device: + Next, on each host, create a CARP + device: &prompt.root; ifconfig carp0 create - Set the hostname, management - IP address, the shared - IP address, and VHID - by adding the required lines to + Set the hostname, management IP + address, the shared IP address, and + VHID by adding the required lines to /etc/rc.conf. Since a virtual CARP device is used instead of an alias, the actual subnet mask of /24 is used @@ -5104,8 +5103,8 @@ ifconfig_carp0="vhid 1 - Preemption is disabled in the GENERIC &os; kernel. - If Preemption has been enabled with a custom kernel, + Preemption is disabled in the GENERIC &os; kernel. If + Preemption has been enabled with a custom kernel, hostc.example.org may not release the IP address back to the original content server. The administrator can force the backup @@ -5118,10 +5117,9 @@ ifconfig_carp1="vhid 2 - Once the configuration is complete, either restart networking or reboot - each system. High availability is now + Once the configuration is complete, either restart + networking or reboot each system. High availability is now enabled. -