Technical article 105253

How to configure PPP for bi-directional dynamic bring up with OpenServer 5?

OpenServer 5.0.0

Written · Last revised

Problem

I am having difficulties configuring dynamic bring up, bi-directional PPP.

NOTE:     The IP addresses used in this TA are for example
          purposes only.

Solution

Dynamic bring up; Static IP assignment:

Sample configuration of two SCO OpenServer 5.0 servers with a single ppp connection. Either of the hosts have the ability to initiate the PPP session. Bi-directional communications can occur once the link is established.

                       .
                       .
                       .
                       .
                       |
       133.133.144     |
<----------------------|------------>
                  |
_______________   |                                    _______________
|             |   |                                    |             |
|             |   |                                    |             |
|         wdn0|---|                                    |             |
|             |                                        |             |
|             |      ___                    ___        |             |
|             |     |   |                  |   |       |             |
|  ppp0 / COM1|-----|   |------/\/\/\------|   |-------|ppp0 / COM1  |
|             |     +___+                  +___+       |             |
+_____________+                                        +_____________+
yosemite          Modem                  Modem       zion
Rel 5.0.0                                            Rel 5.0.0
Rel Supp 5.0.0d                                      Rel Supp 5.0.0d
net100                                               net100
133.133.144.19 ppp0                                  133.133.144.12 ppp0
133.133.144.30 wdn0
+++++++++++++++++++++++++++++++++
Config on zion (133.133.144.12)
+++++++++++++++++++++++++++++++++
1a)
During boot up,  if a /etc/ppphosts file exists, the pppd daemons are
started:
   /etc/ppphosts
   lrwxrwxrwx   1 root     sys           39 Sep 16 20:43 /etc/ppphosts ->
/var/opt/K/SCO/tcp/2.0.0Cl/etc/ppphosts
   #      @(#)ppphosts  6.17 11/29/94 - STREAMware TCP/IP  source
   ##################################################################
   # Dynamic Bring Up incoming with static IP's
   *nppp local=133.133.144.12 remote=133.133.144.19 flow=rtscts
mask=255.255.255.0
   # Dynamic Bring Up outbound with static IP's
   133.133.144.19:133.133.144.12 uucp=yosemite flow=rtscts mask=255.255.255.0
Note: It may be necessary to insert debug=[0-2] in the /etc/ppphosts file
for trouble shooting purposes.  Reference the man page for ppphosts for
information on other parameters that may be set in the /etc/ppphosts file.
1b)

Your routing table should be similar to:

netstat -rn
Routing tables
Destination      Gateway            Flags    Refs      Use  Interface
127.0.0.1        127.0.0.1          UH          2        8  lo0
133.133.144.12   127.0.0.1          UGHS        0        0  lo0
133.133.144.19   133.133.144.12     UH          2        1  ppp0
1c)
/etc/passwd should contain the following or some equivalent
nppp:x:200:50:PPP Login:/usr/lib/ppp:/usr/lib/ppp/ppp
1d)

/usr/lib/uucp/Systems This entry affords connection to the remote (133.133.144.19) host

yosemite Any ACU 38400 <ph#> -\r\d-ogin:-\K\d-ogin:-\K\d-ogin: nppp ssword: test1

1e)
/usr/lib/uucp/Devices
ACU tty1A - 38400 atdialUSR14.4

Note: The dialer should be appropriate for your modem.

1f)
/etc/inittab                 : 'o' is port speed of 38400
Se1A:234:respawn:/etc/getty -t60 tty1A o

Note: It may be necessary for the 'connect'/port speed to be identical on both system configurations.

++++++++++++++++++++++++++++++++++++++++
Configuration on yosemite (133.133.144.19)
++++++++++++++++++++++++++++++++++++++++
2a)
/etc/ppphosts
##################################################################
*nppp local=133.133.144.19 remote=133.133.144.12 mask=255.255.255.0 \
flow=rtscts proxy
133.133.144.12:133.133.144.19 uucp=pppout mask=255.255.255.0 flow=rtscts \
proxy
2b)
netstat -rn
Routing tables
Destination      Gateway            Flags    Refs      Use  Interface
127.0.0.1        127.0.0.1          UH          6       54  lo0
133.133.144      133.133.144.30     UC          1        0  net0
133.133.144.12   133.133.144.19     UH          3      107  ppp0
133.133.144.19   127.0.0.1          UGHS        0        0  lo0
133.133.144.30   127.0.0.1          UGHS        4      106  lo0
224              133.133.144.30     UCS         0        0  net0
2c)
arp -a

? (133.133.144.12) at 10:0:5a:82:a5:4c (802.3) permanent published (proxy only) ? (133.133.144.19) at 10:0:5a:82:a5:4c (802.3) permanent published (proxy only)

Note: To minimize the potential for a broadcast to bring up the ppp link, consider assigning a separate subnet to the ppp portion of the network.

2d)
/etc/passwd
nppp:x:12231:50::/usr/lib/ppp:/usr/lib/ppp/ppp
2e)
/usr/lib/uucp/Devices
ACU tty1A - 38400 atdialUSR14.4
2f)
/usr/lib/uucp/Systems

pppout Any ACU 38400 <ph#> -\r\d-ogin:-\K\d-ogin:-\K\d-ogin: nppp ssword: test1

2g)
/etc/inittab                 : 'o' is port speed of 38400
Se1A:234:off:/etc/getty -t60 tty1A o

From the Xinuos technical article database, record 105253. Reproduced with permission. The original is at www.sco.com/ta/105253, 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.