* Reword advice given in the first person.
* Add missing words to form better sentences. * Suggest that users simply set the router and router_flags variables in /etc/rc.conf, rather than the previous instructions to hack /etc/netstart.
This commit is contained in:
parent
ab1f38fbcb
commit
cc2871ef38
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10613
1 changed files with 21 additions and 19 deletions
|
@ -1,7 +1,7 @@
|
||||||
<!--
|
<!--
|
||||||
The FreeBSD Documentation Project
|
The FreeBSD Documentation Project
|
||||||
|
|
||||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.56 2001/09/04 14:54:05 kuriyama Exp $
|
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.57 2001/09/04 15:14:21 brian Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<chapter id="ppp-and-slip">
|
<chapter id="ppp-and-slip">
|
||||||
|
@ -2001,11 +2001,13 @@ ppp_profile="name_of_service_provider"</programlisting>
|
||||||
do something much fancier.</para>
|
do something much fancier.</para>
|
||||||
|
|
||||||
<para>First, determine which serial port your modem is connected to.
|
<para>First, determine which serial port your modem is connected to.
|
||||||
I have a symbolic link to <filename>/dev/modem</filename> from
|
Many people setup a symbolic link, such as
|
||||||
<filename>/dev/cuaa1</filename>, and only use the modem name in
|
<devicename>/dev/modem</devicename>, to point to the real device name,
|
||||||
my configuration files. It can become quite cumbersome when you
|
<devicename>/dev/cuaaN</devicename>. This allows you to
|
||||||
|
abstract the actual device name should you ever need to move
|
||||||
|
the modem to a different port. It can become quite cumbersome when you
|
||||||
need to fix a bunch of files in <filename>/etc</filename> and
|
need to fix a bunch of files in <filename>/etc</filename> and
|
||||||
<filename>.kermrc</filename>'s all over the system!</para>
|
<filename>.kermrc</filename> files all over the system!</para>
|
||||||
|
|
||||||
<note>
|
<note>
|
||||||
<para><filename>/dev/cuaa0</filename> is
|
<para><filename>/dev/cuaa0</filename> is
|
||||||
|
@ -2204,10 +2206,9 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Not using <option>-c</option> or <option>-a</option> in
|
<para>Not using <option>-c</option> or <option>-a</option> in
|
||||||
<command>slattach</command> (I have no idea why this
|
<command>slattach</command> (This shouldn't be fatal,
|
||||||
can be fatal, but adding
|
but some users have reported that this solves their
|
||||||
this flag solved the problem for at least one
|
problems.)</para>
|
||||||
person).</para>
|
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
@ -2700,7 +2701,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
||||||
<para>Adding static routes to your nearest default routers can
|
<para>Adding static routes to your nearest default routers can
|
||||||
be troublesome (or impossible, if you do not have authority to
|
be troublesome (or impossible, if you do not have authority to
|
||||||
do so...). If you have a multiple-router network in your
|
do so...). If you have a multiple-router network in your
|
||||||
organization, some routers, such as Cisco and Proteon, may
|
organization, some routers, such as those made by Cisco and Proteon, may
|
||||||
not only need to be configured with the static route to the
|
not only need to be configured with the static route to the
|
||||||
SLIP subnet, but also need to be told which static routes to
|
SLIP subnet, but also need to be told which static routes to
|
||||||
tell other routers about, so some expertise and
|
tell other routers about, so some expertise and
|
||||||
|
@ -2788,15 +2789,16 @@ import proto rip interface ed {
|
||||||
net mask in the <literal>proto direct</literal> clause as
|
net mask in the <literal>proto direct</literal> clause as
|
||||||
well).</para>
|
well).</para>
|
||||||
|
|
||||||
<para>When you get <command>gated</command> built and installed
|
<para>Once you have installed and configured
|
||||||
and create a configuration file for it, you will need to run
|
<command>gated</command> on your system, you will need to
|
||||||
<command>gated</command> in place of <command>routed</command>
|
tell the FreeBSD startup scripts to run
|
||||||
on your FreeBSD system; change the
|
<command>gated</command> in place of
|
||||||
<filename>routed/gated</filename> startup parameters in
|
<command>routed</command>. The easiest way to accomplish
|
||||||
<filename>/etc/netstart</filename> as appropriate for your
|
this is to set the <varname>router</varname> and
|
||||||
system. Please see the manual page for
|
<varname>router_flags</varname> variables in
|
||||||
<command>gated</command> for information on
|
<filename>/etc/rc.conf</filename>. Please see the manual
|
||||||
<command>gated</command>'s command-line parameters.</para>
|
page for <command>gated</command> for information on
|
||||||
|
command-line parameters.</para>
|
||||||
</sect4>
|
</sect4>
|
||||||
</sect3>
|
</sect3>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
Loading…
Reference in a new issue