Add ~78 index terms.
This commit is contained in:
Murray Stokely
parent
e7a58f7d91
commit
85ea0cccdb
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9719
1 changed files with 85 additions and 23 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.35 2001/05/14 20:43:13 nik Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.36 2001/06/23 06:57:04 dd Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ppp-and-slip">
|
||||
|
|
@ -12,11 +12,16 @@
|
|||
|
||||
<sect1>
|
||||
<title>Synopsis</title>
|
||||
<indexterm><primary>PPP</primary></indexterm>
|
||||
<indexterm><primary>SLIP</primary></indexterm>
|
||||
|
||||
<para>If you are connecting to the Internet via modem, or wish to
|
||||
provide dial-up connections to the Internet for others using FreeBSD,
|
||||
you have the option of using PPP or SLIP.</para>
|
||||
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>user PPP</secondary></indexterm>
|
||||
<indexterm><primary>PPP</primary><secondary>kernel PPP</secondary></indexterm>
|
||||
<indexterm><primary>PPP</primary><secondary>over Ethernet</secondary></indexterm>
|
||||
<para>This chapter covers three varieties of PPP;
|
||||
<emphasis>user</emphasis>, <emphasis>kernel</emphasis>, and
|
||||
<emphasis>PPPoE</emphasis> (PPP over Ethernet). It also covers
|
||||
|
|
@ -55,6 +60,8 @@
|
|||
<para>This document assumes you have the following:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<indexterm><primary>ISP</primary></indexterm>
|
||||
<indexterm><primary>PPP</primary></indexterm>
|
||||
<listitem>
|
||||
<para>An account with an Internet Service Provider (ISP) which
|
||||
you connect to using PPP. Further, you have a modem or
|
||||
|
|
@ -66,12 +73,18 @@
|
|||
<para>The dial-up number(s) of your ISP.</para>
|
||||
</listitem>
|
||||
|
||||
<indexterm><primary>PAP</primary></indexterm>
|
||||
<indexterm><primary>CHAP</primary></indexterm>
|
||||
<indexterm><primary>Unix</primary></indexterm>
|
||||
<indexterm><primary>login name</primary></indexterm>
|
||||
<indexterm><primary>password</primary></indexterm>
|
||||
<listitem>
|
||||
<para>Your login name and password. This can be either a
|
||||
regular UNIX-style login and password pair, or a PAP or CHAP
|
||||
login and password pair.</para>
|
||||
</listitem>
|
||||
|
||||
<indexterm><primary>name server</primary></indexterm>
|
||||
<listitem>
|
||||
<para>The IP address(es) of one or more name servers.
|
||||
Normally, you will be given two IP addresses by your ISP to
|
||||
|
|
@ -105,6 +118,7 @@
|
|||
role="netmask">255.255.255.0</hostid>.</para>
|
||||
</listitem>
|
||||
|
||||
<indexterm><primary>static IP address</primary></indexterm>
|
||||
<listitem>
|
||||
<para>If your ISP provides you with a static IP address and
|
||||
hostname, you can enter it. Otherwise, we simply let the
|
||||
|
|
@ -127,6 +141,7 @@
|
|||
with FreeBSD. However, if you have installed a custom kernel,
|
||||
you must make sure your kernel is configured for ppp.</para>
|
||||
|
||||
<indexterm><primary>kernel</primary><secondary>compilation</secondary></indexterm>
|
||||
<para>To check, go to your kernel compile directory
|
||||
(<filename>/sys/i386/conf</filename> or
|
||||
<filename>/sys/pc98/conf</filename>) and examine your
|
||||
|
|
@ -226,6 +241,9 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500</screen>
|
|||
<sect3>
|
||||
<title>Name Resolution Configuration</title>
|
||||
|
||||
<indexterm><primary>resolver</primary></indexterm>
|
||||
<indexterm><primary>hostname</primary></indexterm>
|
||||
<indexterm><primary>hosts</primary></indexterm>
|
||||
<para>The resolver is the part of the system that turns IP
|
||||
addresses into hostnames and vice versa. It can be configured
|
||||
to look for maps that describe IP to hostname mappings in one of
|
||||
|
|
@ -309,6 +327,8 @@ nameserver <replaceable>y.y.y.y</replaceable></programlisting>
|
|||
&man.resolv.conf.5; manual page for details of other possible
|
||||
entries in this file.</para>
|
||||
|
||||
<indexterm><primary>PPP</primary></indexterm>
|
||||
<indexterm><primary>ISP</primary></indexterm>
|
||||
<para>If you are running PPP version 2 or greater, the
|
||||
<command>enable dns</command> command will tell PPP to request
|
||||
that your ISP confirms the nameserver values. If your ISP
|
||||
|
|
@ -321,6 +341,7 @@ nameserver <replaceable>y.y.y.y</replaceable></programlisting>
|
|||
<sect3>
|
||||
<title><application>PPP</application> Configuration</title>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>configuration</secondary></indexterm>
|
||||
<para>Both <command>ppp</command> and <command>pppd</command>
|
||||
(the kernel level implementation of PPP) use the configuration
|
||||
files located in the <filename>/usr/share/examples/ppp</filename> directory.
|
||||
|
|
@ -337,6 +358,7 @@ nameserver <replaceable>y.y.y.y</replaceable></programlisting>
|
|||
<sect4 id="userppp-staticIP">
|
||||
<title>PPP and Static IP Addresses</title>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>with static IP addresses</secondary></indexterm>
|
||||
<para>You will need to create a configuration file called
|
||||
<filename>/etc/ppp/ppp.conf</filename>. It should look
|
||||
similar to the example below.</para>
|
||||
|
|
@ -397,6 +419,7 @@ nameserver <replaceable>y.y.y.y</replaceable></programlisting>
|
|||
<varlistentry>
|
||||
<term>Line 4:</term>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>user PPP</secondary></indexterm>
|
||||
<listitem>
|
||||
<para>The dial string. User PPP uses an expect-send
|
||||
syntax similar to the &man.chat.8; program. Refer to
|
||||
|
|
@ -448,7 +471,8 @@ protocol: ppp</screen>
|
|||
needs. When you write this script for the first time,
|
||||
you should enable <quote>chat</quote> logging to ensure
|
||||
that the conversation is going as expected.</para>
|
||||
|
||||
<indexterm><primary>PAP</primary></indexterm>
|
||||
<indexterm><primary>CHAP</primary></indexterm>
|
||||
<para>If you are using PAP or CHAP, there will be no login
|
||||
at this point, so your login string can be left blank.
|
||||
See <link linkend="userppp-PAPnCHAP">PAP and CHAP
|
||||
|
|
@ -459,6 +483,7 @@ protocol: ppp</screen>
|
|||
<varlistentry>
|
||||
<term>Line 8:</term>
|
||||
|
||||
<indexterm><primary>timeout</primary></indexterm>
|
||||
<listitem>
|
||||
<para>Sets the default timeout (in seconds) for the
|
||||
connection. Here, the connection will be closed
|
||||
|
|
@ -469,7 +494,7 @@ protocol: ppp</screen>
|
|||
|
||||
<varlistentry>
|
||||
<term>Line 9:</term>
|
||||
|
||||
<indexterm><primary>ISP</primary></indexterm>
|
||||
<listitem>
|
||||
<para>Sets the interface addresses. The string
|
||||
<replaceable>x.x.x.x</replaceable> should be replaced by
|
||||
|
|
@ -505,7 +530,7 @@ protocol: ppp</screen>
|
|||
|
||||
<varlistentry>
|
||||
<term>Line 11:</term>
|
||||
|
||||
<indexterm><primary>nameserver</primary></indexterm>
|
||||
<listitem>
|
||||
<para>This line tells PPP to ask your ISP to confirm that
|
||||
your nameserver addresses are correct. If your ISP
|
||||
|
|
@ -529,7 +554,8 @@ protocol: ppp</screen>
|
|||
|
||||
<sect4 id="userppp-dynamicIP">
|
||||
<title>PPP and Dynamic IP Addresses</title>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>with dynamic IP addresses</secondary></indexterm>
|
||||
<indexterm><primary>IPCP</primary></indexterm>
|
||||
<para>If your service provider does not assign static IP
|
||||
addresses, <command>ppp</command> can be configured to
|
||||
negotiate the local and remote addresses. This is done by
|
||||
|
|
@ -638,7 +664,8 @@ protocol: ppp</screen>
|
|||
|
||||
<sect4>
|
||||
<title>Receiving Incoming Calls</title>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>receiving
|
||||
incoming calls</secondary></indexterm>
|
||||
<para>When you configure <application>ppp</application> 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
|
||||
|
|
@ -703,6 +730,7 @@ protocol: ppp</screen>
|
|||
|
||||
<sect5>
|
||||
<title>PPP Shells for Dynamic-IP Users</title>
|
||||
<indexterm><primary>PPP shells</primary></indexterm>
|
||||
|
||||
<para>Create a file called
|
||||
<filename>/etc/ppp/ppp-shell</filename> containing the
|
||||
|
|
@ -750,6 +778,7 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting>
|
|||
|
||||
<sect5>
|
||||
<title>PPP shells for Static-IP Users</title>
|
||||
<indexterm><primary>PPP shells</primary></indexterm>
|
||||
|
||||
<para>Create the <filename>ppp-shell</filename> file as above
|
||||
and for each account with statically assigned IPs create a
|
||||
|
|
@ -843,7 +872,10 @@ mary:
|
|||
|
||||
<sect5 id="userppp-mgetty">
|
||||
<title><command>mgetty</command> and AutoPPP</title>
|
||||
|
||||
<indexterm><primary>mgetty</primary></indexterm>
|
||||
<indexterm><primary>AutoPPP</primary></indexterm>
|
||||
<indexterm><primary>LCP</primary></indexterm>
|
||||
|
||||
<para>Configuring and compiling <command>mgetty</command> with
|
||||
the <literal>AUTO_PPP</literal> option enabled allows
|
||||
<command>mgetty</command> to detect the LCP phase of PPP
|
||||
|
|
@ -903,7 +935,9 @@ exec /usr/sbin/ppp -direct pap$IDENT</programlisting>
|
|||
|
||||
<sect5>
|
||||
<title>MS extensions</title>
|
||||
|
||||
<indexterm><primary>DNS</primary></indexterm>
|
||||
<indexterm><primary>NetBIOS</primary></indexterm>
|
||||
<indexterm><primary>PPP</primary><secondary>Microsoft extensions</secondary></indexterm>
|
||||
<para>It is possible to configure PPP to supply DNS and
|
||||
NetBIOS nameserver addresses on demand.</para>
|
||||
|
||||
|
|
@ -932,7 +966,8 @@ set nbns 203.14.100.5</programlisting>
|
|||
|
||||
<sect4 id="userppp-PAPnCHAP">
|
||||
<title>PAP and CHAP authentication</title>
|
||||
|
||||
<indexterm><primary>PAP</primary></indexterm>
|
||||
<indexterm><primary>CHAP</primary></indexterm>
|
||||
<para>Some ISPs set their system up so that the authentication
|
||||
part of your connection is done using either of the PAP or
|
||||
CHAP authentication mechanisms. If this is the case, your ISP
|
||||
|
|
@ -983,7 +1018,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
|
||||
<varlistentry>
|
||||
<term>Line 13:</term>
|
||||
|
||||
<indexterm><primary>password</primary></indexterm>
|
||||
<listitem>
|
||||
<para>This line specifies your PAP/CHAP password. You
|
||||
will need to insert the correct value for
|
||||
|
|
@ -1028,6 +1063,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
|
||||
<sect3 id="userppp-final">
|
||||
<title>Final system configuration</title>
|
||||
<indexterm><primary>PPP</primary><secondary>configuration</secondary></indexterm>
|
||||
|
||||
<para>You now have <command>ppp</command> configured, but there
|
||||
are a few more things to do before it is ready to work. They
|
||||
|
|
@ -1066,10 +1102,12 @@ set nbns 203.14.100.5</programlisting>
|
|||
</note>
|
||||
|
||||
<para>Set the router program to <literal>NO</literal> with
|
||||
following line in your <filename>/etc/rc.conf</filename>:</para>
|
||||
following line in your
|
||||
<filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>router_enable="NO"</programlisting>
|
||||
|
||||
<indexterm><primary>routed</primary></indexterm>
|
||||
<para>It is important that the <command>routed</command> daemon is
|
||||
not started (it is started by default), as it
|
||||
<command>routed</command> tends to delete the default routing
|
||||
|
|
@ -1084,6 +1122,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
|
||||
<programlisting>sendmail_flags="-bd"</programlisting>
|
||||
|
||||
<indexterm><primary>sendmail</primary></indexterm>
|
||||
<para>The downside of this is that you must force
|
||||
<command>sendmail</command> to re-examine the mail queue
|
||||
whenever the ppp link is up by typing:</para>
|
||||
|
|
@ -1098,6 +1137,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
3 add 0 0 HISADDR
|
||||
4 !bg sendmail -bd -q30m</programlisting>
|
||||
|
||||
<indexterm><primary>SMTP</primary></indexterm>
|
||||
<para>If you don't like this, it is possible to set up a
|
||||
<quote>dfilter</quote> to block SMTP traffic. Refer to the
|
||||
sample files for further details.</para>
|
||||
|
|
@ -1217,6 +1257,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
|
||||
<sect2>
|
||||
<title>Setting up Kernel PPP</title>
|
||||
<indexterm><primary>PPP</primary><secondary>kernel PPP</secondary></indexterm>
|
||||
|
||||
<para>Before you start setting up PPP on your machine make sure
|
||||
that <command>pppd</command> is located in
|
||||
|
|
@ -1232,6 +1273,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
modem line.</para>
|
||||
</listitem>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>server</secondary></indexterm>
|
||||
<listitem>
|
||||
<para>as a <quote>server</quote>, i.e. your machine is located on
|
||||
the network and used to connect other computers using
|
||||
|
|
@ -1251,7 +1293,8 @@ set nbns 203.14.100.5</programlisting>
|
|||
|
||||
<sect2>
|
||||
<title>Using <command>pppd</command> as a client</title>
|
||||
|
||||
<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>
|
||||
|
||||
|
|
@ -1272,7 +1315,9 @@ defaultroute # put this if you want that PPP server will be your
|
|||
# default router</programlisting>
|
||||
|
||||
<para>To connect:</para>
|
||||
|
||||
|
||||
<indexterm><primary>kermit</primary></indexterm>
|
||||
<indexterm><primary>modem</primary></indexterm>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Dial to the remote host using kermit (or some other modem
|
||||
|
|
@ -1321,6 +1366,7 @@ ifconfig ppp0 delete
|
|||
kermit -y /etc/ppp/kermit.dial
|
||||
pppd /dev/tty01 19200</programlisting>
|
||||
|
||||
<indexterm><primary>kermit</primary></indexterm>
|
||||
<para><filename>/etc/ppp/kermit.dial</filename> is a kermit script
|
||||
that dials and makes all necessary authorization on the remote
|
||||
host (an example of such a script is attached to the end of this
|
||||
|
|
@ -1653,6 +1699,8 @@ exit 1
|
|||
|
||||
<sect1 id="pppoe">
|
||||
<title>Using <application>PPP</application> over Ethernet (PPPoE)</title>
|
||||
<indexterm><primary>PPP</primary><secondary>over Ethernet</secondary></indexterm>
|
||||
<indexterm><primary>PPPoE (see PPP, over Ethernet)</primary></indexterm>
|
||||
|
||||
<para><emphasis>Contributed by &a.jim; (from <ulink
|
||||
url="http://node.to/freebsd/how-tos/how-to-freebsd-pppoe.html">node.to</ulink>) 10 Jan 2000.</emphasis></para>
|
||||
|
|
@ -1679,7 +1727,7 @@ exit 1
|
|||
|
||||
<sect2>
|
||||
<title>Kernel Configuration</title>
|
||||
|
||||
<indexterm><primary>kernel</primary><secondary>configuration</secondary></indexterm>
|
||||
<para>You will need to set the following options in your kernel
|
||||
configuration file and then <link linkend="kernelconfig">compile a new
|
||||
kernel</link>.</para>
|
||||
|
|
@ -1779,10 +1827,12 @@ ppp_profile="default" # or your provider</programlisting>
|
|||
url="http://www.3com.com/">3Com</ulink> if you think it should
|
||||
comply with the PPPoE specification.</para>
|
||||
|
||||
<indexterm><primary>ADSL</primary></indexterm>
|
||||
<para>If you absolutely want to use your ADSL connection with
|
||||
FreeBSD and are stuck with this modem, you can either:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<indexterm><primary>DSL</primary></indexterm>
|
||||
<listitem>
|
||||
<para>Try replacing the modem with a different brand or model
|
||||
if your DSL provider permits you to do so. If you are not
|
||||
|
|
@ -1973,14 +2023,14 @@ ppp_profile="default" # or your provider</programlisting>
|
|||
|
||||
<sect1 id="slip">
|
||||
<title>Using SLIP</title>
|
||||
|
||||
<indexterm><primary>SLIP</primary></indexterm>
|
||||
<para><emphasis>Originally contributed by &a.asami; and
|
||||
&a.ghelmer;, with input from &a.wilko; and
|
||||
&a.piero;.</emphasis></para>
|
||||
|
||||
<sect2 id="slipc">
|
||||
<title>Setting up a SLIP Client</title>
|
||||
|
||||
<indexterm><primary>SLIP</primary><secondary>client</secondary></indexterm>
|
||||
<para>The following is one way to set up a FreeBSD machine for SLIP
|
||||
on a static host network. For dynamic hostname assignments (i.e.,
|
||||
your address changes each time you dial up), you probably need to
|
||||
|
|
@ -2062,6 +2112,7 @@ ppp_profile="default" # or your provider</programlisting>
|
|||
<programlisting>ifconfig_sl0="inet ${hostname} slip-gateway netmask 0xffffff00 up"</programlisting>
|
||||
</listitem>
|
||||
|
||||
<indexterm><primary>default router</primary></indexterm>
|
||||
<listitem>
|
||||
<para>Designate the default router by changing the
|
||||
line:</para>
|
||||
|
|
@ -2083,6 +2134,8 @@ ppp_profile="default" # or your provider</programlisting>
|
|||
nameserver 128.32.136.9
|
||||
nameserver 128.32.136.12</programlisting>
|
||||
|
||||
<indexterm><primary>name server</primary></indexterm>
|
||||
<indexterm><primary>domain name</primary></indexterm>
|
||||
<para>As you can see, these set up the nameserver hosts. Of
|
||||
course, the actual domain names and addresses depend on your
|
||||
environment.</para>
|
||||
|
|
@ -2105,7 +2158,7 @@ nameserver 128.32.136.12</programlisting>
|
|||
|
||||
<sect3>
|
||||
<title>Making a SLIP connection</title>
|
||||
|
||||
<indexterm><primary>SLIP</primary><secondary>connecting with</secondary></indexterm>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Dial up, type <command>slip</command> at the prompt,
|
||||
|
|
@ -2233,6 +2286,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
|
|||
|
||||
<sect2 id="slips">
|
||||
<title>Setting up a SLIP Server</title>
|
||||
<indexterm><primary>SLIP</primary><secondary>server</secondary></indexterm>
|
||||
|
||||
<para>This document provides suggestions for setting up SLIP Server
|
||||
services on a FreeBSD system, which typically means configuring
|
||||
|
|
@ -2245,7 +2299,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
|
|||
|
||||
<sect3 id="slips-prereqs">
|
||||
<title>Prerequisites</title>
|
||||
|
||||
<indexterm><primary>TCP/IP</primary></indexterm>
|
||||
<para>This document is very technical in nature, so background
|
||||
knowledge is required. It is assumed that you are familiar with
|
||||
the TCP/IP network protocol, and in particular, network and node
|
||||
|
|
@ -2258,6 +2312,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
|
|||
0-937175-82-X), or Douglas Comer's books on the TCP/IP
|
||||
protocol.</para>
|
||||
|
||||
<indexterm><primary>modem</primary></indexterm>
|
||||
<para>It is further assumed that you have already setup your
|
||||
modem(s) and configured the appropriate system files to allow
|
||||
logins through your modems. If you have not prepared your
|
||||
|
|
@ -2341,7 +2396,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
|
|||
|
||||
<sect3>
|
||||
<title>Kernel Configuration</title>
|
||||
|
||||
<indexterm><primary>kernel</primary><secondary>configuration</secondary></indexterm>
|
||||
<para>FreeBSD's default kernels usually come with two SLIP
|
||||
interfaces defined (<devicename>sl0</devicename> and
|
||||
<devicename>sl1</devicename>); you can use <command>netstat
|
||||
|
|
@ -2385,6 +2440,7 @@ sl1* 296 <Link> 0 0 0 0
|
|||
|
||||
<programlisting>pseudo-device sl 2</programlisting>
|
||||
|
||||
<indexterm><primary>SLIP</primary></indexterm>
|
||||
<para>This is the line that defines the number of SLIP devices
|
||||
available in the kernel; the number at the end of the line is
|
||||
the maximum number of SLIP connections that may be operating
|
||||
|
|
@ -2485,6 +2541,8 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
in FreeBSD 2.2 (unless your <filename>slip.login</filename>
|
||||
script included code to make use of the flags).</para>
|
||||
|
||||
<indexterm><primary>SLIP</primary></indexterm>
|
||||
<indexterm><primary>TCP/IP</primary></indexterm>
|
||||
<para>Your choice of local and remote addresses for your SLIP
|
||||
links depends on whether you are going to dedicate a TCP/IP
|
||||
subnet or if you are going to use <quote>proxy ARP</quote> on
|
||||
|
|
@ -2495,6 +2553,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
<link linkend="slips-prereqs">slips-prereqs</link> section
|
||||
and/or consult your IP network manager.</para>
|
||||
|
||||
<indexterm><primary>gated</primary></indexterm>
|
||||
<para>If you are going to use a separate subnet for your SLIP
|
||||
clients, you will need to allocate the subnet number out of
|
||||
your assigned IP network number and assign each of your SLIP
|
||||
|
|
@ -2506,6 +2565,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
your other routers to inform them about your SLIP server's
|
||||
route to the SLIP subnet.</para>
|
||||
|
||||
<indexterm><primary>Ethernet</primary></indexterm>
|
||||
<para>Otherwise, if you will use the <quote>proxy ARP</quote>
|
||||
method, you will need to assign your SLIP client's IP
|
||||
addresses out of your SLIP server's Ethernet subnet, and you
|
||||
|
|
@ -2566,6 +2626,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
address whenever a another IP node on the Ethernet asks to
|
||||
speak to the SLIP client's IP address.</para>
|
||||
|
||||
<indexterm><primary>Ethernet</primary><secondary>MAC address</secondary></indexterm>
|
||||
<para>When using the example above, be sure to replace the
|
||||
Ethernet MAC address (<hostid
|
||||
role="mac">00:11:22:33:44:55</hostid>) with the MAC address of
|
||||
|
|
@ -2650,7 +2711,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
|
||||
<sect3>
|
||||
<title>Routing Considerations</title>
|
||||
|
||||
<indexterm><primary>SLIP</primary><secondary>routing</secondary></indexterm>
|
||||
<para>If you are not using the <quote>proxy ARP</quote> method for
|
||||
routing packets between your SLIP clients and the rest of your
|
||||
network (and perhaps the Internet), you will probably either
|
||||
|
|
@ -2662,7 +2723,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
|
||||
<sect4>
|
||||
<title>Static Routes</title>
|
||||
|
||||
<indexterm><primary>static routes</primary></indexterm>
|
||||
<para>Adding static routes to your nearest default routers can
|
||||
be troublesome (or impossible, if you do not have authority to
|
||||
do so...). If you have a multiple-router network in your
|
||||
|
|
@ -2676,7 +2737,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
|
||||
<sect4>
|
||||
<title>Running <command>gated</command></title>
|
||||
|
||||
<indexterm><primary>gated</primary></indexterm>
|
||||
<para>An alternative to the headaches of static routes is to
|
||||
install <command>gated</command> on your FreeBSD SLIP server
|
||||
and configure it to use the appropriate routing protocols
|
||||
|
|
@ -2735,6 +2796,7 @@ import proto rip interface ed {
|
|||
all ;
|
||||
} ;</programlisting>
|
||||
|
||||
<indexterm><primary>RIP</primary></indexterm>
|
||||
<para>The above sample <filename>gated.conf</filename> file
|
||||
broadcasts routing information regarding the SLIP subnet
|
||||
<replaceable>xxx.xxx.yy</replaceable> via RIP onto the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue