From b69352046d45c0a42fe59cf96b82998099e4586b Mon Sep 17 00:00:00 2001 From: Giorgos Keramidas Date: Thu, 14 Feb 2002 23:21:41 +0000 Subject: [PATCH] Expand contractions. --- en_US.ISO8859-1/books/ppp-primer/book.sgml | 114 ++++++++++----------- 1 file changed, 57 insertions(+), 57 deletions(-) diff --git a/en_US.ISO8859-1/books/ppp-primer/book.sgml b/en_US.ISO8859-1/books/ppp-primer/book.sgml index c3c649d88a..f2fabeb04c 100644 --- a/en_US.ISO8859-1/books/ppp-primer/book.sgml +++ b/en_US.ISO8859-1/books/ppp-primer/book.sgml @@ -180,7 +180,7 @@ own LAN if you want. IP addresses are assigned as follows: to the first serial port ('/dev/cuaa0' or 'COM1:' in DOS-terms). -Finally, we'll also assume that your Internet Service Provider (ISP) +Finally, we will also assume that your Internet Service Provider (ISP) automatically provides the IP addresses of both your PPP/FreeBSD side as well as the ISP's side. (i.e.: Dynamic IP Addresses on both ends of the link.) Specific details for configuring the Dial-Out side of @@ -200,7 +200,7 @@ Local Area Network: -The Host Name of the FreeBSD system; in our example it's "Curly", +The Host Name of the FreeBSD system; in our example it is "Curly", @@ -227,7 +227,7 @@ information to prevent trouble in subsequent steps. Verifying the FreeBSD Host Name -It's possible that the FreeBSD host name was specified and saved +It is possible that the FreeBSD host name was specified and saved when the system was initially installed. To verify that it was, enter the following command at a prompt: @@ -243,12 +243,12 @@ ahead to . For example, in our sample network, we would see 'curly.my.domain' as a result of the `hostname` command if the name had been set -correctly during, or after, installation. (At this point, don't worry -too much about the ".my.domain" part, we'll sort this out later. The +correctly during, or after, installation. (At this point, do not worry +too much about the ".my.domain" part, we will sort this out later. The important part is the name up to the first dot.) -If a host name wasn't specified when FreeBSD was installed you'll -probably see 'myname.my.domain` as a response. You'll need to edit +If a host name was not specified when FreeBSD was installed you will +probably see 'myname.my.domain` as a response. You will need to edit /etc/rc.conf to set the name of the machine. @@ -308,7 +308,7 @@ Ultra (8216) network adapters. Other models of network adapters may have different device names in FreeBSD. Check the FAQ for specifics about your network adapter. If -you're not sure of the device name of your adapter, check the FreeBSD +you are not sure of the device name of your adapter, check the FreeBSD FAQ to determine the device name for the card you have and substitute that name (i.e.: 'de0', 'zp0', or similar) in the following steps. @@ -387,7 +387,7 @@ indicators are: ether 01:02:03:04:05:06 -then the Ethernet card hasn't been configured yet. +then the Ethernet card has not been configured yet. If the configuration for the Ethernet interface is correct you can skip forward to . @@ -421,7 +421,7 @@ that controls this is: -You'll need to amend this line to tell FreeBSD that you want to add +You will need to amend this line to tell FreeBSD that you want to add another device, namely the 'ed0' device. Change this line to read: @@ -435,7 +435,7 @@ read: ("lo0") and the Ethernet device ("ed0")! - Reminder: If your Ethernet card isn't named 'ed0', specify + Reminder: If your Ethernet card is not named 'ed0', specify the correct device name here instead. If you performed the installation of FreeBSD over a network @@ -457,7 +457,7 @@ line that says: -You'll need to add another line after that to specify the settings +You will need to add another line after that to specify the settings for your 'ed0' device. If you performed the installation of FreeBSD over a network @@ -465,7 +465,7 @@ connection then there may already be an 'ifconfig_ed0=' line after the loopback definition. If so, verify that it has the correct values. -For our sample configuration we'll insert a line immediately after +For our sample configuration we will insert a line immediately after the loopback device definition that says: @@ -474,7 +474,7 @@ the loopback device definition that says: -When you've finished editing /etc/rc.conf to specify and +When you have finished editing /etc/rc.conf to specify and configure the network interfaces the section should look really close to: @@ -507,10 +507,10 @@ workstation and not as a gateway between LAN nodes and your ISP you should skip forward to . If you intend for the PPP program to service the local FreeBSD box -as well as LAN workstations (as a router) you'll need to enable IP +as well as LAN workstations (as a router) you will need to enable IP forwarding. -To enable IP Packet forwarding you'll need to edit the +To enable IP Packet forwarding you will need to edit the /etc/rc.conf file. This file contains overrides of the defaults in @@ -553,7 +553,7 @@ always has an IP address of 127.0.0.1. Scroll all the way to the bottom of the file (paying attention to -the comments along the way; there's some good information there!) and +the comments along the way; there is some good information there!) and enter (assuming our sample network) the following IP addresses and host names: @@ -568,7 +568,7 @@ System (No changes are needed to the line for the '127.0.0.1 localhost' entry.) -Once you've entered these lines, press the 'Esc' key to invoke the +Once you have entered these lines, press the 'Esc' key to invoke the control menu. Select "leave editor" and be sure to select "save changes" when prompted. @@ -577,7 +577,7 @@ changes" when prompted. Testing the FreeBSD system -Congratulations! Once you've made it to this point, the FreeBSD +Congratulations! Once you have made it to this point, the FreeBSD system is configured as a network-connected Unix system! If you made any changes to the /etc/rc.conf file you should probably re-boot your FreeBSD system. This will accomplish two important @@ -651,8 +651,8 @@ names (loopback and curly) correctly correlate to their IP addresses (127.0.0.1 and 192.168.1.1). This verifies that the /etc/hosts files is correct. -If the IP address for "curly" isn't 192.168.1.1 or the address for -"localhost" isn't 127.0.0.1, return to and review your +If the IP address for "curly" is not 192.168.1.1 or the address for +"localhost" is not 127.0.0.1, return to and review your entries in '/etc/hosts'. If the names and addresses are indicated correctly in the result of @@ -697,7 +697,7 @@ inside the FreeBSD system and automagically connects and disconnects with your ISP as required to make the Internet a seamless element of your network. -In this section we'll address the configuration(s) for both modes +In this section we will address the configuration(s) for both modes with emphasis on configuring your `ppp` environment to operate in "Automatic" mode. @@ -775,12 +775,12 @@ detail. This section will describe only the minimal configuration to get a dial-out connection working. -Below is the /etc/ppp/ppp.conf file that we'll be using to provide a +Below is the /etc/ppp/ppp.conf file that we will be using to provide a dial-out Internet gateway for our example LAN: The full syntax for ppp.conf is described in - &man.ppp.8;. Particularly, note that any line that isn't a label that + &man.ppp.8;. Particularly, note that any line that is not a label that ends with a colon (e.g., default:, interactive:), a command that begins with ! (e.g., !include), or a comment @@ -851,7 +851,7 @@ implicitly added to the configuration lines to each other section. This is a good place to put "global defaults" applicable to all dial-up sessions; especially modem settings and dialing prefixes which -typically don't change based on which destination system you're +typically do not change based on which destination system you are connecting to. Following are the descriptions of each line in the "default" section @@ -895,7 +895,7 @@ features of the PPP program. The current version of `ppp` supports data compression in accordance with draft Internet standards. Unfortunately many ISPs use equipment that does not support this capability. Since most modems try to perform on-the-fly compression -anyway you're probably not losing much performance by disabling this +anyway you are probably not losing much performance by disabling this feature on the FreeBSD side and denying the remote side from forcing it on you. @@ -918,7 +918,7 @@ attempts by the remote end to reports line quality. As most modern dial-up modems have automatic error correction and detection and LQR reporting is not fully implemented in many vendor's -products it's generally a safe bet to include these two lines in the +products it is generally a safe bet to include these two lines in the default configuration. @@ -1010,7 +1010,7 @@ settings used to set up an "interactive" PPP session with a specific remote system. Settings in this section will have the lines included in the "default" section included automatically. -The example cited in this section of the guide presumes that you'll +The example cited in this section of the guide presumes that you will be connecting to a remote system that understands how to authenticate a user without any fancy scripting language. That is, this sample uses the CHAP protocol to set up the connection. @@ -1023,7 +1023,7 @@ configuration should work OK. Windows '95 Dial-Up Networking you need to resort to using the "Dial Up Scripting Tool" from the Microsoft Plus! pack or you have to select "Bring up a terminal windows after dialing" in the Windows '95 -connection options then you'll need to look at the sample PPP +connection options then you will need to look at the sample PPP configuration files and the ppp manpage for examples of "expect / response" scripting to make your ISP connection. The "set login" command is used for this purpose. @@ -1070,14 +1070,14 @@ system. set authkey Your_Password_On_Remote_System -This is the password you'd use to log in to the remote system. +This is the password you would use to log in to the remote system. set phone 1-800-123-4567 -This is the phone number of the remote system. If you're inside a PBX +This is the phone number of the remote system. If you are inside a PBX you can prepend '9, ' to the number here. @@ -1099,7 +1099,7 @@ specific requirements. This tells the PPP program that once the modems are connected it should immediately attempt to negotiate the connection. Some remote -sites do this automatically, some don't. This instructs your side of +sites do this automatically, some do not. This instructs your side of the link to take the initiative and try to set up the connection. @@ -1127,7 +1127,7 @@ the configuration section which defines the "interactive" configuration. As noted earlier, the examples cited in this section of -the guide presume that you'll be connecting to a remote system that +the guide presume that you will be connecting to a remote system that understands how to use the CHAP protocol to set up the connection. Following are descriptions for each line in the "demand" section of @@ -1146,7 +1146,7 @@ system. set authkey Your_Password_On_Remote_System -This is the password you'd use to log in to the remote system. +This is the password you would use to log in to the remote system. @@ -1173,7 +1173,7 @@ may wish to tailor this number to your specific requirements. This tells the PPP program that once the modems are connected it should immediately attempt to negotiate the connection. Some remote -sites do this automatically, some don't. This instructs your side of +sites do this automatically, some do not. This instructs your side of the link to take the initiative and try to set up the connection. @@ -1204,7 +1204,7 @@ between the local and remote systems when the link is established. The 255.255.255.0 string tells the PPP program what Subnet mask to apply to these pseudo-interfaces. -Remember, we've assumed that your ISP provides the IP addresses for +Remember, we have assumed that your ISP provides the IP addresses for both ends of the link! If your ISP assigned you a specific IP address that you should use on your side when configuring your system, enter that IP address here instead of 127.1.1.1. @@ -1213,7 +1213,7 @@ that IP address here instead of 127.1.1. his end you should enter that IP address here instead of 127.2.2.2. -In both cases, it's probably a good idea to leave the '/0' on +In both cases, it is probably a good idea to leave the '/0' on the end of each address. This gives the PPP program the opportunity to change the address(es) of the link if it has to. @@ -1236,7 +1236,7 @@ while idle: -Accept packets that FreeBSD doesn't already know how to forward, +Accept packets that FreeBSD does not already know how to forward, @@ -1332,7 +1332,7 @@ established using this configuration, it must: -It's critical that those configurations in +It is critical that those configurations in '/etc/ppp/ppp.conf' which include the 'set ifaddr' and 'add 0 0' statements (i.e.: those configurations used for Dial-on-Demand configurations) execute the "delete ALL" and "add 0 0 @@ -1428,7 +1428,7 @@ the ISP. Perform the following steps: Create the Windows 95 "hosts" file: -In order to connect to the other TCP/IP systems on the LAN you'll +In order to connect to the other TCP/IP systems on the LAN you will need to create an identical copy of the "hosts" file that you installed on the FreeBSD system in . @@ -1498,7 +1498,7 @@ settings associated with the TCP component. Click the "Specify an IP address" radio button. -(In our example LAN the Windows 95 system is the one we've called "Larry".) +(In our example LAN the Windows 95 system is the one we have called "Larry".) @@ -1602,7 +1602,7 @@ files transparently across the Internet. - That's it! +That is it! @@ -1616,14 +1616,14 @@ similar to Windows 95 with minor exceptions in the user interface. The steps shown here are appropriate for a Windows NT 4.0 Workstation, but the principles are the same for NT 3.5x. You may wish to refer to the "Configuring Windows for Workgroups" section if -you're configuring Windows NT 3.5x, since the user interface is +you are configuring Windows NT 3.5x, since the user interface is the same for NT 3.5 and WfW. Perform the following steps: Create the Windows NT "hosts" file: -In order to connect to the other TCP/IP systems on the LAN you'll +In order to connect to the other TCP/IP systems on the LAN you will need to create an identical copy of the "hosts" file that you installed on the FreeBSD system in Section 3.4 @@ -1662,7 +1662,7 @@ settings: With the "Identification" tab selected, verify the "Computer Name" -and "Workgroup" fields. In this example we'll use "Shemp" for the name +and "Workgroup" fields. In this example we will use "Shemp" for the name and "Stooges" for the workgroup. Click the "Change" button and amend these entries as necessary. @@ -1703,7 +1703,7 @@ interface is shown. text boxes. -In our example LAN the Windows NT system is the one we've called +In our example LAN the Windows NT system is the one we have called "Shemp" @@ -1802,7 +1802,7 @@ files transparently across the Internet. -That's it! +That is it! @@ -1812,7 +1812,7 @@ files transparently across the Internet. Configuring Windows for Workgroups to act as a network client requires that the Microsoft TCP/IP-32 driver diskette has been installed on the workstation. The TCP/IP drivers are not included -with the WfW CD or diskettes; if you need a copy they're available at +with the WfW CD or diskettes; if you need a copy they are available at ftp://ftp.microsoft.com/peropsys/windows/public/tcpip/. Once the TCP/IP drivers have been loaded, perform the following @@ -1820,7 +1820,7 @@ steps: Create the Windows for Workgroups "hosts" file: -In order to connect to the other TCP/IP systems on the LAN you'll +In order to connect to the other TCP/IP systems on the LAN you will need to create an identical copy of the "hosts" file that you installed on the FreeBSD system in Section 3.4. @@ -1879,7 +1879,7 @@ blank. If it is checked, click it to remove the "X". In our example LAN the Windows for Workgroups system is the one -we've called "Moe"; in the "IP Address" field enter "192.168.1.3". +we have called "Moe"; in the "IP Address" field enter "192.168.1.3". @@ -1961,7 +1961,7 @@ necessary to add all of the addresses that your ISP provided. -That's it! +That is it! @@ -1969,7 +1969,7 @@ necessary to add all of the addresses that your ISP provided. Testing the Network - Once you've completed that appropriate tasks above you should have + Once you have completed that appropriate tasks above you should have a functioning PPP gateway to the Internet. @@ -2001,7 +2001,7 @@ art, it is possible to set up a Mini-DNS server on the FreeBSD system that also acts as your gateway to your ISP. Building on the files in /etc/namedb when the FreeBSD -system was installed it's possible to create a name server that is +system was installed it is possible to create a name server that is both authoritative for the example network shown here as well as a front-door to the Internet DNS architecture. @@ -2031,7 +2031,7 @@ Essentially, it tells the Name Server: -What "domain names" it's responsible for, and +What "domain names" it is responsible for, and @@ -2156,7 +2156,7 @@ start with '192.168.1.' and -To add workstation entries to this file you'll need to add two +To add workstation entries to this file you will need to add two lines for each system; one in the top section where the name(s) are mapped into Internet Addresses ("IN A"), and another line that maps the addresses back into names in the $ORIGIN @@ -2197,7 +2197,7 @@ command: -Whenever you modify any of the files in /etc/namedb you'll +Whenever you modify any of the files in /etc/namedb you will need to kick-start the Name Server process to make it pick up the modifications. This is performed with the following system command: @@ -2360,7 +2360,7 @@ until ruleset '0' is defined! If you choose not to use Filtering Rules in the PPP configuration then ALL traffic will be permitted both into and -out of your system while it's connected to your ISP. +out of your system while it is connected to your ISP. If you decide that you want to implement filtering rules, add the above lines to your /etc/ppp/ppp.conf file in either the