From owner-svn-doc-head@FreeBSD.ORG Mon Jan 28 15:05:37 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 24DF48B4; Mon, 28 Jan 2013 15:05:37 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 10DF91C8; Mon, 28 Jan 2013 15:05:37 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0SF5agC010616; Mon, 28 Jan 2013 15:05:36 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0SF5aMM010613; Mon, 28 Jan 2013 15:05:36 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301281505.r0SF5aMM010613@svn.freebsd.org> From: Dru Lavigne Date: Mon, 28 Jan 2013 15:05:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40778 - head/en_US.ISO8859-1/books/handbook/ppp-and-slip X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 15:05:37 -0000 Author: dru Date: Mon Jan 28 15:05:36 2013 New Revision: 40778 URL: http://svnweb.freebsd.org/changeset/doc/40778 Log: Commit white fix space only patch to correct repo this time. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Jan 28 15:00:58 2013 (r40777) +++ head/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Mon Jan 28 15:05:36 2013 (r40778) @@ -21,6 +21,7 @@ Synopsis + PPP @@ -29,10 +30,10 @@ FreeBSD has a number of ways to link one computer to - another. To establish a network or Internet connection through a - dial-up modem, or to allow others to do so through you, requires - the use of PPP or SLIP. This chapter describes setting up - these modem-based communication services in detail. + another. To establish a network or Internet connection through + a dial-up modem, or to allow others to do so through you, + requires the use of PPP or SLIP. This chapter describes setting + up these modem-based communication services in detail. After reading this chapter, you will know: @@ -50,7 +51,7 @@ How to set up PPPoA (PPP over ATM). - + How to configure and set up a SLIP client and server (&os; 7.X only). @@ -82,21 +83,23 @@ - You may be wondering what the main difference is between user - PPP and kernel PPP. The answer is simple: user PPP processes the - inbound and outbound data in userland rather than in the kernel. - This is expensive in terms of copying the data between the kernel - and userland, but allows a far more feature-rich PPP implementation. - User PPP uses the tun device to communicate - with the outside world whereas kernel PPP uses the + You may be wondering what the main difference is between + user PPP and kernel PPP. The answer is simple: user PPP + processes the inbound and outbound data in userland rather than + in the kernel. This is expensive in terms of copying the data + between the kernel and userland, but allows a far more + feature-rich PPP implementation. User PPP uses the + tun device to communicate with the + outside world whereas kernel PPP uses the ppp device. Throughout in this chapter, user PPP will simply be - referred to as ppp unless a distinction - needs to be made between it and any other PPP software such as - pppd (&os; 7.X only). Unless otherwise stated, all of - the commands explained in this chapter should be executed as + referred to as ppp unless a + distinction needs to be made between it and any other PPP + software such as pppd + (&os; 7.X only). Unless otherwise stated, all of the + commands explained in this chapter should be executed as root. @@ -104,33 +107,33 @@ - - Tom - Rhodes - Updated and enhanced by - + + Tom + Rhodes + Updated and enhanced by + - - Brian - Somers + + Brian + Somers Originally contributed by - + Nik Clayton With input from - - + + Dirk - Frömberg - - - Peter - Childs - + Frömberg + + + Peter + Childs + @@ -164,14 +167,14 @@ PPP - An account with an Internet Service Provider (ISP) which - you connect to using PPP. + An account with an Internet Service Provider (ISP) + which you connect to using PPP. A modem or - other device connected to your system and properly configured - to allow you to connect to your ISP. + other device connected to your system and properly + configured to allow you to connect to your ISP. @@ -194,9 +197,9 @@ password - Your login name and password. (Either a - regular &unix; style login and password pair, or a PAP or CHAP - login and password pair). + Your login name and password. (Either a + regular &unix; style login and password pair, or a PAP + or CHAP login and password pair). @@ -205,26 +208,27 @@ The IP address of one or more name servers. - Normally, you will be given two IP addresses by your ISP to - use for this. If they have not given you at least one, then - you can use the enable dns command in - ppp.conf and - ppp will set the name servers for - you. This feature depends on your ISPs PPP implementation - supporting DNS negotiation. + Normally, you will be given two IP addresses by your + ISP to use for this. If they have not given you at + least one, then you can use the enable + dns command in ppp.conf + and ppp will set the name + servers for you. This feature depends on your ISPs + PPP implementation supporting DNS negotiation. - The following information may be supplied by your ISP, but - is not completely necessary: + The following information may be supplied by your ISP, + but is not completely necessary: - The IP address of your ISP's gateway. The gateway is - the machine to which you will connect and will be set up as - your default route. If you do not have - this information, we can make one up and your ISP's PPP - server will tell us the correct value when we connect. + The IP address of your ISP's gateway. The gateway + is the machine to which you will connect and will be + set up as your default route. If + you do not have this information, we can make one up + and your ISP's PPP server will tell us the correct value + when we connect. This IP number is referred to as HISADDR by @@ -234,7 +238,7 @@ The netmask you should use. If your ISP has not provided you with one, you can safely use 255.255.255.255. + role="netmask">255.255.255.255. @@ -242,28 +246,30 @@ static IP address - If your ISP provides you with a static IP address and - hostname, you can enter it. Otherwise, we simply let the - peer assign whatever IP address it sees fit. + If your ISP provides you with a static IP address + and hostname, you can enter it. Otherwise, we simply + let the peer assign whatever IP address it sees + fit. - If you do not have any of the required information, contact - your ISP. + If you do not have any of the required information, + contact your ISP. Throughout this section, many of the examples showing the contents of configuration files are numbered by line. These numbers serve to aid in the presentation and - discussion only and are not meant to be placed in the actual - file. Proper indentation with tab and space characters is - also important. + discussion only and are not meant to be placed in the + actual file. Proper indentation with tab and space + characters is also important. - Automatic <application>PPP</application> Configuration + Automatic <application>PPP</application> + Configuration PPP @@ -271,17 +277,19 @@ Both ppp and pppd - (the kernel level implementation of PPP, &os; 7.X only) use the configuration - files located in the /etc/ppp directory. - Examples for user ppp can be found in - /usr/share/examples/ppp/. - - Configuring ppp requires that you edit a - number of files, depending on your requirements. What you put - in them depends to some extent on whether your ISP allocates IP - addresses statically (i.e., you get given one IP address, and - always use that one) or dynamically (i.e., your IP address - changes each time you connect to your ISP). + (the kernel level implementation of PPP, &os; 7.X only) + use the configuration files located in the /etc/ppp directory. + Examples for user ppp can be found in /usr/share/examples/ppp/. + + Configuring ppp requires that you + edit a number of files, depending on your requirements. + What you put in them depends to some extent on whether your + ISP allocates IP addresses statically (i.e., you get given + one IP address, and always use that one) or dynamically + (i.e., your IP address changes each time you connect to + your ISP). PPP and Static IP Addresses @@ -292,14 +300,14 @@ You will need to edit the - /etc/ppp/ppp.conf configuration file. It - should look similar to the example below. + /etc/ppp/ppp.conf configuration file. + It should look similar to the example below. Lines that end in a : start in - the first column (beginning of the line)— all other - lines should be indented as shown using spaces or - tabs. + the first column (beginning of the line)— all + other lines should be indented as shown using spaces + or tabs. 1 default: @@ -327,7 +335,8 @@ Identifies the default entry. Commands in this - entry are executed automatically when ppp is run. + entry are executed automatically when ppp is + run. @@ -335,13 +344,14 @@ Line 2: - Enables logging parameters. When the configuration - is working satisfactorily, this line should be reduced - to saying: + Enables logging parameters. When the + configuration is working satisfactorily, this line + should be reduced to saying: - set log phase tun + set log phase tun - in order to avoid excessive log file sizes. + in order to avoid excessive log file + sizes. @@ -350,10 +360,11 @@ Tells PPP how to identify itself to the peer. - PPP identifies itself to the peer if it has any trouble - negotiating and setting up the link, providing information - that the peers administrator may find useful when - investigating such problems. + PPP identifies itself to the peer if it has any + trouble negotiating and setting up the link, + providing information that the peers administrator + may find useful when investigating such + problems. @@ -366,7 +377,8 @@ /dev/cuau0 and COM2 is - /dev/cuau1. + /dev/cuau1. @@ -374,9 +386,9 @@ Line 5: - Sets the speed you want to connect at. If 115200 - does not work (it should with any reasonably new modem), - try 38400 instead. + Sets the speed you want to connect at. If + 115200 does not work (it should with any reasonably + new modem), try 38400 instead. @@ -390,14 +402,15 @@ The dial string. User PPP uses an expect-send - syntax similar to the &man.chat.8; program. Refer to - the manual page for information on the features of this - language. - - Note that this command continues onto the next line - for readability. Any command in - ppp.conf may do this if the last - character on the line is a \ character. + syntax similar to the &man.chat.8; program. Refer + to the manual page for information on the features + of this language. + + Note that this command continues onto the next + line for readability. Any command in + ppp.conf may do this if the + last character on the line is a \ + character. @@ -406,7 +419,8 @@ Sets the idle timeout for the link. 180 seconds - is the default, so this line is purely cosmetic. + is the default, so this line is purely + cosmetic. @@ -415,8 +429,8 @@ Tells PPP to ask the peer to confirm the local - resolver settings. If you run a local name server, this - line should be commented out or removed. + resolver settings. If you run a local name server, + this line should be commented out or removed. @@ -424,8 +438,8 @@ Line 10: - A blank line for readability. Blank lines are ignored - by PPP. + A blank line for readability. Blank lines are + ignored by PPP. @@ -435,9 +449,10 @@ Identifies an entry for a provider called provider. This could be changed - to the name of your ISP so - that later you can use the - to start the connection. + to the name of your ISP so + that later you can use the to start + the connection. @@ -445,21 +460,22 @@ Line 12: - Sets the phone number for this provider. Multiple - phone numbers may be specified using the colon - (:) or pipe character - (|) as a separator. The difference - between the two separators is described in &man.ppp.8;. - To summarize, if you want to rotate through the numbers, - use a colon. If you want to always attempt to dial the - first number first and only use the other numbers if the - first number fails, use the pipe character. Always - quote the entire set of phone numbers as shown. - - You must enclose the phone number in quotation marks - (") if there is any intention on using - spaces in the phone number. This can cause a simple, yet - subtle error. + Sets the phone number for this provider. + Multiple phone numbers may be specified using the + colon (:) or pipe character + (|) as a separator. The + difference between the two separators is described + in &man.ppp.8;. To summarize, if you want to rotate + through the numbers, use a colon. If you want to + always attempt to dial the first number first and + only use the other numbers if the first number + fails, use the pipe character. Always quote the + entire set of phone numbers as shown. + + You must enclose the phone number in quotation + marks (") if there is any + intention on using spaces in the phone number. + This can cause a simple, yet subtle error. @@ -468,11 +484,11 @@ Identifies the user name and password. When - connecting using a &unix; style login prompt, these - values are referred to by the set - login command using the \U and \P - variables. When connecting using PAP or CHAP, these - values are used at authentication time. + connecting using a &unix; style login prompt, these + values are referred to by the set + login command using the \U and \P + variables. When connecting using PAP or CHAP, these + values are used at authentication time. @@ -482,14 +498,16 @@ PAP CHAP - If you are using PAP or CHAP, there will be no login - at this point, and this line should be commented out or - removed. See PAP and CHAP - authentication for further details. - - The login string is of the same chat-like syntax as - the dial string. In this example, the string works for - a service whose login session looks like this: + If you are using PAP or CHAP, there will be no + login at this point, and this line should be + commented out or removed. See PAP and CHAP + authentication for further details. + + The login string is of the same chat-like + syntax as the dial string. In this example, the + string works for a service whose login session looks + like this: J. Random Provider login: foo @@ -510,11 +528,12 @@ protocol: ppp timeout - Sets the default idle timeout (in seconds) for the - connection. Here, the connection will be closed - automatically after 300 seconds of inactivity. If you - never want to timeout, set this value to zero or use - the command line switch. + Sets the default idle timeout (in seconds) for + the connection. Here, the connection will be closed + automatically after 300 seconds of inactivity. If + you never want to timeout, set this value to zero + or use the command line + switch. @@ -549,29 +568,31 @@ protocol: ppp Adds a default route to your ISP's gateway. The - special word HISADDR is replaced with - the gateway address specified on line 17. It is - important that this line appears after line 17, - otherwise HISADDR will not yet be - initialized. - - If you do not wish to run ppp in , - this line should be moved to the - ppp.linkup file. + special word HISADDR is replaced + with the gateway address specified on line 17. It + is important that this line appears after line 17, + otherwise HISADDR will not yet + be initialized. + + If you do not wish to run ppp in + , this line should be moved + to the ppp.linkup file. It is not necessary to add an entry to - ppp.linkup when you have a static IP - address and are running ppp in mode as your - routing table entries are already correct before you connect. - You may however wish to create an entry to invoke programs after - connection. This is explained later with the sendmail - example. + ppp.linkup when you have a static + IP address and are running ppp in + mode as your routing table entries are already correct + before you connect. You may however wish to create an + entry to invoke programs after connection. This is + explained later with the sendmail example. Example configuration files can be found in the - /usr/share/examples/ppp/ directory. + /usr/share/examples/ppp/ + directory. @@ -607,31 +628,33 @@ protocol: ppp Line 17: - The number after the / character - is the number of bits of the address that ppp will - insist on. You may wish to use IP numbers more - appropriate to your circumstances, but the above example - will always work. - - The last argument (0.0.0.0) tells - PPP to start negotiations using address 0.0.0.0 rather than 10.0.0.1 and is necessary for some - ISPs. Do not use 0.0.0.0 as the first - argument to set ifaddr as it prevents - PPP from setting up an initial route in - mode. + The number after the / + character is the number of bits of the address that + ppp will insist on. You may wish to use IP numbers + more appropriate to your circumstances, but the + above example will always work. + + The last argument (0.0.0.0) + tells PPP to start negotiations using address + 0.0.0.0 rather than + 10.0.0.1 and is + necessary for some ISPs. Do not use + 0.0.0.0 as the first argument + to set ifaddr as it prevents + PPP from setting up an initial route in + mode. - If you are not running in mode, you - will need to create an entry in - /etc/ppp/ppp.linkup. - ppp.linkup is used after a connection has - been established. At this point, ppp will - have assigned the interface addresses and it will now be - possible to add the routing table entries: + If you are not running in mode, + you will need to create an entry in + /etc/ppp/ppp.linkup. + ppp.linkup is used after a connection + has been established. At this point, + ppp will have assigned the interface + addresses and it will now be possible to add the routing + table entries: 1 provider: 2 add default HISADDR @@ -683,82 +706,82 @@ protocol: ppp When you configure ppp to - receive incoming calls on a machine connected to a LAN, you - must decide if you wish to forward packets to the LAN. If you - do, you should allocate the peer an IP number from your LAN's - subnet, and use the command enable proxy in - your /etc/ppp/ppp.conf file. You should - also confirm that the /etc/rc.conf file - contains the following: + receive incoming calls on a machine connected to a LAN, + you must decide if you wish to forward packets to the LAN. + If you do, you should allocate the peer an IP number from + your LAN's subnet, and use the command enable + proxy in your + /etc/ppp/ppp.conf file. You should + also confirm that the /etc/rc.conf + file contains the following: gateway_enable="YES" - - Which getty? + + Which getty? - Configuring FreeBSD for Dial-up - Services provides a good description on enabling - dial-up services using &man.getty.8;. - - An alternative to getty is mgetty (from - comms/mgetty+sendfax - port), - a smarter version of getty designed - with dial-up lines in mind. - - The advantages of using mgetty is - that it actively talks to modems, - meaning if port is turned off in - /etc/ttys then your modem will not answer - the phone. - - Later versions of mgetty (from - 0.99beta onwards) also support the automatic detection of - PPP streams, allowing your clients script-less access to - your server. + Configuring FreeBSD for + Dial-up Services provides a good description + on enabling dial-up services using &man.getty.8;. + + An alternative to getty is mgetty (from + comms/mgetty+sendfax + port), a smarter version of getty + designed with dial-up lines in mind. + + The advantages of using mgetty is + that it actively talks to modems, + meaning if port is turned off in + /etc/ttys then your modem will not + answer the phone. + + Later versions of mgetty (from + 0.99beta onwards) also support the automatic detection of + PPP streams, allowing your clients script-less access to + your server. - Refer to Mgetty and + Refer to Mgetty and AutoPPP for more information on - mgetty. - + mgetty. + - - <application>PPP</application> Permissions + + <application>PPP</application> Permissions - The ppp command must normally be - run as the root user. If however, - you wish to allow ppp to run in - server mode as a normal user by executing - ppp as described below, that user - must be given permission to run ppp - by adding them to the network group - in /etc/group. - - You will also need to give them access to one or more - sections of the configuration file using the - allow command: - - allow users fred mary - - If this command is used in the default - section, it gives the specified users access to - everything. - + The ppp command must normally be + run as the root user. If however, + you wish to allow ppp to run in + server mode as a normal user by executing + ppp as described below, that user + must be given permission to run ppp + by adding them to the network + group in /etc/group. + + You will also need to give them access to one or more + sections of the configuration file using the + allow command: + + allow users fred mary + + If this command is used in the + default section, it gives the specified + users access to everything. + - - PPP Shells for Dynamic-IP Users + + PPP Shells for Dynamic-IP Users - - PPP shells - + + PPP shells + - Create a file called - /etc/ppp/ppp-shell containing the - following: + Create a file called + /etc/ppp/ppp-shell containing the + following: - #!/bin/sh + #!/bin/sh IDENT=`echo $0 | sed -e 's/^.*-\(.*\)$/\1/'` CALLEDAS="$IDENT" TTY=`tty` @@ -772,30 +795,31 @@ echo "Starting PPP for $IDENT" exec /usr/sbin/ppp -direct $IDENT - This script should be executable. Now make a symbolic - link called ppp-dialup to this script - using the following commands: - - &prompt.root; ln -s ppp-shell /etc/ppp/ppp-dialup - - You should use this script as the - shell for all of your dialup users. - This is an example from /etc/passwd - for a dialup PPP user with username - pchilds (remember do not directly edit - the password file, use &man.vipw.8;). + This script should be executable. Now make a + symbolic link called ppp-dialup to + this script using the following commands: + + &prompt.root; ln -s ppp-shell /etc/ppp/ppp-dialup + + You should use this script as the + shell for all of your dialup users. + This is an example from /etc/passwd + for a dialup PPP user with username + pchilds (remember do not directly + edit the password file, use &man.vipw.8;). pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup - Create a /home/ppp directory that + Create a /home/ppp directory that is world readable containing the following 0 byte files: -r--r--r-- 1 root wheel 0 May 27 02:23 .hushlogin -r--r--r-- 1 root wheel 0 May 27 02:22 .rhosts - which prevents /etc/motd from being - displayed. + which prevents /etc/motd from + being displayed. @@ -805,31 +829,32 @@ exec /usr/sbin/ppp -direct $IDENTPPP shells - Create the ppp-shell file as above, - and for each account with statically assigned IPs create a - symbolic link to ppp-shell. + Create the ppp-shell file as + above, and for each account with statically assigned + IPs create a symbolic link to + ppp-shell. For example, if you have three dialup customers, - fred, sam, and - mary, that you route /24 CIDR networks - for, you would type the following: + fred, sam, + and mary, that you route /24 CIDR + networks for, you would type the following: &prompt.root; ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-fred &prompt.root; ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-sam &prompt.root; ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-mary - Each of these users dialup accounts should have their - shell set to the symbolic link created above (for example, - mary's shell should be + Each of these users dialup accounts should have + their shell set to the symbolic link created above (for + example, mary's shell should be /etc/ppp/ppp-mary). - Setting Up <filename>ppp.conf</filename> for Dynamic-IP - Users + Setting Up <filename>ppp.conf</filename> for + Dynamic-IP Users - The /etc/ppp/ppp.conf file should - contain something along the lines of: + The /etc/ppp/ppp.conf file + should contain something along the lines of: default: set debug phase lcp chat @@ -847,17 +872,17 @@ ttyu1: The indenting is important. - The default: section is loaded for - each session. For each dialup line enabled in - /etc/ttys create an entry similar to - the one for ttyu0: above. Each line - should get a unique IP address from your pool of IP - addresses for dynamic users. + The default: section is loaded + for each session. For each dialup line enabled in + /etc/ttys create an entry similar + to the one for ttyu0: above. Each + line should get a unique IP address from your pool of + IP addresses for dynamic users. - Setting Up <filename>ppp.conf</filename> for Static-IP - Users + Setting Up <filename>ppp.conf</filename> for + Static-IP Users Along with the contents of the sample /usr/share/examples/ppp/ppp.conf @@ -891,140 +916,146 @@ mary: add 203.14.103.0 netmask 255.255.255.0 HISADDR - - <command>mgetty</command> and AutoPPP + + <command>mgetty</command> and AutoPPP - - mgetty - + + mgetty + - - AutoPPP - + + AutoPPP + - - LCP - + + LCP + - By default the By default the comms/mgetty+sendfax port - comes - with the AUTO_PPP option enabled - allowing mgetty to detect the LCP phase - of PPP connections and automatically spawn off a ppp - shell. However, since the default login/password - sequence does not occur it is necessary to authenticate - users using either PAP or CHAP. + comes with the AUTO_PPP option enabled + allowing mgetty to detect the LCP + phase of PPP connections and automatically spawn off a + ppp shell. However, since the default login/password + sequence does not occur it is necessary to authenticate + users using either PAP or CHAP. - This section assumes the user has successfully - compiled, and installed the This section assumes the user has successfully + compiled, and installed the comms/mgetty+sendfax port on - his system. + his system. - Make sure your - /usr/local/etc/mgetty+sendfax/login.config - file has the following in it: + Make sure your + /usr/local/etc/mgetty+sendfax/login.config + file has the following in it: - /AutoPPP/ - - /etc/ppp/ppp-pap-dialup + /AutoPPP/ - - /etc/ppp/ppp-pap-dialup - This will tell mgetty to run the - ppp-pap-dialup script for detected - PPP connections. + This will tell mgetty to run the + ppp-pap-dialup script for detected + PPP connections. - Create a file called - /etc/ppp/ppp-pap-dialup containing the - following (the file should be executable): + Create a file called + /etc/ppp/ppp-pap-dialup containing + the following (the file should be executable): - #!/bin/sh + #!/bin/sh exec /usr/sbin/ppp -direct pap$IDENT - For each dialup line enabled in - /etc/ttys, create a corresponding entry - in /etc/ppp/ppp.conf. This will - happily co-exist with the definitions we created - above. + For each dialup line enabled in + /etc/ttys, create a corresponding + entry in /etc/ppp/ppp.conf. This + will happily co-exist with the definitions we created + above. - pap: + pap: enable pap set ifaddr 203.14.100.1 203.14.100.20-203.14.100.40 enable proxy - Each user logging in with this method will need to have *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***