Remove the manual connection section which I added long ago. This will come
back, after some work, as a troubleshooting modem problems/connection problems section. Sponcered by: FreeBSDMall Inc.
This commit is contained in:
Tom Rhodes
parent
93e9c2e4c7
commit
69c86ce83e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=17155
1 changed files with 0 additions and 253 deletions
|
|
@ -246,259 +246,6 @@
|
|||
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Manual <command>ppp</command> Initialization</title>
|
||||
|
||||
<para>Under normal circumstances, most users will only use one
|
||||
<devicename>tun</devicename> device
|
||||
(<devicename>/dev/tun0</devicename>). References to
|
||||
<devicename>tun0</devicename> below may be changed to
|
||||
<devicename>tunN</devicename> where <literal>N</literal>
|
||||
is any unit number corresponding to your system.</para>
|
||||
|
||||
<para>For FreeBSD installations that do not have &man.devfs.5; enabled (FreeBSD 4.X and earlier),
|
||||
the existence of the <devicename>tun0</devicename> device should
|
||||
be verified (this is not necessary if &man.devfs.5; is enabled as device
|
||||
nodes will be created on demand).</para>
|
||||
|
||||
<para>The easiest way to make sure that the
|
||||
<devicename>tun0</devicename> device is configured correctly
|
||||
is to remake the device. To remake the device, do the
|
||||
following:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /dev</userinput>
|
||||
&prompt.root; <userinput>sh MAKEDEV tun0</userinput></screen>
|
||||
|
||||
<para>If you need 16 tunnel devices in your kernel, you will need
|
||||
to create them. This can be done by executing the following
|
||||
commands:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /dev</userinput>
|
||||
&prompt.root; <userinput>sh MAKEDEV tun15</userinput></screen>
|
||||
|
||||
<sect4>
|
||||
<title>Check the Modem</title>
|
||||
<para>If you reconfigured your <filename>kernel</filename>
|
||||
then you recall the <devicename>sio</devicename>
|
||||
device. If your modem acts like a standard serial port
|
||||
then you most likely only need to make the serial device.
|
||||
You can do this by changing your directory to
|
||||
<filename>/dev</filename> and running the <filename>MAKEDEV</filename>
|
||||
script like above. Now make the serial devices with
|
||||
<screen>&prompt.root; <userinput>sh MAKEDEV cuaa0 cuaa1 cuaa2 cuaa3</userinput></screen>
|
||||
which will create the serial devices for your system.
|
||||
If your modem is on <devicename>sio1</devicename> or
|
||||
<acronym>COM2</acronym> if you are in DOS, then your
|
||||
modem device would be <devicename>/dev/cuaa1</devicename>.
|
||||
</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Manual Connections</title>
|
||||
<para>Connecting to the Internet by manually controlling
|
||||
<command>ppp</command> is quick, easy, and a great way
|
||||
to debug a connection or just get information on how your
|
||||
<acronym>ISP</acronym> handles connections. Lets start
|
||||
<application>PPP</application> from the command line,
|
||||
note that, in all of our examples we will use <emphasis>example</emphasis>
|
||||
as the hostname of the machine running <application>PPP</application>.
|
||||
You start <command>ppp</command> by just typing <command>ppp</command>:
|
||||
|
||||
<screen>&prompt.root; <userinput>ppp</userinput></screen>
|
||||
|
||||
<para>We have now started <command>ppp</command>.</para>
|
||||
|
||||
<screen>ppp ON example> <userinput>set device <devicename>/dev/cuaa1</devicename></userinput></screen>
|
||||
|
||||
<para>We set our modem device, in this case it is
|
||||
<devicename>cuaa1</devicename>.</para>
|
||||
|
||||
<screen>ppp ON example> <userinput>set speed 115200</userinput></screen>
|
||||
|
||||
<para>Set the connection speed, in this case we
|
||||
are using 115,200 <acronym>kbps</acronym>.</para>
|
||||
|
||||
<screen>ppp ON example> <userinput>enable dns</userinput></screen>
|
||||
|
||||
<para>Tell <command>ppp</command> to configure our
|
||||
resolver and add the nameserver lines to
|
||||
<filename>/etc/resolv.conf</filename>. If <command>ppp</command>
|
||||
cannot determine our hostname, we can set one manually later.
|
||||
</para>
|
||||
|
||||
<screen>ppp ON example> <userinput>term</userinput></screen>
|
||||
|
||||
<para>Switch to <quote>terminal</quote> mode so that we can manually
|
||||
control the modem.</para>
|
||||
|
||||
<programlisting>
|
||||
deflink: Entering terminal mode on <devicename>/dev/cuaa1</devicename>
|
||||
type '~h' for help</programlisting>
|
||||
|
||||
<screen><userinput>at</userinput>
|
||||
OK
|
||||
<userinput>atdt<replaceable>123456789</replaceable></userinput></screen>
|
||||
|
||||
<para>Use <command>at</command> to initialize the modem,
|
||||
then use <command>atdt</command> and the number for your
|
||||
<acronym>ISP</acronym> to begin the dial in process.</para>
|
||||
|
||||
<screen>CONNECT</screen>
|
||||
|
||||
<para>Confirmation of the connection, if we are going to have
|
||||
any connection problems, unrelated to hardware, here is where
|
||||
we will attempt to resolve them.</para>
|
||||
|
||||
<screen>ISP Login:<userinput>myusername</userinput></screen>
|
||||
|
||||
<para>Here you are prompted for a username, return the
|
||||
prompt with the username that was provided by the
|
||||
<acronym>ISP</acronym>.</para>
|
||||
|
||||
<screen>ISP Pass:<userinput>mypassword</userinput></screen>
|
||||
|
||||
<para>This time we are prompted for a password, just
|
||||
reply with the password that was provided by the
|
||||
<acronym>ISP</acronym>. Just like when logging into
|
||||
FreeBSD, the password will not echo.</para>
|
||||
|
||||
<screen>Shell or PPP:<userinput>ppp</userinput></screen>
|
||||
|
||||
<para>Depending on your <acronym>ISP</acronym> this prompt
|
||||
may never appear. Here we are being asked if we wish to
|
||||
use a shell on the provider, or to start
|
||||
<command>ppp</command>. In this example, we have chosen
|
||||
to use <command>ppp</command> as we want an Internet
|
||||
connection.</para>
|
||||
|
||||
<screen>Ppp ON example></screen>
|
||||
|
||||
<para>Notice that in this example the first <option>p</option>
|
||||
has been capitalized. This shows that we have successfully
|
||||
connected to the <acronym>ISP</acronym>.</para>
|
||||
|
||||
<screen>PPp ON example></screen>
|
||||
|
||||
<para>We have successfully authenticated with our
|
||||
<acronym>ISP</acronym> and are waiting for the
|
||||
assigned <acronym>IP</acronym> address.</para>
|
||||
|
||||
<screen>PPP ON example></screen>
|
||||
|
||||
<para>We have made an agreement on an <acronym>IP</acronym>
|
||||
address and successfully completed our connection.</para>
|
||||
|
||||
<screen>PPP ON example><userinput>add default HISADDR</userinput></screen>
|
||||
|
||||
<para>Here we add our default route, we need to do this
|
||||
before we can talk to the outside world as currently the
|
||||
only established connection is with the peer. If this
|
||||
fails due to existing routes you can put a bang character
|
||||
<literal>!</literal> in front of the <option>add</option>.
|
||||
Alternatively, you can set this before making the actual connection
|
||||
and it will negotiate a new route accordingly.</para>
|
||||
|
||||
<para>If everything went good we should now have an active
|
||||
connection to the Internet, which could be thrown into
|
||||
the background using
|
||||
<keycombo action="simul"><keycap>CTRL</keycap> <keycap>z</keycap></keycombo>
|
||||
If you notice the <command>PPP</command> return to
|
||||
<command>ppp</command> then we have lost our connection.
|
||||
This is good to know because it shows our connection status.
|
||||
Capital P's show that we have a connection to the
|
||||
<acronym>ISP</acronym> and lowercase p's show that the
|
||||
connection has been lost for whatever reason.
|
||||
<command>ppp</command> only has these 2 states.
|
||||
</para>
|
||||
|
||||
<sect4>
|
||||
<title>Troubleshooting Manual Connections</title>
|
||||
<para>Like everything else, once in awhile a problem or
|
||||
may occur. <application>PPP</application> is no
|
||||
exemption to this theory. If <command>ppp</command>
|
||||
would happen to stop responding there are some things
|
||||
we can try.</para>
|
||||
|
||||
<para>If you have a direct line and cannot seem to make a
|
||||
connection, then turn hardware flow <acronym>CTS/RTS</acronym>
|
||||
to off with the <option>set ctsrts off</option>. This is
|
||||
mainly the case if you are connected to some
|
||||
<application>PPP</application> capable terminal servers,
|
||||
where <application>PPP</application> hangs when it tries
|
||||
to write data to your communication link, so it
|
||||
would be waiting for a <acronym>CTS</acronym>, or Clear
|
||||
To Send signal which may never come. If you use this
|
||||
option however, you should also use the <option>set accmap</option>
|
||||
option, which may be required to defeat hardware dependent on
|
||||
passing certain characters from end to end, most of the time
|
||||
XON/XOFF. See the &man.ppp.8; manual page for more information
|
||||
on this option, and how it is used.</para>
|
||||
|
||||
<para>If you have an older modem, you may need to use the
|
||||
<option>set parity even</option>. Parity is set at none
|
||||
be default, but is used for error checking (with a large
|
||||
increase in traffic) on older modems and some
|
||||
<acronym>ISP</acronym>s. You may need this option for
|
||||
the Compuserve ISP.</para>
|
||||
|
||||
<para><application>PPP</application> may not return to the
|
||||
command mode, which is usually a negotiation error where
|
||||
the <acronym>ISP</acronym> is waiting for your side to start
|
||||
negotiating. At this point, using the <command>~p</command>
|
||||
command will force ppp to start sending the configuration
|
||||
information.</para>
|
||||
|
||||
<para>If you never obtain a login prompt, then most likely you
|
||||
need to use <acronym>PAP</acronym> or <acronym>CHAP</acronym>
|
||||
authentication instead of the Unix-style in the example above. To
|
||||
use <acronym>PAP</acronym> or <acronym>CHAP</acronym> just add the
|
||||
following options to <application>PPP</application> before going
|
||||
into terminal mode:</para>
|
||||
|
||||
<screen>ppp ON example> <userinput>set authname <replaceable>myusername</replaceable></userinput></screen>
|
||||
|
||||
<para>Where <replaceable>myusername</replaceable> should be replaced with
|
||||
the username that was assigned by the <acronym>ISP</acronym>.</para>
|
||||
|
||||
<screen>ppp ON example> <userinput>set authkey <replaceable>mypassword</replaceable></userinput></screen>
|
||||
|
||||
<para>Where <replaceable>mypassword</replaceable> should be replaced with
|
||||
the password that was assigned by the <acronym>ISP</acronym>.</para>
|
||||
|
||||
<para>If you connect fine, but cannot seem to find any domain name, try to
|
||||
use &man.ping.8; with an <acronym>IP</acronym> address and see if you
|
||||
can get any return information. If you experience 100 percent (100%)
|
||||
packet loss, then its most likely that you were not assigned a default
|
||||
route. Double check that the option <option>add default HISADDR</option>
|
||||
was set during the connection. If you can connect to a remote
|
||||
<acronym>IP</acronym> address then it is possible that a resolver address
|
||||
has not been added to the <filename>/etc/resolv.conf</filename>. This
|
||||
file should look like:</para>
|
||||
|
||||
<programlisting>domain <replaceable>example.com</replaceable>
|
||||
nameserver <replaceable>x.x.x.x</replaceable>
|
||||
nameserver <replaceable>y.y.y.y</replaceable></programlisting>
|
||||
|
||||
<para>Where <replaceable>x.x.x.x</replaceable> and
|
||||
<replaceable>y.y.y.y</replaceable> should be replaced with the
|
||||
<acronym>IP</acronym> address of your <acronym>ISP</acronym>'s DNS servers.
|
||||
This information may or may not have been provided when you signed up, but
|
||||
a quick call to your <acronym>ISP</acronym> should remedy that.</para>
|
||||
|
||||
<para>You could also have &man.syslog.3; provide a logging function
|
||||
for your <application>PPP</application> connection. Just add:</para>
|
||||
|
||||
<programlisting>
|
||||
!ppp
|
||||
*.* /var/log/ppp.log</programlisting>
|
||||
|
||||
<para>to <filename>/etc/syslog.conf</filename>. In most cases, this
|
||||
functionality already exists.</para>
|
||||
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Automatic <application>PPP</application> Configuration</title>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue