svn commit: r41456 - in projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook: advanced-networking ppp-and-slip
Dru Lavigne
dru at FreeBSD.org
Thu Apr 18 20:48:00 UTC 2013
Author: dru
Date: Thu Apr 18 20:47:59 2013
New Revision: 41456
URL: http://svnweb.freebsd.org/changeset/doc/41456
Log:
Remove slip, pppd, and 7.x from PPP chapter. This chapter needs to be renamed.
Remove reference to pppd in Advanced Networking chapter.
Approved by: hrs (mentor)
Modified:
projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml
Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
==============================================================================
--- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Apr 18 13:58:37 2013 (r41455)
+++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Apr 18 20:47:59 2013 (r41456)
@@ -4815,10 +4815,9 @@ Received 264951 bytes in 0.1 seconds</sc
<para>A TA will operate basically the same as a modem except
connection and throughput speeds will be much faster than your
- old modem. You will need to configure
- <link linkend="ppp">PPP</link> exactly the same as for a modem
- setup. Make sure you set your serial speed as high as
- possible.</para>
+ old modem. You will need to configure PPP exactly the same as
+ for a modem setup. Make sure you set your serial speed as
+ high as possible.</para>
<indexterm><primary>PPP</primary></indexterm>
<para>The main advantage of using a TA to connect to an Internet
@@ -4835,10 +4834,6 @@ Received 264951 bytes in 0.1 seconds</sc
the same time any problems you experienced with the PPP
program and are going to persist.</para>
- <para>If you want maximum stability, use the kernel
- <link linkend="ppp">PPP</link> option, not the
- <link linkend="userppp">userland PPP</link>.</para>
-
<para>The following TA's are known to work with FreeBSD:</para>
<itemizedlist>
Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml
==============================================================================
--- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Thu Apr 18 13:58:37 2013 (r41455)
+++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Thu Apr 18 20:47:59 2013 (r41456)
@@ -32,7 +32,7 @@
<para>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
+ requires the use of PPP. This chapter describes setting
up these modem-based communication services in detail.</para>
<para>After reading this chapter, you will know:</para>
@@ -42,9 +42,6 @@
<para>How to set up user PPP.</para>
</listitem>
<listitem>
- <para>How to set up kernel PPP (&os; 7.X only).</para>
- </listitem>
- <listitem>
<para>How to set up <acronym>PPPoE</acronym> (PPP over
Ethernet).</para>
</listitem>
@@ -52,10 +49,6 @@
<para>How to set up <acronym>PPPoA</acronym> (PPP over
ATM).</para>
</listitem>
- <listitem>
- <para>How to configure and set up a SLIP client and
- server (&os; 7.X only).</para>
- </listitem>
</itemizedlist>
<indexterm id="ppp-ppp-user">
@@ -79,29 +72,9 @@
</listitem>
<listitem>
<para>Understand the basics and purpose of a dialup connection
- and PPP and/or SLIP.</para>
+ and PPP.</para>
</listitem>
</itemizedlist>
-
- <para>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
- <devicename>tun</devicename> device to communicate with the
- outside world whereas kernel PPP uses the
- <devicename>ppp</devicename> device.</para>
-
- <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>
- (&os; 7.X only). Unless otherwise stated, all of the
- commands explained in this chapter should be executed as
- <username>root</username>.</para>
- </note>
</sect1>
<sect1 id="userppp">
@@ -264,11 +237,9 @@
<secondary>configuration</secondary>
</indexterm>
- <para>Both <command>ppp</command> and <command>pppd</command>
- (the kernel level implementation of PPP, &os; 7.X only)
- use the configuration files located in the <filename
- class="directory">/etc/ppp</filename> directory.
- Examples for user ppp can be found in <filename
+ <para><command>ppp</command> uses the configuration files
+ located in <filename class="directory">/etc/ppp</filename>.
+ Examples can be found in <filename
class="directory">/usr/share/examples/ppp/</filename>.</para>
<para>Configuring <command>ppp</command> requires that you
@@ -1352,505 +1323,6 @@ ifconfig_tun0=</programlisting>
</sect2>
</sect1>
- <sect1 id="ppp">
- <sect1info>
- <authorgroup>
- <author>
- <firstname>Gennady B.</firstname>
- <surname>Sorokopud</surname>
- <contrib>Parts originally contributed by </contrib>
- </author>
- <author>
- <firstname>Robert</firstname>
- <surname>Huff</surname>
- </author>
- </authorgroup>
- </sect1info>
-
- <title>Using Kernel PPP</title>
-
- <warning>
- <para>This section applies and is valid only for
- &os; 7.X.</para>
- </warning>
-
- <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
- <filename class="directory">/usr/sbin</filename> and the
- directory <filename class="directory">/etc/ppp</filename>
- exists.</para>
-
- <para><command>pppd</command> can work in two modes:</para>
-
- <orderedlist>
- <listitem>
- <para>As a <quote>client</quote> — you want to connect
- your machine to the outside world via a PPP serial
- connection or modem line.</para>
- </listitem>
-
- <listitem>
- <indexterm>
- <primary>PPP</primary>
- <secondary>server</secondary>
- </indexterm>
-
- <para>As a <quote>server</quote> — your machine is
- located on the network, and is used to connect other
- computers using PPP.</para>
- </listitem>
- </orderedlist>
-
- <para>In both cases you will need to set up an options file
- (<filename>/etc/ppp/options</filename> or
- <filename>~/.ppprc</filename> if you have more than one user
- on your machine that uses PPP).</para>
-
- <para>You will also need some modem/serial software (preferably
- <filename role="package">comms/kermit</filename>), so you
- can dial and establish a connection with the remote
- host.</para>
- </sect2>
-
- <sect2>
- <sect2info>
- <authorgroup>
- <author>
- <firstname>Trev</firstname>
- <surname>Roydhouse</surname>
- <contrib>Based on information provided by </contrib>
- <!-- Trev.Roydhouse at f401.n711.z3.fidonet.org -->
- </author>
- </authorgroup>
- </sect2info>
-
- <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>
-
- <programlisting>crtscts # enable hardware flow control
-modem # modem control line
-noipdefault # remote PPP server must supply your IP address
- # if the remote host does not send your IP during IPCP
- # negotiation, remove this option
-passive # wait for LCP packets
-domain ppp.foo.com # put your domain name here
-
-:<replaceable>remote_ip</replaceable> # put the IP of remote PPP host here
- # it will be used to route packets via PPP link
- # if you didn't specified the noipdefault option
- # change this line to <replaceable>local_ip</replaceable>:<replaceable>remote_ip</replaceable>
-
-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
- <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>
-
- <step>
- <para>Exit <application>Kermit</application> (without
- hanging up the line).</para>
- </step>
-
- <step>
- <para>Enter the following:</para>
-
- <screen>&prompt.root; <userinput>/usr/sbin/pppd <replaceable>/dev/tty01</replaceable> <replaceable>19200</replaceable></userinput></screen>
-
- <para>Be sure to use the appropriate speed and device
- name.</para>
- </step>
- </procedure>
-
- <para>Now your computer is connected with PPP. If the
- connection fails, you can add the <option>debug</option>
- option to the <filename>/etc/ppp/options</filename> file,
- and check console messages to track the problem.</para>
-
- <para>Following <filename>/etc/ppp/pppup</filename> script will
- make all 3 stages automatic:</para>
-
- <programlisting>#!/bin/sh
-pgrep -l pppd
-pid=`pgrep pppd`
-if [ "X${pid}" != "X" ] ; then
- echo 'killing pppd, PID=' ${pid}
- kill ${pid}
-fi
-pgrep -l kermit
-pid=`pgrep kermit`
-if [ "X${pid}" != "X" ] ; then
- echo 'killing kermit, PID=' ${pid}
- kill -9 ${pid}
-fi
-
-ifconfig ppp0 down
-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>
-
- <para>Use the following <filename>/etc/ppp/pppdown</filename>
- script to disconnect the PPP line:</para>
-
- <programlisting>#!/bin/sh
-pid=`pgrep pppd`
-if [ X${pid} != "X" ] ; then
- echo 'killing pppd, PID=' ${pid}
- kill -TERM ${pid}
-fi
-
-pgrep -l kermit
-pid=`pgrep kermit`
-if [ "X${pid}" != "X" ] ; then
- echo 'killing kermit, PID=' ${pid}
- kill -9 ${pid}
-fi
-
-/sbin/ifconfig ppp0 down
-/sbin/ifconfig ppp0 delete
-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>
-
- <programlisting>#!/bin/sh
-pid=`pgrep pppd`
-if [ X${pid} != "X" ] ; then
- echo 'pppd running: PID=' ${pid-NONE}
-else
- echo 'No pppd running.'
-fi
-set -x
-netstat -n -I ppp0
-ifconfig ppp0</programlisting>
-
- <para>To hang up the modem, execute
- <filename>/etc/ppp/kermit.hup</filename>, which should
- contain:</para>
-
- <programlisting>set line /dev/tty01 ; put your modem device here
-set speed 19200
-set file type binary
-set file names literal
-set win 8
-set rec pack 1024
-set send pack 1024
-set block 3
-set term bytesize 8
-set command bytesize 8
-set flow none
-
-pau 1
-out +++
-inp 5 OK
-out ATH0\13
-echo \13
-exit</programlisting>
-
- <para>Here is an alternate method using <command>chat</command>
- instead of <command>kermit</command>:</para>
-
- <para>The following two files are sufficient to accomplish a
- <command>pppd</command> connection.</para>
-
- <para><filename>/etc/ppp/options</filename>:</para>
-
- <programlisting>/dev/cuad1 115200
-
-crtscts # enable hardware flow control
-modem # modem control line
-connect "/usr/bin/chat -f /etc/ppp/login.chat.script"
-noipdefault # remote PPP serve must supply your IP address
- # if the remote host doesn't send your IP during
- # IPCP negotiation, remove this option
-passive # wait for LCP packets
-domain <replaceable>your.domain</replaceable> # put your domain name here
-
-: # put the IP of remote PPP host here
- # it will be used to route packets via PPP link
- # if you didn't specified the noipdefault option
- # change this line to <replaceable>local_ip</replaceable>:<replaceable>remote_ip</replaceable>
-
-defaultroute # put this if you want that PPP server will be
- # your default router</programlisting>
-
- <para><filename>/etc/ppp/login.chat.script</filename>:</para>
-
- <note>
- <para>The following should go on a single line.</para>
- </note>
-
- <programlisting>ABORT BUSY ABORT 'NO CARRIER' "" AT OK ATDT<replaceable>phone.number</replaceable>
- CONNECT "" TIMEOUT 10 ogin:-\\r-ogin: <replaceable>login-id</replaceable>
- TIMEOUT 5 sword: <replaceable>password</replaceable></programlisting>
-
- <para>Once these are installed and modified correctly, all
- you need to do is run <command>pppd</command>, like so:</para>
-
- <screen>&prompt.root; <userinput>pppd</userinput></screen>
- </sect2>
-
- <sect2>
- <title>Using <command>pppd</command> as a Server</title>
-
- <para><filename>/etc/ppp/options</filename> should contain
- something similar to the following:</para>
-
- <programlisting>crtscts # Hardware flow control
-netmask 255.255.255.0 # netmask (not required)
-192.114.208.20:192.114.208.165 # IP's of local and remote hosts
- # local ip must be different from one
- # you assigned to the Ethernet (or other)
- # interface on your machine.
- # remote IP is IP address that will be
- # assigned to the remote machine
-domain ppp.foo.com # your domain
-passive # wait for LCP
-modem # modem line</programlisting>
-
- <para>The following <filename>/etc/ppp/pppserv</filename> script
- will tell <application>pppd</application> to behave as a
- server:</para>
-
- <programlisting>#!/bin/sh
-pgrep -l pppd
-pid=`pgrep pppd`
-if [ "X${pid}" != "X" ] ; then
- echo 'killing pppd, PID=' ${pid}
- kill ${pid}
-fi
-pgrep -l kermit
-pid=`pgrep kermit`
-if [ "X${pid}" != "X" ] ; then
- echo 'killing kermit, PID=' ${pid}
- kill -9 ${pid}
-fi
-
-# reset ppp interface
-ifconfig ppp0 down
-ifconfig ppp0 delete
-
-# enable autoanswer mode
-kermit -y /etc/ppp/kermit.ans
-
-# run ppp
-pppd /dev/tty01 19200</programlisting>
-
- <para>Use this <filename>/etc/ppp/pppservdown</filename> script
- to stop the server:</para>
-
- <programlisting>#!/bin/sh
-pgrep -l pppd
-pid=`pgrep pppd`
-if [ "X${pid}" != "X" ] ; then
- echo 'killing pppd, PID=' ${pid}
- kill ${pid}
-fi
-pgrep -l kermit
-pid=`pgrep kermit`
-if [ "X${pid}" != "X" ] ; then
- echo 'killing kermit, PID=' ${pid}
- kill -9 ${pid}
-fi
-ifconfig ppp0 down
-ifconfig ppp0 delete
-
-kermit -y /etc/ppp/kermit.noans</programlisting>
-
- <para>The following <application>Kermit</application> script
- (<filename>/etc/ppp/kermit.ans</filename>) will enable/disable
- autoanswer mode on your modem. It should look like
- this:</para>
-
- <programlisting>set line /dev/tty01
-set speed 19200
-set file type binary
-set file names literal
-set win 8
-set rec pack 1024
-set send pack 1024
-set block 3
-set term bytesize 8
-set command bytesize 8
-set flow none
-
-pau 1
-out +++
-inp 5 OK
-out ATH0\13
-inp 5 OK
-echo \13
-out ATS0=1\13 ; change this to out ATS0=0\13 if you want to disable
- ; autoanswer mode
-inp 5 OK
-echo \13
-exit</programlisting>
-
- <para>A script named <filename>/etc/ppp/kermit.dial</filename>
- is used for dialing and authenticating on the remote host.
- You will need to customize it for your needs. Put your login
- and password in this script; you will also need to change the
- input statement depending on responses from your modem and
- remote host.</para>
-
- <programlisting>;
-; put the com line attached to the modem here:
-;
-set line /dev/tty01
-;
-; put the modem speed here:
-;
-set speed 19200
-set file type binary ; full 8 bit file xfer
-set file names literal
-set win 8
-set rec pack 1024
-set send pack 1024
-set block 3
-set term bytesize 8
-set command bytesize 8
-set flow none
-set modem hayes
-set dial hangup off
-set carrier auto ; Then SET CARRIER if necessary,
-set dial display on ; Then SET DIAL if necessary,
-set input echo on
-set input timeout proceed
-set input case ignore
-def \%x 0 ; login prompt counter
-goto slhup
-
-:slcmd ; put the modem in command mode
-echo Put the modem in command mode.
-clear ; Clear unread characters from input buffer
-pause 1
-output +++ ; hayes escape sequence
-input 1 OK\13\10 ; wait for OK
-if success goto slhup
-output \13
-pause 1
-output at\13
-input 1 OK\13\10
-if fail goto slcmd ; if modem doesn't answer OK, try again
-
-:slhup ; hang up the phone
-clear ; Clear unread characters from input buffer
-pause 1
-echo Hanging up the phone.
-output ath0\13 ; hayes command for on hook
-input 2 OK\13\10
-if fail goto slcmd ; if no OK answer, put modem in command mode
-
-:sldial ; dial the number
-pause 1
-echo Dialing.
-output atdt9,550311\13\10 ; put phone number here
-assign \%x 0 ; zero the time counter
-
-:look
-clear ; Clear unread characters from input buffer
-increment \%x ; Count the seconds
-input 1 {CONNECT }
-if success goto sllogin
-reinput 1 {NO CARRIER\13\10}
-if success goto sldial
-reinput 1 {NO DIALTONE\13\10}
-if success goto slnodial
-reinput 1 {\255}
-if success goto slhup
-reinput 1 {\127}
-if success goto slhup
-if < \%x 60 goto look
-else goto slhup
-
-:sllogin ; login
-assign \%x 0 ; zero the time counter
-pause 1
-echo Looking for login prompt.
-
-:slloop
-increment \%x ; Count the seconds
-clear ; Clear unread characters from input buffer
-output \13
-;
-; put your expected login prompt here:
-;
-input 1 {Username: }
-if success goto sluid
-reinput 1 {\255}
-if success goto slhup
-reinput 1 {\127}
-if success goto slhup
-if < \%x 10 goto slloop ; try 10 times to get a login prompt
-else goto slhup ; hang up and start again if 10 failures
-
-:sluid
-;
-; put your userid here:
-;
-output ppp-login\13
-input 1 {Password: }
-;
-; put your password here:
-;
-output ppp-password\13
-input 1 {Entering SLIP mode.}
-echo
-quit
-
-:slnodial
-echo \7No dialtone. Check the telephone line!\7
-exit 1
-
-; local variables:
-; mode: csh
-; comment-start: "; "
-; comment-start-skip: "; "
-; end:</programlisting>
- </sect2>
- </sect1>
-
<sect1 id="ppp-troubleshoot">
<sect1info>
<authorgroup>
@@ -2559,760 +2031,4 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNI
<filename>/var/log/ppp.log</filename> for clues.</para>
</sect2>
</sect1>
-
- <sect1 id="slip">
- <sect1info>
- <authorgroup>
- <author>
- <firstname>Satoshi</firstname>
- <surname>Asami</surname>
- <contrib>Originally contributed by </contrib>
- </author>
- </authorgroup>
- <authorgroup>
- <author>
- <firstname>Guy</firstname>
- <surname>Helmer</surname>
- <contrib>With input from </contrib>
- </author>
- <author>
- <firstname>Piero</firstname>
- <surname>Serini</surname>
- </author>
- </authorgroup>
- </sect1info>
-
- <title>Using SLIP</title>
-
- <indexterm><primary>SLIP</primary></indexterm>
-
- <warning>
- <para>This section applies and is valid only for
- &os; 7.X.</para>
- </warning>
-
- <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 (your address changes each time you dial up), you
- probably need to have a more complex setup.</para>
-
- <para>First, determine which serial port your modem is connected
- to. Many people set up a symbolic link, such as
- <filename class="devicefile">/dev/modem</filename>, to point
- to the real device name, <filename
- class="devicefile">/dev/cuad<replaceable>N</replaceable></filename>.
- 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 class="directory">/etc</filename> and
- <filename>.kermrc</filename> files all over the system!</para>
-
- <note>
- <para><filename class="devicefile">/dev/cuad0</filename>
- is <devicename>COM1</devicename>, <filename
- class="devicefile">/dev/cuad1</filename> is
- <devicename>COM2</devicename>, etc.</para>
- </note>
-
- <para>Make sure you have the following in your kernel
- configuration file:</para>
-
- <programlisting>device sl</programlisting>
-
- <para>It is included in the <filename>GENERIC</filename> kernel,
- so this should not be a problem unless you have deleted
- it.</para>
-
- <sect3>
- <title>Things You Have to Do Only Once</title>
-
- <procedure>
- <step>
- <para>Add your home machine, the gateway and nameservers
- to your <filename>/etc/hosts</filename> file. Ours
- looks like this:</para>
-
- <programlisting>127.0.0.1 localhost loghost
-136.152.64.181 water.CS.Example.EDU water.CS water
-136.152.64.1 inr-3.CS.Example.EDU inr-3 slip-gateway
-128.32.136.9 ns1.Example.EDU ns1
-128.32.136.12 ns2.Example.EDU ns2</programlisting>
- </step>
-
- <step>
- <para>Make sure you have <literal>files</literal> before
- <literal>dns</literal> in the <literal>hosts:</literal>
- section of your <filename>/etc/nsswitch.conf</filename>
- file. Without these parameters funny things may
- happen.</para>
- </step>
-
- <step>
- <para>Edit the <filename>/etc/rc.conf</filename>
- file.</para>
-
- <orderedlist>
- <listitem>
- <para>Set your hostname by editing the line that
- says:</para>
-
- <programlisting>hostname="myname.my.domain"</programlisting>
-
- <para>Your machine's full Internet hostname should be
- placed here.</para>
- </listitem>
-
- <listitem>
- <indexterm><primary>default
- route</primary></indexterm>
-
- <para>Designate the default router by changing the
- line:</para>
-
- <programlisting>defaultrouter="NO"</programlisting>
-
- <para>to:</para>
-
- <programlisting>defaultrouter="slip-gateway"</programlisting>
- </listitem>
- </orderedlist>
- </step>
-
- <step>
- <para>Make a file <filename>/etc/resolv.conf</filename>
- which contains:</para>
-
- <programlisting>domain CS.Example.EDU
-nameserver 128.32.136.9
-nameserver 128.32.136.12</programlisting>
-
- <indexterm><primary>nameserver</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>
- </step>
-
- <step>
- <para>Set the password for <username>root</username> and
- <username>toor</username> (and any other
- accounts that do not have a password).</para>
- </step>
-
- <step>
- <para>Reboot your machine and make sure it comes up with
- the correct hostname.</para>
- </step>
- </procedure>
- </sect3>
-
- <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,
- 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>
-
- <programlisting># kermit setup
-set modem hayes
-set line /dev/modem
-set speed 115200
-set parity none
-set flow rts/cts
-set terminal bytesize 8
-set file type binary
-# The next macro will dial up and login
-define slip dial 643-9600, input 10 =>, if failure stop, -
-output slip\x0d, input 10 Username:, if failure stop, -
-output silvia\x0d, input 10 Password:, if failure stop, -
-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>
-
- <note>
- <para>Leaving your password in plain text anywhere in
- the filesystem is generally a <emphasis>bad</emphasis>
- idea. Do it at your own risk.</para>
- </note>
- </step>
-
- <step>
- <para>Leave the <application>Kermit</application> there
- (you can suspend it by
- <keycombo>
- <keycap>Ctrl</keycap>
- <keycap>z</keycap>
- </keycombo>) and as <username>root</username>,
- type:</para>
-
- <screen>&prompt.root; <userinput>slattach -h -c -s 115200 /dev/modem</userinput></screen>
-
- <para>If you are able to <command>ping</command> hosts
- on the other side of the router, you are connected!
- If it does not work, you might want to try
- <option>-a</option> instead of <option>-c</option> as
- an argument to <command>slattach</command>.</para>
- </step>
- </procedure>
- </sect3>
-
- <sect3>
- <title>How to Shutdown the Connection</title>
-
- <para>Do the following:</para>
-
- <screen>&prompt.root; <userinput>kill -INT `cat /var/run/slattach.modem.pid`</userinput></screen>
-
- <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>
-
- <para>The &man.slattach.8; manual page says you have to use
- <command>ifconfig sl0 down</command> to mark the interface
- down, but this does not seem to make any difference.
- (<command>ifconfig sl0</command> reports the same
- thing.)</para>
-
- <para>Some times, your modem might refuse to drop the carrier.
- In that case, simply start <command>kermit</command> and
- quit it again. It usually goes out on the second
- try.</para>
- </sect3>
-
- <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>
-
- <itemizedlist>
- <listitem>
- <para>Not using <option>-c</option> or <option>-a</option>
- in <command>slattach</command> (This should not be
- fatal, but some users have reported that this solves
- their problems.)</para>
- </listitem>
-
- <listitem>
- <para>Using <option>s10</option> instead of
- <option>sl0</option> (might be hard to see the
- difference on some fonts).</para>
- </listitem>
-
- <listitem>
- <para>Try <command>ifconfig sl0</command> to see your
- interface status. For example, you might get:</para>
-
- <screen>&prompt.root; <userinput>ifconfig sl0</userinput>
-sl0: flags=10<POINTOPOINT>
- inet 136.152.64.181 --> 136.152.64.1 netmask ffffff00</screen>
- </listitem>
-
- <listitem>
- <para>If you get <errorname>no route to host</errorname>
- messages from &man.ping.8;, 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
-Destination Gateway Flags Refs Use IfaceMTU Rtt Netmasks:
-
-(root node)
-(root node)
-
-Route Tree for Protocol Family inet:
-(root node) =>
-default inr-3.Example.EDU UG 8 224515 sl0 - -
-localhost.Exampl localhost.Example. UH 5 42127 lo0 - 0.438
-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>The preceding examples are from a relatively busy
- system. The numbers on your system will vary depending
- on network activity.</para>
-
- </listitem>
- </itemizedlist>
- </sect3>
- </sect2>
-
- <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 your system to automatically start up connections
- upon login for remote SLIP clients.</para>
-
- <!-- Disclaimer is not necessarily relevant
- <para> The author has written this document based
- on his experience; however, as your system and needs may be
- different, this document may not answer all of your questions, and
- the author cannot be responsible if you damage your system or lose
- data due to attempting to follow the suggestions here.</para>
- -->
-
- <sect3 id="slips-prereqs">
- <title>Prerequisites</title>
-
- <indexterm><primary>TCP/IP networking</primary></indexterm>
- <para>This section 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 addressing, network address masks, subnetting,
- routing, and routing protocols, such as RIP. Configuring
- SLIP services on a dial-up server requires a knowledge of
- these concepts, and if you are not familiar with them,
- please read a copy of either Craig Hunt's <emphasis>TCP/IP
- Network Administration</emphasis> published by O'Reilly
- & Associates, Inc. (ISBN Number 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 set up your
- modem(s) and configured the appropriate system files to
- allow logins through your modems. If you have not prepared
- your system for this yet, please see <xref
- linkend="dialup"/> for details on dialup services
- configuration. You may also want to check the manual pages
- or &man.sio.4; for information on the serial port device
- driver and &man.ttys.5;, &man.gettytab.5;, &man.getty.8;,
- & &man.init.8; for information relevant to configuring
- the system to accept logins on modems, and perhaps
- &man.stty.1; for information on setting serial port
- parameters (such as <literal>clocal</literal> for
- directly-connected serial interfaces).</para>
- </sect3>
-
- <sect3>
- <title>Quick Overview</title>
-
- <para>In its typical configuration, using FreeBSD as a SLIP
- server works as follows: a SLIP user dials up your FreeBSD
- SLIP Server system and logs in with a special SLIP login
- ID that uses <filename>/usr/sbin/sliplogin</filename> as
- the special user's shell. The <command>sliplogin</command>
- program browses the file
- <filename>/etc/sliphome/slip.hosts</filename> to find a
- matching line for the special user, and if it finds a match,
- connects the serial line to an available SLIP interface and
- then runs the shell script
- <filename>/etc/sliphome/slip.login</filename> to configure
- the SLIP interface.</para>
-
- <sect4>
- <title>An Example of a SLIP Server Login</title>
-
- <para>For example, if a SLIP user ID were
- <username>Shelmerg</username>,
- <username>Shelmerg</username>'s entry in
- <filename>/etc/master.passwd</filename> would look
- something like this:</para>
-
- <programlisting>Shelmerg:password:1964:89::0:0:Guy Helmer - SLIP:/usr/users/Shelmerg:/usr/sbin/sliplogin</programlisting>
-
- <para>When <username>Shelmerg</username> logs in,
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-projects
mailing list