From owner-svn-doc-all@FreeBSD.ORG Wed Feb 12 23:20:57 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 D07C1A6C; Wed, 12 Feb 2014 23:20:57 +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 B9F0B19C8; Wed, 12 Feb 2014 23:20:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s1CNKv6b042859; Wed, 12 Feb 2014 23:20:57 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s1CNKvuF042812; Wed, 12 Feb 2014 23:20:57 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402122320.s1CNKvuF042812@svn.freebsd.org> From: Dru Lavigne Date: Wed, 12 Feb 2014 23:20:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43892 - 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: Wed, 12 Feb 2014 23:20:57 -0000 Author: dru Date: Wed Feb 12 23:20:57 2014 New Revision: 43892 URL: http://svnweb.freebsd.org/changeset/doc/43892 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 Wed Feb 12 22:32:41 2014 (r43891) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Feb 12 23:20:57 2014 (r43892) @@ -86,14 +86,15 @@ - Gateways and Routes - - CoranthGryphonContributed by + + Gateways and Routes + + + CoranthGryphonContributed + by - - routing gateway subnet @@ -151,12 +152,13 @@ host2.example.com link#1 UC Ethernet MAC address - The addresses beginning with 0:e0: are Ethernet hardware addresses, - also known as MAC addresses. &os; will - automatically identify any hosts, test0 in - the example, on the local Ethernet and add a route for that - host over the Ethernet interface, - ed0. This type of route has a + The addresses beginning with 0:e0: are Ethernet + hardware addresses, also known as MAC + addresses. &os; will automatically identify any hosts, + test0 in the example, on the local + Ethernet and add a route for that host over the Ethernet + interface, ed0. This type of route has a timeout, seen in the Expire column, which is used if the host does not respond in a specific amount of time. When this happens, the route to this host will be @@ -168,10 +170,11 @@ host2.example.com link#1 UC subnet &os; will add subnet routes for the local subnet. - 10.20.30.255 is the broadcast - address for the subnet 10.20.30 - and example.com is the - domain name associated with that subnet. The designation + 10.20.30.255 is the + broadcast address for the subnet 10.20.30 and example.com is the domain + name associated with that subnet. The designation link#1 refers to the first Ethernet card in the machine. @@ -189,13 +192,14 @@ host2.example.com link#1 UC The two host2 lines represent aliases which were created using &man.ifconfig.8;. The => symbol after the - lo0 interface says that an alias - has been set in addition to the loopback address. Such routes - only show up on the host that supports the alias; all other - hosts on the local network will have a + lo0 interface says that an alias has been + set in addition to the loopback address. Such routes only + show up on the host that supports the alias; all other hosts + on the local network will have a link#1 line for such routes. - The final line (destination subnet 224) deals with + The final line (destination subnet 224) deals with multicasting. Finally, various attributes of each route can be seen in @@ -332,25 +336,28 @@ host2.example.com link#1 UC A common question is Why is - T1-GW configured as the default gateway for - Local1, rather than the + T1-GW configured as the default + gateway for Local1, rather than the ISP server it is connected to?. Since the PPP interface is using an - address on the ISP's local network for - the local side of the connection, routes for any other - machines on the ISP's local network will - be automatically generated. The system already knows how - to reach the T1-GW machine, so there is no - need for the intermediate step of sending traffic to the + address on the ISP's local network for the + local side of the connection, routes for any other machines on + the ISP's local network will be + automatically generated. The system already knows how to + reach the T1-GW machine, so there is + no need for the intermediate step of sending traffic to the ISP's server. - It is common to use the address X.X.X.1 as the gateway address for - the local network. So, if the local class C address space is - 10.20.30 and the - ISP is using 10.9.9, the default routes would - be: + It is common to use the address X.X.X.1 as the gateway + address for the local network. So, if the local class C + address space is 10.20.30 and the + ISP is using 10.9.9, the default routes + would be: @@ -452,13 +459,15 @@ host2.example.com link#1 UC - Setting Up Static Routes + + Setting Up Static Routes + - AlHoangContributed by + AlHoangContributed + by - Manual Configuration @@ -497,14 +506,18 @@ host2.example.com link#1 UC - In this scenario, RouterA is a &os; - machine that is acting as a router to the rest of the - Internet. It has a default route set to 10.0.0.1 which allows it to - connect with the outside world. RouterB is - already configured properly as it uses 192.168.1.1 as the gateway. + In this scenario, RouterA is a + &os; machine that is acting as a router to the rest of the + Internet. It has a default route set to 10.0.0.1 which allows it to + connect with the outside world. + RouterB is already configured + properly as it uses 192.168.1.1 as the + gateway. - The routing table on RouterA looks - something like this: + The routing table on RouterA + looks something like this: &prompt.user; netstat -nr Routing tables @@ -516,17 +529,20 @@ default 10.0.0.1 UG 10.0.0.0/24 link#1 UC 0 0 xl0 192.168.1.0/24 link#2 UC 0 0 xl1 - With the current routing table, RouterA - cannot reach Internal Net 2 as it does not have a route for - 192.168.2.0/24. The + With the current routing table, + RouterA cannot reach Internal Net + 2 as it does not have a route for 192.168.2.0/24. The following command adds the Internal Net 2 network to - RouterA's routing table using 192.168.1.2 as the next - hop: + RouterA's routing table using + 192.168.1.2 as + the next hop: &prompt.root; route add -net 192.168.2.0/24 192.168.1.2 - Now RouterA can reach any hosts on the - 192.168.2.0/24 + Now RouterA can reach any hosts + on the 192.168.2.0/24 network. @@ -558,8 +574,9 @@ route_internalnet2="-net 192.168.2.0/24 Using more than one string in static_routes creates multiple static routes. The following shows an example of adding static - routes for the 192.168.0.0/24 - and 192.168.1.0/24 + routes for the 192.168.0.0/24 and + 192.168.1.0/24 networks: static_routes="net1 net2" @@ -644,13 +661,16 @@ route_net2="-net 192.168.1.0/24 192.168. which has largely been replaced by &man.pim.4; in many multicast installations. &man.mrouted.8; and the related &man.map-mbone.8; and &man.mrinfo.8; utilities are available - in the &os; Ports Collection as net/mrouted. + in the &os; Ports Collection as + net/mrouted. - Wireless Networking + + Wireless Networking + Loader @@ -659,7 +679,6 @@ route_net2="-net 192.168.1.0/24 192.168. MurrayStokely - wireless networking @@ -800,11 +819,13 @@ route_net2="-net 192.168.1.0/24 192.168. changed according to the configuration. A list of available wireless drivers and supported adapters can be found in the &os; Hardware Notes, available on - the Release + the Release Information page of the &os; website. If a native &os; driver for the wireless device does not exist, it may be possible to use the &windows; driver - with the help of the NDIS driver + with the help of the NDIS driver wrapper. @@ -980,7 +1001,8 @@ freebsdap 00:11:95:c3:0d:ac 1 This section provides a simple example of how to make the wireless network adapter work in &os; without encryption. Once familiar with these concepts, it is - strongly recommend to use WPA to set up + strongly recommend to use WPA to set up the wireless network. There are three basic steps to configure a wireless @@ -1057,7 +1079,8 @@ ifconfig_wlan0="mode 11gWPA-PSK, also known as WPA Personal, which is - described in . + described in . If using an &apple; &airport; Extreme base @@ -1079,7 +1102,8 @@ ifconfig_wlan0="authmode shared wepmode with legacy devices, it is better to use WEP with open authentication. More information regarding - WEP can be found in . + WEP can be found in . @@ -1339,17 +1363,19 @@ wlan0: flags=8843<UP,BROADCAST,RUNNIN (EAP-TLS) is a well-supported wireless authentication protocol since it was the first EAP method to be certified - by the Wi-Fi alliance. - EAP-TLS requires three certificates - to run: the certificate of the Certificate Authority - (CA) installed on all machines, the - server certificate for the authentication server, and - one client certificate for each wireless client. In - this EAP method, both the - authentication server and wireless client authenticate - each other by presenting their respective certificates, - and then verify that these certificates were signed by - the organization's CA. + by the Wi-Fi + alliance. EAP-TLS requires + three certificates to run: the certificate of the + Certificate Authority (CA) installed + on all machines, the server certificate for the + authentication server, and one client certificate for + each wireless client. In this EAP + method, both the authentication server and wireless + client authenticate each other by presenting their + respective certificates, and then verify that these + certificates were signed by the organization's + CA. As previously, the configuration is done via /etc/wpa_supplicant.conf: @@ -1742,8 +1768,8 @@ Associated with 00:13:46:49:41:76IBSS mode, also called ad-hoc mode, is designed for point to point connections. For example, to establish an ad-hoc network between the machines - A and B, choose two - IP addresses and a + A and B, + choose two IP addresses and a SSID. On A: @@ -1773,8 +1799,8 @@ Associated with 00:13:46:49:41:76The I in the output confirms that A is in ad-hoc mode. Now, configure - B with a different IP - address: + B with a different + IP address: &prompt.root; ifconfig wlan0 inet 192.168.0.2 netmask 255.255.255.0 ssid freebsdap &prompt.root; ifconfig wlan0 @@ -1787,8 +1813,9 @@ Associated with 00:13:46:49:41:76 - Both A and B are now - ready to exchange information. + Both A and + B are now ready to exchange + information. @@ -1807,7 +1834,8 @@ Associated with 00:13:46:49:41:76AP, the kernel must be configured with the appropriate networking support for the wireless card as well as the security protocols being used. For more - details, see . + details, see . The NDIS driver wrapper for @@ -1914,8 +1942,8 @@ freebsdap 00:11:95:c3:0d:ac 1 AP using the WPA security protocol. More details regarding WPA and the configuration of - WPA-based - wireless clients can be found in . + WPA-based wireless clients can be found + in . The &man.hostapd.8; daemon is used to deal with client authentication and key management on the @@ -1931,7 +1959,8 @@ freebsdap 00:11:95:c3:0d:ac 1 hostapd_enable="YES" Before trying to configure &man.hostapd.8;, first - configure the basic settings introduced in . + configure the basic settings introduced in . <acronym>WPA-PSK</acronym> @@ -2042,10 +2071,10 @@ wpa_pairwise=CCMP TKIP for more details. - It is possible to see the stations associated with the - AP using ifconfig - wlan0 list + clients can associate with it. See for more details. It + is possible to see the stations associated with the + AP using ifconfig wlan0 list sta. @@ -2112,7 +2141,8 @@ freebsdap 00:11:95:c3:0d:ac 1 In this example, the client machine found the AP and can associate with it using the - correct parameters. See for more details. + correct parameters. See for more details. @@ -2131,8 +2161,10 @@ freebsdap 00:11:95:c3:0d:ac 1 and the operating system switches automatically when the link state changes. - Link aggregation and failover is covered in and an example for using - both wired and wireless connections is provided at . + Link aggregation and failover is covered in and an example for using + both wired and wireless connections is provided at . @@ -2228,16 +2260,17 @@ freebsdap 00:11:95:c3:0d:ac 1 - Bluetooth + + Bluetooth + - PavLucistnikWritten by + PavLucistnikWritten + by
pav@FreeBSD.org
 - - Bluetooth Introduction @@ -2804,8 +2837,9 @@ Success, response: OK, Success (0x20)In order to provide the OPUSH service, &man.sdpd.8; must be running and a root folder, where all incoming objects will be stored, must be created. The - default path to the root folder is /var/spool/obex. Finally, - start the OBEX server on a valid + default path to the root folder is + /var/spool/obex. Finally, start the + OBEX server on a valid RFCOMM channel number. The OBEX server will automatically register the OPUSH service with the local @@ -2877,12 +2911,14 @@ rfcomm_sppd[94692]: Starting on /dev/tty - Bridging + + Bridging + - AndrewThompsonWritten by + AndrewThompsonWritten + by - Introduction @@ -3206,23 +3242,25 @@ bridge0: flags=8843<UP,BROADCAST,RUNN forwarding table. Clients learned on a particular segment of the bridge can not roam to another segment. - Another example of using sticky addresses is to - combine the bridge with VLANs to create - a router where customer networks are isolated without - wasting IP address space. Consider that - CustomerA is on - vlan100 and CustomerB is on + Another example of using sticky addresses is to combine + the bridge with VLANs to create a router + where customer networks are isolated without wasting + IP address space. Consider that + CustomerA is + on vlan100 and CustomerB is on vlan101. The bridge has the address - 192.168.0.1 and is also an - Internet router. + 192.168.0.1 and + is also an Internet router. &prompt.root; ifconfig bridge0 addm vlan100 sticky vlan100 addm vlan101 sticky vlan101 &prompt.root; ifconfig bridge0 inet 192.168.0.1/24 - In this example, both clients see 192.168.0.1 as their default - gateway. Since the bridge cache is sticky, one host can not - spoof the MAC address of the other - customer in order to intercept their traffic. + In this example, both clients see 192.168.0.1 as their + default gateway. Since the bridge cache is sticky, one host + can not spoof the MAC address of the + other customer in order to intercept their traffic. Any communication between the VLANs can be blocked using a firewall or, as seen in this example, @@ -3231,8 +3269,8 @@ bridge0: flags=8843<UP,BROADCAST,RUNN &prompt.root; ifconfig bridge0 private vlan100 private vlan101 The customers are completely isolated from each other - and the full /24 address - range can be allocated without subnetting. + and the full /24 + address range can be allocated without subnetting. @@ -3245,7 +3283,8 @@ bridge0: flags=8843<UP,BROADCAST,RUNN is removed. The following example sets the maximum number of - Ethernet devices for CustomerA on + Ethernet devices for CustomerA on vlan100 to 10: &prompt.root; ifconfig bridge0 ifmaxaddr vlan100 10 @@ -3272,11 +3311,13 @@ bridge0: flags=8843<UP,BROADCAST,RUNN information. The following examples use the - Net-SNMP software (net-mgmt/net-snmp) to query a - bridge from a client system. The net-mgmt/bsnmptools port can - also be used. From the SNMP client - which is running Net-SNMP, add - the following lines to + Net-SNMP software + (net-mgmt/net-snmp) to query a bridge + from a client system. The + net-mgmt/bsnmptools port can also be + used. From the SNMP client which is + running Net-SNMP, add the + following lines to $HOME/.snmp/snmp.conf in order to import the bridge MIB definitions: @@ -3340,12 +3381,14 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault - Link Aggregation and Failover + + Link Aggregation and Failover + - AndrewThompsonWritten by + AndrewThompsonWritten + by - lagg failover @@ -3685,15 +3728,18 @@ ifconfig_lagg0="laggp - Diskless Operation + + Diskless Operation + - Jean-FrançoisDockèsUpdated by + Jean-FrançoisDockèsUpdated + by - AlexDupreReorganized and enhanced by + AlexDupreReorganized + and enhanced by - diskless workstation diskless operation @@ -3717,8 +3763,9 @@ ifconfig_lagg0="laggp file system on the server. The script will probably require a little customization. - Standard system startup files exist in /etc to detect and support a - diskless system startup. + Standard system startup files exist in + /etc to detect and support a diskless + system startup. Swapping, if needed, can be done either to an NFS file or to a local disk. @@ -3736,10 +3783,10 @@ ifconfig_lagg0="laggp / and /usr. - The root file system is a copy of a standard &os; - root, with some configuration files overridden by ones - specific to diskless operation or, possibly, to the - workstation they belong to. + The root file system is a copy of a standard &os; root, + with some configuration files overridden by ones specific to + diskless operation or, possibly, to the workstation they + belong to. The parts of the root which have to be writable are overlaid with &man.md.4; file systems. Any changes will be @@ -3855,8 +3902,9 @@ ifconfig_lagg0="laggp answer both BOOTP and DHCP requests. - ISC DHCP is not part of - the base system. Install the net/isc-dhcp42-server port or + ISC DHCP is not part of the + base system. Install the + net/isc-dhcp42-server port or package. Once ISC DHCP is installed, @@ -3980,7 +4028,8 @@ subnet 192.168.4.0 netmask 255.255.255.0 Create a directory from which &man.tftpd.8; will - serve the files, such as /tftpboot. + serve the files, such as + /tftpboot. @@ -4152,7 +4201,8 @@ cd /usr/src/etc; make distributionMiscellaneous Issues - Running with a Read-only <filename>/usr</filename> + Running with a Read-only + <filename>/usr</filename> diskless operation @@ -4162,7 +4212,8 @@ cd /usr/src/etc; make distributionIf the diskless workstation is configured to run &xorg;, adjust the XDM configuration file as it - puts the error log on /usr by default. + puts the error log on /usr by + default. @@ -4174,27 +4225,28 @@ cd /usr/src/etc; make distribution In this situation, there are sometimes problems with - the special files in /dev, due to differing - major/minor integer sizes. A solution to this problem - is to export a directory from the non-&os; server, mount - this directory onto a &os; machine, and use &man.devfs.5; - to allocate device nodes transparently for the - user. + the special files in /dev, due to + differing major/minor integer sizes. A solution to this + problem is to export a directory from the non-&os; server, + mount this directory onto a &os; machine, and use + &man.devfs.5; to allocate device nodes transparently for + the user. - PXE Booting with an <acronym>NFS</acronym> Root File + <info> + <title>PXE Booting with an <acronym>NFS</acronym> Root File System + CraigRodrigues
