os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add full stops, remove unnecessary words, use more descriptive markup.

Browse source 
This chapter needs a lot of work.

PR:		43260 (partially)
Submitted by:	Martin Heinen <martin@sumuk.de>
This commit is contained in:
Murray Stokely 2002-09-30 14:07:02 +00:00
parent 2a7e369725
commit f38bbeac68
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=14422
1 changed files with 23 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

43
en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml
View file

@ -324,30 +324,30 @@
<screen>&prompt.root; <userinput>ppp</userinput></screen>
<para>We have now started <command>ppp</command></para>
<para>We have now started <command>ppp</command>.</para>
<screen>ppp ON example&gt; <userinput>set device <devicename>/dev/cuaa1</devicename></userinput></screen>
<para>We set our modem device, in this case it is
<devicename>cuaa1</devicename></para>
<devicename>cuaa1</devicename>.</para>
<screen>ppp ON example&gt; <userinput>set speed 115200</userinput></screen>
<para>Set the connection speed, in this case we
are using 115,200 <acronym>kbps</acronym></para>
are using 115,200 <acronym>kbps</acronym>.</para>
<screen>ppp ON example&gt; <userinput>enable dns</userinput></screen>
<para>Tell <command>ppp</command> to configure our
resolver and add the nameserver lines to
<filename>/etc/resolv.conf</filename>. If we <command>ppp</command>
cannot determine our hostname, we can set one manually later
<filename>/etc/resolv.conf</filename>. If <command>ppp</command>
cannot determine our hostname, we can set one manually later.
</para>
<screen>ppp ON example&gt; <userinput>term</userinput></screen>
<para>Switch to "terminal" mode so that we can manually
control the modem</para>
<para>Switch to <quote>terminal</quote> mode so that we can manually
control the modem.</para>
<programlisting>
deflink: Entering terminal mode on <devicename>/dev/cuaa1</devicename>
@ -359,7 +359,7 @@ OK
<para>Use <command>at</command> to initialize the modem,
then use <command>atdt</command> and the number for your
<acronym>ISP</acronym> to begin the dial in process</para>
<acronym>ISP</acronym> to begin the dial in process.</para>
<screen>CONNECT</screen>
@ -371,7 +371,7 @@ OK
<para>Here you are prompted for a username, return the
prompt with the username that was provided by the
<acronym>ISP</acronym></para>
<acronym>ISP</acronym>.</para>
<screen>ISP Pass:<userinput>mypassword</userinput></screen>
@ -404,7 +404,7 @@ OK
<screen>PPP ON example&gt;</screen>
<para>We have made an agreement on an <acronym>IP</acronym>
address and successfully completed our connection</para>
address and successfully completed our connection.</para>
<screen>PPP ON example&gt;<userinput>add default HISADDR</userinput></screen>
@ -412,7 +412,7 @@ OK
before we can talk to the outside world as currently the
only established connection is with the peer. If this
fails due to existing routes you can put a bang character
<emphasis>!</emphasis> in front of the <option>add</option>.
<literal>!</literal> in front of the <option>add</option>.
Alternatively, you can set this before making the actual connection
and it will negotiate a new route accordingly.</para>
@ -701,7 +701,7 @@ nameserver <replaceable>y.y.y.y</replaceable></programlisting>
<para>You must enclose the phone number in quotation marks
(<literal>"</literal>) if there is any intention on using
spaces in the phone number. This can cause a simple, yet
subtle error</para>
subtle error.</para>
</listitem>
</varlistentry>
@ -1559,7 +1559,7 @@ ifconfig_tun0=</programlisting>
<indexterm><primary>PPP</primary><secondary>client</secondary></indexterm>
<indexterm><primary>Cisco</primary></indexterm>
<para>The following <filename>/etc/ppp/options</filename> might be
used to connect to a CISCO terminal server PPP line.</para>
used to connect to a Cisco terminal server PPP line.</para>
<programlisting>crtscts # enable hardware flow control
modem # modem control line
@ -2410,7 +2410,7 @@ tun0: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1500
</listitem>
<listitem>
<para>Set the startup flags of sl0 by adding a
<para>Set the startup flags of <devicename>sl0</devicename> by adding a
line:</para>
<programlisting>ifconfig_sl0="inet ${hostname} slip-gateway netmask 0xffffff00 up"</programlisting>
@ -2566,9 +2566,10 @@ sl0: flags=10&lt;POINTOPOINT&gt;
</listitem>
<listitem>
<para>Also, <command>netstat -r</command> will give the
routing table, in case you get the <quote>no route to
host</quote> messages from ping. An example shown here:</para>
<para>If you get <errorname>no route to host</errorname>
messages from ping, there may be a problem with your
routing table. You can use the <command>netstat -r</command>
command to display the current routes :</para>
<screen>&prompt.root; <userinput>netstat -r</userinput>
Routing tables
@ -2585,8 +2586,10 @@ inr-3.Example.ED water.CS.Example.E UH 1 0 sl0 - -
water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
(root node)</screen>
<para>This is after the link has been up for a while, the numbers
on your system will vary.</para>
<para>The preceding examples are from a relatively busy system.
The numbers on your system will vary depending on
network activity.</para>
</listitem>
</itemizedlist>
</sect3>
@ -2772,7 +2775,7 @@ sl1* 296 &lt;Link&gt; 0 0 0 0
the configuration for <filename>/usr/sbin/sliplogin</filename>
(see &man.sliplogin.8; for the actual manual page for
<command>sliplogin</command>): <filename>slip.hosts</filename>,
which defines the SLIP users &amp; their associated IP
which defines the SLIP users and their associated IP
addresses; <filename>slip.login</filename>, which usually just
configures the SLIP interface; and (optionally)
<filename>slip.logout</filename>, which undoes