- Whitespace cleanup and indentaion changes. Translators can ignore this
change.
This commit is contained in:
Gabor Kovesdan
parent
dfd24d9758
commit
1c4519ff04
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=31971
1 changed files with 252 additions and 124 deletions
|
|
@ -92,10 +92,11 @@
|
|||
|
||||
<note>
|
||||
<para>Throughout in this chapter, user PPP will simply be
|
||||
referred to as <application>ppp</application> unless a distinction needs to be made between it
|
||||
and any other PPP software such as <application>pppd</application>.
|
||||
Unless otherwise stated, all of the commands explained in this
|
||||
chapter should be executed as <username>root</username>.</para>
|
||||
referred to as <application>ppp</application> unless a distinction
|
||||
needs to be made between it and any other PPP software such as
|
||||
<application>pppd</application>. Unless otherwise stated, all of
|
||||
the commands explained in this chapter should be executed as
|
||||
<username>root</username>.</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -249,7 +250,11 @@
|
|||
<sect3>
|
||||
<title>Automatic <application>PPP</application> Configuration</title>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>configuration</secondary></indexterm>
|
||||
<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>/etc/ppp</filename> directory.
|
||||
|
|
@ -266,7 +271,11 @@
|
|||
<sect4 id="userppp-staticIP">
|
||||
<title>PPP and Static IP Addresses</title>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>with static IP addresses</secondary></indexterm>
|
||||
<indexterm>
|
||||
<primary>PPP</primary>
|
||||
<secondary>with static IP addresses</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>You will need to edit the
|
||||
<filename>/etc/ppp/ppp.conf</filename> configuration file. It
|
||||
should look similar to the example below.</para>
|
||||
|
|
@ -339,9 +348,11 @@
|
|||
<listitem>
|
||||
<para>Identifies the device to which the modem is
|
||||
connected. <devicename>COM1</devicename> is
|
||||
<filename>/dev/cuad0</filename> (or <filename>/dev/cuaa0</filename> under &os; 5.X) and
|
||||
<filename>/dev/cuad0</filename> (or
|
||||
<filename>/dev/cuaa0</filename> under &os; 5.X) and
|
||||
<devicename>COM2</devicename> is
|
||||
<filename>/dev/cuad1</filename> (or <filename>/dev/cuaa1</filename>).</para>
|
||||
<filename>/dev/cuad1</filename> (or
|
||||
<filename>/dev/cuaa1</filename>).</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -358,7 +369,11 @@
|
|||
<varlistentry>
|
||||
<term>Line 6 & 7:</term>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>user PPP</secondary></indexterm>
|
||||
<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
|
||||
|
|
@ -545,8 +560,16 @@ 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>
|
||||
|
||||
<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
|
||||
|
|
@ -637,8 +660,12 @@ protocol: ppp</screen>
|
|||
|
||||
<sect4>
|
||||
<title>Receiving Incoming Calls</title>
|
||||
<indexterm><primary>PPP</primary><secondary>receiving
|
||||
incoming calls</secondary></indexterm>
|
||||
|
||||
<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
|
||||
|
|
@ -659,7 +686,7 @@ protocol: ppp</screen>
|
|||
dial-up services using &man.getty.8;.</para>
|
||||
|
||||
<para>An alternative to <command>getty</command> is <ulink
|
||||
url="http://www.leo.org/~doering/mgetty/index.html">mgetty</ulink>,
|
||||
url="http://www.leo.org/~doering/mgetty/index.html">mgetty</ulink>,
|
||||
a smarter version of <command>getty</command> designed
|
||||
with dial-up lines in mind.</para>
|
||||
|
||||
|
|
@ -704,7 +731,10 @@ protocol: ppp</screen>
|
|||
|
||||
<sect4>
|
||||
<title>PPP Shells for Dynamic-IP Users</title>
|
||||
<indexterm><primary>PPP shells</primary></indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>PPP shells</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>Create a file called
|
||||
<filename>/etc/ppp/ppp-shell</filename> containing the
|
||||
|
|
@ -752,7 +782,10 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting>
|
|||
|
||||
<sect4>
|
||||
<title>PPP Shells for Static-IP Users</title>
|
||||
<indexterm><primary>PPP shells</primary></indexterm>
|
||||
|
||||
<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
|
||||
|
|
@ -774,7 +807,8 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting>
|
|||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>Setting Up <filename>ppp.conf</filename> for Dynamic-IP Users</title>
|
||||
<title>Setting Up <filename>ppp.conf</filename> for Dynamic-IP
|
||||
Users</title>
|
||||
|
||||
<para>The <filename>/etc/ppp/ppp.conf</filename> file should
|
||||
contain something along the lines of:</para>
|
||||
|
|
@ -841,11 +875,18 @@ mary:
|
|||
|
||||
<sect4 id="userppp-mgetty">
|
||||
<title><command>mgetty</command> and AutoPPP</title>
|
||||
|
||||
<indexterm>
|
||||
<primary><command>mgetty</command></primary>
|
||||
</indexterm>
|
||||
<indexterm><primary>AutoPPP</primary></indexterm>
|
||||
<indexterm><primary>LCP</primary></indexterm>
|
||||
<primary><command>mgetty</command></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
|
||||
|
|
@ -906,9 +947,20 @@ exec /usr/sbin/ppp -direct pap$IDENT</programlisting>
|
|||
|
||||
<sect4>
|
||||
<title>MS Extensions</title>
|
||||
<indexterm><primary>DNS</primary></indexterm>
|
||||
<indexterm><primary>NetBIOS</primary></indexterm>
|
||||
<indexterm><primary>PPP</primary><secondary>Microsoft extensions</secondary></indexterm>
|
||||
|
||||
<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>
|
||||
|
||||
|
|
@ -1028,35 +1080,41 @@ set nbns 203.14.100.5</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="userppp-nat">
|
||||
<title>Using PPP Network Address Translation Capability</title>
|
||||
<indexterm><primary>PPP</primary><secondary>NAT</secondary></indexterm>
|
||||
<title>Using PPP Network Address Translation Capability</title>
|
||||
|
||||
<para>PPP has ability to use internal NAT without kernel diverting
|
||||
capabilities. This functionality may be enabled by the following
|
||||
line in <filename>/etc/ppp/ppp.conf</filename>:</para>
|
||||
<indexterm>
|
||||
<primary>PPP</primary><secondary>NAT</secondary>
|
||||
</indexterm>
|
||||
|
||||
<programlisting>nat enable yes</programlisting>
|
||||
<para>PPP has ability to use internal NAT without kernel diverting
|
||||
capabilities. This functionality may be enabled by the following
|
||||
line in <filename>/etc/ppp/ppp.conf</filename>:</para>
|
||||
|
||||
<para>Alternatively, PPP NAT may be enabled by command-line
|
||||
option <literal>-nat</literal>. There is also
|
||||
<filename>/etc/rc.conf</filename> knob named
|
||||
<literal>ppp_nat</literal>, which is enabled by default.</para>
|
||||
<programlisting>nat enable yes</programlisting>
|
||||
|
||||
<para>If you use this feature, you may also find useful
|
||||
the following <filename>/etc/ppp/ppp.conf</filename> options
|
||||
to enable incoming connections forwarding:</para>
|
||||
<para>Alternatively, PPP NAT may be enabled by command-line
|
||||
option <literal>-nat</literal>. There is also
|
||||
<filename>/etc/rc.conf</filename> knob named
|
||||
<literal>ppp_nat</literal>, which is enabled by default.</para>
|
||||
|
||||
<programlisting>nat port tcp 10.0.0.2:ftp ftp
|
||||
<para>If you use this feature, you may also find useful
|
||||
the following <filename>/etc/ppp/ppp.conf</filename> options
|
||||
to enable incoming connections forwarding:</para>
|
||||
|
||||
<programlisting>nat port tcp 10.0.0.2:ftp ftp
|
||||
nat port tcp 10.0.0.2:http http</programlisting>
|
||||
|
||||
<para>or do not trust the outside at all</para>
|
||||
<para>or do not trust the outside at all</para>
|
||||
|
||||
<programlisting>nat deny_incoming yes</programlisting>
|
||||
<programlisting>nat deny_incoming yes</programlisting>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="userppp-final">
|
||||
<title>Final System Configuration</title>
|
||||
<indexterm><primary>PPP</primary><secondary>configuration</secondary></indexterm>
|
||||
|
||||
<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
|
||||
|
|
@ -1095,19 +1153,19 @@ ifconfig_tun0=</programlisting>
|
|||
for further details.</para>
|
||||
</note>
|
||||
|
||||
<para>Make sure that the router program is set to <literal>NO</literal> with
|
||||
the following line in your
|
||||
<para>Make sure that the router program is set to
|
||||
<literal>NO</literal> with the following line in your
|
||||
<filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>router_enable="NO"</programlisting>
|
||||
|
||||
<indexterm>
|
||||
<primary><application>routed</application></primary>
|
||||
</indexterm>
|
||||
<primary><application>routed</application></primary>
|
||||
</indexterm>
|
||||
|
||||
<para>It is important that the <command>routed</command> daemon is
|
||||
not started, as
|
||||
<command>routed</command> tends to delete the default routing
|
||||
table entries created by <command>ppp</command>.</para>
|
||||
not started, as <command>routed</command> tends to delete the default
|
||||
routing table entries created by <command>ppp</command>.</para>
|
||||
|
||||
<para>It is probably a good idea to ensure that the
|
||||
<literal>sendmail_flags</literal> line does not include the
|
||||
|
|
@ -1135,7 +1193,10 @@ ifconfig_tun0=</programlisting>
|
|||
3 add 0 0 HISADDR
|
||||
4 !bg sendmail -bd -q30m</programlisting>
|
||||
|
||||
<indexterm><primary>SMTP</primary></indexterm>
|
||||
<indexterm>
|
||||
<primary>SMTP</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>If you do not 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>
|
||||
|
|
@ -1264,7 +1325,11 @@ ifconfig_tun0=</programlisting>
|
|||
|
||||
<sect2>
|
||||
<title>Setting Up Kernel PPP</title>
|
||||
<indexterm><primary>PPP</primary><secondary>kernel PPP</secondary></indexterm>
|
||||
|
||||
<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
|
||||
|
|
@ -1280,7 +1345,11 @@ ifconfig_tun0=</programlisting>
|
|||
modem line.</para>
|
||||
</listitem>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>server</secondary></indexterm>
|
||||
<indexterm>
|
||||
<primary>PPP</primary>
|
||||
<secondary>server</secondary>
|
||||
</indexterm>
|
||||
|
||||
<listitem>
|
||||
<para>As a <quote>server</quote> — your machine is located on
|
||||
the network, and is used to connect other computers using
|
||||
|
|
@ -1311,8 +1380,16 @@ ifconfig_tun0=</programlisting>
|
|||
</sect2info>
|
||||
|
||||
<title>Using <command>pppd</command> as a Client</title>
|
||||
<indexterm><primary>PPP</primary><secondary>client</secondary></indexterm>
|
||||
<indexterm><primary>Cisco</primary></indexterm>
|
||||
|
||||
<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>
|
||||
|
||||
|
|
@ -1338,7 +1415,8 @@ defaultroute # put this if you want that PPP server will be your
|
|||
<indexterm><primary>modem</primary></indexterm>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Dial to the remote host using <application>Kermit</application> (or some other modem
|
||||
<para>Dial to the remote host using
|
||||
<application>Kermit</application> (or some other modem
|
||||
program), and enter your user name and password (or whatever
|
||||
is needed to enable PPP on the remote host).</para>
|
||||
</step>
|
||||
|
|
@ -1385,11 +1463,14 @@ 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 <application>Kermit</application>
|
||||
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 document).</para>
|
||||
<indexterm>
|
||||
<primary>Kermit</primary>
|
||||
</indexterm>
|
||||
|
||||
<para><filename>/etc/ppp/kermit.dial</filename> is a
|
||||
<application>Kermit</application> 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 document).</para>
|
||||
|
||||
<para>Use the following <filename>/etc/ppp/pppdown</filename> script
|
||||
to disconnect the PPP line:</para>
|
||||
|
|
@ -1413,9 +1494,9 @@ fi
|
|||
kermit -y /etc/ppp/kermit.hup
|
||||
/etc/ppp/ppptest</programlisting>
|
||||
|
||||
<para>Check to see if <command>pppd</command> is still running by executing
|
||||
<filename>/usr/etc/ppp/ppptest</filename>, which should look like
|
||||
this:</para>
|
||||
<para>Check to see if <command>pppd</command> is still running by
|
||||
executing <filename>/usr/etc/ppp/ppptest</filename>, which should look
|
||||
like this:</para>
|
||||
|
||||
<programlisting>#!/bin/sh
|
||||
pid=`pgrep pppd`
|
||||
|
|
@ -1725,19 +1806,22 @@ exit 1
|
|||
</sect1info>
|
||||
<title>Troubleshooting <acronym>PPP</acronym> Connections</title>
|
||||
|
||||
<indexterm><primary>PPP</primary><secondary>troubleshooting</secondary></indexterm>
|
||||
<indexterm>
|
||||
<primary>PPP</primary>
|
||||
<secondary>troubleshooting</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>This section covers a few issues which may arise when
|
||||
using PPP over a modem connection. For instance, perhaps you
|
||||
need to know exactly what prompts the system you are dialing
|
||||
into will present. Some <acronym>ISP</acronym>s present the
|
||||
<literal>ssword</literal> prompt, and others will present
|
||||
<literal>password</literal>; if the <command>ppp</command>
|
||||
script is not written accordingly, the login attempt will
|
||||
fail. The most common way to debug <command>ppp</command>
|
||||
connections is by connecting manually. The following
|
||||
information will walk you through a manual connection step by
|
||||
step.</para>
|
||||
<para>This section covers a few issues which may arise when
|
||||
using PPP over a modem connection. For instance, perhaps you
|
||||
need to know exactly what prompts the system you are dialing
|
||||
into will present. Some <acronym>ISP</acronym>s present the
|
||||
<literal>ssword</literal> prompt, and others will present
|
||||
<literal>password</literal>; if the <command>ppp</command>
|
||||
script is not written accordingly, the login attempt will
|
||||
fail. The most common way to debug <command>ppp</command>
|
||||
connections is by connecting manually. The following
|
||||
information will walk you through a manual connection step by
|
||||
step.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Check the Device Nodes</title>
|
||||
|
|
@ -1754,11 +1838,12 @@ exit 1
|
|||
<devicename>sio</devicename> devices. These are the COM
|
||||
ports we need. If your modem acts like a standard serial
|
||||
port then you should see it listed on
|
||||
<devicename>sio1</devicename>, or <devicename>COM2</devicename>. If so, you are not
|
||||
required to rebuild the kernel.
|
||||
<devicename>sio1</devicename>, or <devicename>COM2</devicename>. If
|
||||
so, you are not required to rebuild the kernel.
|
||||
When matching up sio modem is on <devicename>sio1</devicename> or
|
||||
<devicename>COM2</devicename> if you are in DOS, then your
|
||||
modem device would be <filename>/dev/cuad1</filename> (or <filename>/dev/cuaa1</filename> under &os; 5.X).</para>
|
||||
modem device would be <filename>/dev/cuad1</filename> (or
|
||||
<filename>/dev/cuaa1</filename> under &os; 5.X).</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
@ -1782,7 +1867,8 @@ exit 1
|
|||
<screen>ppp ON example> <userinput>set device <filename>/dev/cuad1</filename></userinput></screen>
|
||||
|
||||
<para>We set our modem device, in this case it is
|
||||
<devicename>cuad1</devicename> (or <filename>/dev/cuaa1</filename> under &os; 5.X).</para>
|
||||
<devicename>cuad1</devicename> (or
|
||||
<filename>/dev/cuaa1</filename> under &os; 5.X).</para>
|
||||
|
||||
<screen>ppp ON example> <userinput>set speed 115200</userinput></screen>
|
||||
|
||||
|
|
@ -1986,7 +2072,12 @@ nameserver <replaceable>y.y.y.y</replaceable></programlisting>
|
|||
</sect1info>
|
||||
|
||||
<title>Using PPP over Ethernet (PPPoE)</title>
|
||||
<indexterm><primary>PPP</primary><secondary>over Ethernet</secondary></indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>PPP</primary>
|
||||
<secondary>over Ethernet</secondary>
|
||||
</indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>PPPoE</primary>
|
||||
<see>PPP, over Ethernet</see>
|
||||
|
|
@ -2099,10 +2190,12 @@ ppp_profile="name_of_service_provider"</programlisting>
|
|||
|
||||
<sect2 id="ppp-3com">
|
||||
|
||||
<title>PPPoE with a &tm.3com; <trademark class="registered">HomeConnect</trademark> ADSL Modem Dual Link</title>
|
||||
<title>PPPoE with a &tm.3com; <trademark
|
||||
class="registered">HomeConnect</trademark> ADSL Modem Dual
|
||||
Link</title>
|
||||
|
||||
<para>This modem does not follow <ulink
|
||||
url="http://www.faqs.org/rfcs/rfc2516.html">RFC 2516</ulink>
|
||||
url="http://www.faqs.org/rfcs/rfc2516.html">RFC 2516</ulink>
|
||||
(<emphasis>A Method for transmitting PPP over Ethernet
|
||||
(PPPoE)</emphasis>, written by L. Mamakos, K. Lidl, J. Evarts,
|
||||
D. Carrel, D. Simone, and R. Wheeler). Instead, different packet
|
||||
|
|
@ -2122,14 +2215,20 @@ ppp_profile="name_of_service_provider"</programlisting>
|
|||
|
||||
<para>Unfortunately, because this is a system-wide setting, it is
|
||||
not possible to talk to a normal PPPoE client or server and a
|
||||
&tm.3com; <trademark class="registered">HomeConnect</trademark> ADSL Modem at the same time.</para>
|
||||
&tm.3com; <trademark class="registered">HomeConnect</trademark>
|
||||
ADSL Modem at the same time.</para>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="pppoa">
|
||||
<title>Using <application>PPP</application> over ATM (PPPoA)</title>
|
||||
<indexterm><primary>PPP</primary><secondary>over ATM</secondary></indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>PPP</primary>
|
||||
<secondary>over ATM</secondary>
|
||||
</indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>PPPoA</primary>
|
||||
<see>PPP, over ATM</see>
|
||||
|
|
@ -2343,8 +2442,8 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500
|
|||
|
||||
<para>This will open a tunnel for a PPP session to your DSL router.
|
||||
Ethernet DSL modems have a preconfigured LAN IP address which you
|
||||
connect to. In the case of the Alcatel &speedtouch; Home this address is
|
||||
<hostid role="ipaddr">10.0.0.138</hostid>. Your router documentation
|
||||
connect to. In the case of the Alcatel &speedtouch; Home this address
|
||||
is <hostid role="ipaddr">10.0.0.138</hostid>. Your router documentation
|
||||
should tell you which address your device uses. To open the tunnel and
|
||||
start a PPP session execute the following
|
||||
command:</para>
|
||||
|
|
@ -2406,7 +2505,12 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
|
|||
|
||||
<sect2 id="slipc">
|
||||
<title>Setting Up a SLIP Client</title>
|
||||
<indexterm><primary>SLIP</primary><secondary>client</secondary></indexterm>
|
||||
|
||||
<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 (your
|
||||
address changes each time you dial up), you probably need to
|
||||
|
|
@ -2415,15 +2519,18 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
|
|||
<para>First, determine which serial port your modem is connected to.
|
||||
Many people set up a symbolic link, such as
|
||||
<filename>/dev/modem</filename>, to point to the real device name,
|
||||
<filename>/dev/cuadN</filename> (or <filename>/dev/cuaaN</filename> under &os; 5.X). 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
|
||||
<filename>.kermrc</filename> files all over the system!</para>
|
||||
<filename>/dev/cuadN</filename> (or <filename>/dev/cuaaN</filename>
|
||||
under &os; 5.X). 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 <filename>.kermrc</filename> files all
|
||||
over the system!</para>
|
||||
|
||||
<note>
|
||||
<para><filename>/dev/cuad0</filename> (or <filename>/dev/cuaa0</filename> under &os; 5.X) is
|
||||
<devicename>COM1</devicename>, <filename>cuad1</filename> (or <filename>/dev/cuaa1</filename>) is
|
||||
<para><filename>/dev/cuad0</filename> (or
|
||||
<filename>/dev/cuaa0</filename> under &os; 5.X) is
|
||||
<devicename>COM1</devicename>, <filename>cuad1</filename> (or
|
||||
<filename>/dev/cuaa1</filename>) is
|
||||
<devicename>COM2</devicename>, etc.</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -2521,13 +2628,19 @@ nameserver 128.32.136.12</programlisting>
|
|||
|
||||
<sect3>
|
||||
<title>Making a SLIP Connection</title>
|
||||
<indexterm><primary>SLIP</primary><secondary>connecting with</secondary></indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>SLIP</primary>
|
||||
<secondary>connecting with</secondary>
|
||||
</indexterm>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Dial up, type <command>slip</command> at the prompt,
|
||||
enter your machine name and password. What is required to
|
||||
be entered depends on your environment. If you use
|
||||
<application>Kermit</application>, you can try a script like this:</para>
|
||||
<application>Kermit</application>, you can try a script like
|
||||
this:</para>
|
||||
|
||||
<programlisting># kermit setup
|
||||
set modem hayes
|
||||
|
|
@ -2545,8 +2658,8 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
|
|||
|
||||
<para>Of course, you have to change the username and password
|
||||
to fit yours. After doing so, you can just type
|
||||
<command>slip</command> from the <application>Kermit</application> prompt to
|
||||
connect.</para>
|
||||
<command>slip</command> from the
|
||||
<application>Kermit</application> prompt to connect.</para>
|
||||
|
||||
<note>
|
||||
<para>Leaving your password in plain text anywhere in the
|
||||
|
|
@ -2556,7 +2669,8 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<para>Leave the <application>Kermit</application> there (you can suspend it by
|
||||
<para>Leave the <application>Kermit</application> there (you can
|
||||
suspend it by
|
||||
<keycombo>
|
||||
<keycap>Ctrl</keycap>
|
||||
<keycap>z</keycap>
|
||||
|
|
@ -2582,9 +2696,8 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
|
|||
|
||||
<para>to kill <command>slattach</command>. Keep in mind you must be
|
||||
<username>root</username> to do the above. Then go back to
|
||||
<command>kermit</command> (by running <command>fg</command> if you suspended it) and
|
||||
exit from
|
||||
it (<keycap>q</keycap>).</para>
|
||||
<command>kermit</command> (by running <command>fg</command> if you
|
||||
suspended it) and exit from it (<keycap>q</keycap>).</para>
|
||||
|
||||
<para>The &man.slattach.8; manual page says you have
|
||||
to use <command>ifconfig sl0 down</command>
|
||||
|
|
@ -2600,8 +2713,8 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
|
|||
<sect3>
|
||||
<title>Troubleshooting</title>
|
||||
|
||||
<para>If it does not work, feel free to ask on &a.net.name; mailing list. The things that
|
||||
people tripped over so far:</para>
|
||||
<para>If it does not work, feel free to ask on &a.net.name; mailing
|
||||
list. The things that people tripped over so far:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -2658,7 +2771,11 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
|
|||
|
||||
<sect2 id="slips">
|
||||
<title>Setting Up a SLIP Server</title>
|
||||
<indexterm><primary>SLIP</primary><secondary>server</secondary></indexterm>
|
||||
|
||||
<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
|
||||
|
|
@ -2757,8 +2874,8 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
|
|||
any additional flags (<literal>autocomp</literal>). If
|
||||
something goes wrong, <command>sliplogin</command> usually
|
||||
logs good informational messages via the
|
||||
<application>syslogd</application> daemon facility, which usually logs
|
||||
to <filename>/var/log/messages</filename> (see the manual
|
||||
<application>syslogd</application> daemon facility, which usually
|
||||
logs to <filename>/var/log/messages</filename> (see the manual
|
||||
pages for &man.syslogd.8; and &man.syslog.conf.5; and perhaps
|
||||
check <filename>/etc/syslog.conf</filename> to see to what
|
||||
<application>syslogd</application> is logging and where it is
|
||||
|
|
@ -2768,8 +2885,15 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
|
|||
|
||||
<sect3>
|
||||
<title>Kernel Configuration</title>
|
||||
<indexterm><primary>kernel</primary><secondary>configuration</secondary></indexterm>
|
||||
<indexterm><primary>SLIP</primary></indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>kernel</primary>
|
||||
<secondary>configuration</secondary>
|
||||
</indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>SLIP</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>&os;'s default kernel (<filename>GENERIC</filename>)
|
||||
comes with SLIP (&man.sl.4;) support; in case of a custom
|
||||
|
|
@ -2781,8 +2905,8 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
|
|||
<para>By default, your &os; machine will not forward packets.
|
||||
If you want your FreeBSD SLIP Server to act as a router, you
|
||||
will have to edit the <filename>/etc/rc.conf</filename> file and
|
||||
change the setting of the <literal>gateway_enable</literal> variable to
|
||||
<option>YES</option>.</para>
|
||||
change the setting of the <literal>gateway_enable</literal> variable
|
||||
to <option>YES</option>.</para>
|
||||
|
||||
<para>You will then need to reboot for the new settings to take
|
||||
effect.</para>
|
||||
|
|
@ -2837,8 +2961,8 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
|
|||
(resolved to IP addresses by
|
||||
<filename>/etc/hosts</filename> or by the domain name
|
||||
service, depending on your specifications in the file
|
||||
<filename>/etc/nsswitch.conf</filename>), and the network mask may be
|
||||
a name that can be resolved by a lookup into
|
||||
<filename>/etc/nsswitch.conf</filename>), and the network mask
|
||||
may be a name that can be resolved by a lookup into
|
||||
<filename>/etc/networks</filename>. On a sample system,
|
||||
<filename>/etc/sliphome/slip.hosts</filename> looks like
|
||||
this:</para>
|
||||
|
|
@ -2955,7 +3079,11 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
address whenever 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>
|
||||
<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
|
||||
|
|
@ -3073,8 +3201,8 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
</indexterm>
|
||||
|
||||
<note>
|
||||
<para><application>&gated;</application> is proprietary software now and
|
||||
will not be available as source code to the public anymore
|
||||
<para><application>&gated;</application> is proprietary software now
|
||||
and will not be available as source code to the public anymore
|
||||
(more info on the <ulink
|
||||
url="http://www.gated.org/">&gated;</ulink> website). This
|
||||
section only exists to ensure backwards compatibility for
|
||||
|
|
@ -3082,12 +3210,12 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
|
|||
</note>
|
||||
|
||||
<para>An alternative to the headaches of static routes is to
|
||||
install <application>&gated;</application> on your FreeBSD SLIP server
|
||||
and configure it to use the appropriate routing protocols
|
||||
install <application>&gated;</application> on your FreeBSD SLIP
|
||||
server and configure it to use the appropriate routing protocols
|
||||
(RIP/OSPF/BGP/EGP) to tell other routers about your SLIP
|
||||
subnet.
|
||||
You will need to write a <filename>/etc/gated.conf</filename>
|
||||
file to configure your <application>&gated;</application>; here is a sample, similar to
|
||||
subnet. You will need to write a
|
||||
<filename>/etc/gated.conf</filename> file to configure your
|
||||
<application>&gated;</application>; here is a sample, similar to
|
||||
what the author used on a FreeBSD SLIP server:</para>
|
||||
|
||||
<programlisting>#
|
||||
|
|
@ -3139,10 +3267,10 @@ import proto rip interface ed {
|
|||
tracing to <filename>/var/tmp/gated.output</filename> for
|
||||
debugging <application>&gated;</application>'s activity; you can
|
||||
certainly turn off the tracing options if
|
||||
<application>&gated;</application> works correctly for you. You will need to
|
||||
change the <replaceable>xxx.xxx.yy</replaceable>'s into the
|
||||
network address of your own SLIP subnet (be sure to change the
|
||||
net mask in the <literal>proto direct</literal> clause as
|
||||
<application>&gated;</application> works correctly for you. You
|
||||
will need to change the <replaceable>xxx.xxx.yy</replaceable>'s
|
||||
into the network address of your own SLIP subnet (be sure to change
|
||||
the net mask in the <literal>proto direct</literal> clause as
|
||||
well).</para>
|
||||
|
||||
<para>Once you have installed and configured
|
||||
|
|
|
|||
Loading…
Reference in a new issue