rodrigc@FreeBSD.org
Written by - The &intel; Preboot eXecution Environment (PXE) allows booting the operating system @@ -4211,7 +4263,8 @@ cd /usr/src/etc; make distributionTFTP. After the host computer receives this information, it downloads the boot loader via TFTP and then executes the boot loader. - This is documented in section 2.2.1 of the Preboot + This is documented in section 2.2.1 of the Preboot Execution Environment (PXE) Specification. In &os;, the boot loader retrieved during the PXE process is @@ -4229,8 +4282,9 @@ cd /usr/src/etc; make distribution Choose a directory which will have a &os; installation which will be NFS - mountable. For example, a directory such as /b/tftpboot/FreeBSD/install - can be used. + mountable. For example, a directory such as + /b/tftpboot/FreeBSD/install can be + used. &prompt.root; export NFSROOTDIR=/b/tftpboot/FreeBSD/install &prompt.root; mkdir -p ${NFSROOTDIR} @@ -4238,7 +4292,8 @@ cd /usr/src/etc; make distribution Enable the NFS server by following - the instructions in . + the instructions in . @@ -4274,7 +4329,8 @@ cd /usr/src/etc; make distribution - Rebuild the &os; kernel and userland (): + Rebuild the &os; kernel and userland (): &prompt.root; cd /usr/src &prompt.root; make buildworld @@ -4358,17 +4414,19 @@ myhost.example.com:/b/tftpboot/FreeBSD/i NFS boot and runs /etc/rc.initdiskless. Read the comments in this script to understand what is going on. In this case, - /etc and /var need to be memory backed - file systems so that these directories are writable but the - NFS root directory is read-only: + /etc and /var need + to be memory backed file systems so that these directories are + writable but the NFS root directory is + read-only: &prompt.root; chroot ${NFSROOTDIR} &prompt.root; mkdir -p conf/base &prompt.root; tar -c -v -f conf/base/etc.cpio.gz --format cpio --gzip etc &prompt.root; tar -c -v -f conf/base/var.cpio.gz --format cpio --gzip var - When the system boots, memory file systems for /etc and /var will be created and - mounted and the contents of the + When the system boots, memory file systems for + /etc and /var will + be created and mounted and the contents of the cpio.gz files will be copied into them. @@ -4385,7 +4443,8 @@ myhost.example.com:/b/tftpboot/FreeBSD/i Install the DHCP server by - following the instructions documented at . Make sure that + following the instructions documented at . Make sure that /etc/rc.conf and /usr/local/etc/dhcpd.conf are correctly configured. @@ -4443,7 +4502,8 @@ myhost.example.com:/b/tftpboot/FreeBSD/i Use the net/wireshark package or port to debug the network traffic involved during the PXE booting process, as illustrated - in the diagram below. In , an example + in the diagram below. In , an example configuration is shown where the DHCP, TFTP, and NFS servers are on the same machine. However, these @@ -4456,11 +4516,16 @@ myhost.example.com:/b/tftpboot/FreeBSD/i - - - - - + + + + + @@ -4547,12 +4612,14 @@ Received 264951 bytes in 0.1 seconds - Network Address Translation + + Network Address Translation + - ChernLeeContributed by + ChernLeeContributed + by - Overview @@ -4768,20 +4835,27 @@ redirect_port tcp 192.168.0.3:80 80Each machine and interface behind the LAN should be assigned IP addresses in the private network space, - as defined by RFC + as defined by RFC 1918, and have a default gateway of the &man.natd.8; machine's internal IP address. For example, client A and - B behind the LAN have - IP addresses of 192.168.0.2 and 192.168.0.3, while the &man.natd.8; - machine's LAN interface has an - IP address of 192.168.0.1. The default gateway - of clients A and B must be - set to that of the &man.natd.8; machine, 192.168.0.1. The &man.natd.8; - machine's external Internet interface does not require any - special modification for &man.natd.8; to work. + B behind the LAN + have IP addresses of 192.168.0.2 and 192.168.0.3, while the + &man.natd.8; machine's LAN interface has an + IP address of 192.168.0.1. The default + gateway of clients A and + B must be set to that of the + &man.natd.8; machine, 192.168.0.1. The + &man.natd.8; machine's external Internet interface does not + require any special modification for &man.natd.8; to + work. @@ -4798,10 +4872,10 @@ redirect_port tcp 192.168.0.3:80 80 For example, an IRC server runs on - client A and a web server runs on client - B. For this to work properly, connections - received on ports 6667 (IRC) and 80 - (HTTP) must be redirected to the + client A and a web server runs on + client B. For this to work properly, + connections received on ports 6667 (IRC) + and 80 (HTTP) must be redirected to the respective machines. The syntax for is as @@ -4823,7 +4897,8 @@ redirect_port tcp 192.168.0.3:80 80-redirect_port. For example, tcp 192.168.0.2:2000-3000 2000-3000 would redirect all connections received on ports 2000 to 3000 - to ports 2000 to 3000 on client A. + to ports 2000 to 3000 on client + A. These options can be used when directly running &man.natd.8;, placed within the @@ -4849,12 +4924,17 @@ redirect_port tcp 192.168.0.3:80 80IP address back to the specific LAN client. This is also known as static NAT. For example, - if IP addresses 128.1.1.1, 128.1.1.2, and 128.1.1.3 are available, 128.1.1.1 can be used as the - &man.natd.8; machine's external IP - address, while 128.1.1.2 and - 128.1.1.3 are forwarded back - to LAN clients A and - B. + if IP addresses 128.1.1.1, 128.1.1.2, and 128.1.1.3 are available, + 128.1.1.1 can be + used as the &man.natd.8; machine's external + IP address, while 128.1.1.2 and 128.1.1.3 are forwarded back + to LAN clients A + and B. The syntax is as follows: @@ -4901,25 +4981,29 @@ redirect_port tcp 192.168.0.3:80 80 - <acronym>IPv6</acronym> + + <acronym>IPv6</acronym> + - AaronKaplanOriginally Written by + AaronKaplanOriginally + Written by - TomRhodesRestructured and Added by + TomRhodesRestructured + and Added by - BradDavisExtended by + BradDavisExtended + by - - IPv6, also known as IPng IP next generation, is the new version of the well known IP protocol, also known as - IPv4. &os; includes the KAME + IPv4. &os; includes the KAME IPv6 reference implementation. &os; comes with everything needed to use IPv6. This section focuses on getting IPv6 configured @@ -4933,16 +5017,17 @@ 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 + 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 + out, there will be no more available and switching to IPv6 will be critical. @@ -4978,7 +5063,8 @@ redirect_port tcp 192.168.0.3:80 80 - Address autoconfiguration (RFC2462). + Address autoconfiguration (RFC2462). @@ -5014,7 +5100,8 @@ redirect_port tcp 192.168.0.3:80 80 - KAME.net + KAME.net @@ -5040,8 +5127,9 @@ redirect_port tcp 192.168.0.3:80 80 The IPv4 broadcast address, usually - xxx.xxx.xxx.255, is expressed - by multicast addresses in IPv6. + xxx.xxx.xxx.255, + is expressed by multicast addresses in + IPv6. @@ -5062,7 +5150,8 @@ redirect_port tcp 192.168.0.3:80 80::128 bitsunspecified - Equivalent to 0.0.0.0 in *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***