Technical article 109485

How to manually configure SCO PPP for incoming/outgoing connections.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5

Written · Last revised

Problem

How do I manually configure SCO PPP for incoming and/or outgoing
connections on my SCO server?  Although this can be done easily
through /usr/bin/pppconf, it is sometimes more expeditious to do
the configuration manually.
NOTE:     This article is divided into several parts.  Note that this article
          assumes you have working modems on both systems.

Solution

Follow these steps:
CONFIGURE PPP DRIVER:
You must first configure the ppp driver into the kernel if it
isn't already there.  To do this, enter:
SCOAdmin-->Networks-->Network Configuration Manager
and then:

Select Hardware-->Add New WAN Connection-->SCO TCP/IP driver--> SCO TCP/IP-->Add

You can now configure a Dynamic Outgoing, Dynamic Incoming, Dedicated, or Manual Outgoing link with the screens presented. The screens you see here are the same screens you will see if you run /usr/bin/pppconf.

Or, you can choose "Cancel" and "OK", exit the Network
Configuration Manager, relink, and reboot.  Note that you must
relink and reboot the system after installing the PPP driver.

You are now ready to configure your PPP link.

CONFIGURE UUCP FILES:

For any outgoing link, you need two basic files configured.

You should already have valid and working entries in /usr/lib/uucp/Devices for the modem(s) you plan to use for PPP. If not, see other articles in this database on installing, configuring, and testing modems.

Then, you need /usr/lib/uucp/Systems.  A typical Systems file
entry looks something like this:
ppp-isp Any  ACU 38400 6614900 \K\d-in:-\K\d-in: craigd ssword: craigd123
Note that this is one contiguous line which sometimes wraps around.
The name "ppp-isp" will refer to an entry in /etc/ppphosts.  "Any
ACU 38400" are standard Systems entries which indicate time of day
to call, the tag to refer to in the Devices file, and the speed to
use for the connection.  The rest of the line is the "chat script"
used to log in to the remote system.
CONFIGURE PPP FILES:
There is one main PPP configuration file, /etc/ppphosts, which
gets created when the PPP driver is installed in the kernel.  This
file will have different fields and parameters depending on what
type of connection you are trying to configure:
Dynamic Outgoing            link bringup occurs whenever there
                            is TCP/IP routed through the PPP
                            interface
Manual Outgoing             link is brought up only when the
                            pppattach(ADMN) command is run on
                            the local machine
Dynamic Incoming            link is brought up when a remote
                            machine logs in via UUCP and the
                            PPP shell is executed
Dedicated                   no modems involved, straight serial
                            connection, link is brought up
                            dynamically
Note that there is a difference between dynamic bringup and
dynamic address assignment.  Dynamic bringup refers to how the
link is activated; dynamic addressing refers to whether or not
you know your IP addresses before the link is activated.

Here are example /etc/ppphosts entries for each of these connection types:

Dynamic outbound PPP connection:
ppp-isp:ppp-local uucp=ppp-isp idle=5 debug=2
where "ppp-isp:ppp-local" refers to entries in /etc/hosts.  If
you are not using /etc/hosts entries, you can use IP addresses
here, with the format "remote:local".  The "uucp=ppp-isp" is what
refers to correct entry in /usr/lib/uucp/Systems.  The "idle" and
"debug" parameters are optional -- as are most PPP configuration
options. More information on those can be found in the
/etc/ppphosts file itself or the ppphosts(SFF) manual page.
Manual outbound PPP connection:
0.0.0.0:0.0.0.0 uucp=ppp-isp attach=ppp-isp conf=10 debug=2
Here, we don't know the remote and local IP addresses until after
we connect to the ISP, so we specify 0.0.0.0 for both.  In this
case, we must use the command "pppattach ppp-isp" to manually
start the PPP bringup.  Note that the attachname can be any name
or token, but the "attach=" entry should be on the first line of
the entry in /etc/ppphosts for this link.
Dynamic inbound PPP connection:
  *nppp idle=1 conf=10 nak=10 mru=1500 noipaddr
local=128.212.33.10 remote=128.212.33.90
You must create an "nppp" account, either manually or through the
SCOadmin Account Manager.  Make sure the new account uses the
/usr/lib/ppp/ppp shell.  The "*nppp" is the indicator, in this
case, that the link is incoming and not outgoing.  Anytime the
nppp user logs in, the rest of the parameters on the line will be
used in the PPP negotiation.
Dedicated PPP connection:
  128.212.33.10:128.212.33.90 staticdev=tty1a
term=2 nak=10 mru=296 accm=A0000 auth=pap

The main difference here is that there is no reference to UUCP; rather, we have a "staticdev=tty1a" which tells the PPP driver to use that tty for all communication with the remote end.

Take care and consideration in deciding which link options to
include in your /etc/ppphosts entries.  Some options are not
necessary, some are not going to be understood by the remote
server, and some may actually hinder your PPP performance.  It
is usually wise to start with a minimal set of options (IP
addresses, UUCP name, debug value) and add on from there as
necessary.

See also

man page ppphosts(SFF)

For troubleshooting information, see other articles in this database.

From the Xinuos technical article database, record 109485. Reproduced with permission. The original is at www.sco.com/ta/109485, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.