🚀 go-pugleaf

(This problem is different than the one resolved in January 1993 under
SCO reference number 551407, which resulted in SCO SLS net363.)

When running PPP or SLIP links under SCO TCP/IP v1.2.1o, the IP
address of the local end of a point-to-point link may not be on the
same network number or subnet as the IP address of any other interface
on the same system (e.g. an Ethernet interface).  Ken in SCO's tech
support group (+1 408 427 6823) suggests the work-around of changing
the local end of the point-to-point link to be on a different network
or subnet number than that used on any other interface.  Basically,
they're saying that SCO TCP 1.2.1o no longer supports the idea of
un-numbered interfaces.

For example, under SCO TCP 1.1.3f, SCO TCP 1.2 plus net363, and SCO
TCP 1.2.1 up through 1.2.1l, you used to be able to say

# ifconfig wdn0
wdn0: flags=23<UP,BROADCAST,NOTRAILERS>
        inet 137.175.2.28 netmask ffffff00 broadcast 137.175.2.255
# netstat -ina
Name   Mtu   Network     Address       Ipkts   Ierrs Opkts   Oerrs Collis
wdn0   1500  137.175.2   137.175.2.28  21379   0     1177    0     19
lo0    2048  127         127.0.0.1     148     0     148     0     0
# netstat -rn
Routing tables
Destination      Gateway            Flags    Refs     Use  Interface
127.0.0.1        127.0.0.1          UH          1        0 lo0
137.175.2        137.175.2.28       U           6     1112 wdn0
#
# pppd 137.175.2.28:38.2.72.1 auto
#
# ifconfig du0
du0: flags=51<UP,POINTOPOINT,RUNNING>
        inet 137.175.2.28 --> 38.2.72.1 netmask ffff0000
# netstat -ina
Name   Mtu   Network     Address       Ipkts   Ierrs Opkts   Oerrs Collis
wdn0   1500  137.175.2   137.175.2.28  22050   0     1303    0     37
lo0    2048  127         127.0.0.1     188     0     188     0     0
du0    1500  137.175     137.175.2.28  0       0     0       0     0
#
# route add default 38.2.72.1 1
add net default: gateway 38.2.72.1 flags 0x3
#
# netstat -rn
Routing tables
Destination      Gateway            Flags    Refs     Use  Interface
38.2.72.1        137.175.2.28       UH          0        0 du0
127.0.0.1        127.0.0.1          UH          1        0 lo0
default          38.2.72.1          UG          0        0 du0
137.175.2        137.175.2.28       U           6     1112 wdn0
#

Under SCO TCP 1.2.1o, that "route add" statement results in

# route add default 38.2.72.1 1
add net default: gateway 38.2.72.1 flags 0x3: Network is unreachable


If use your SCO UNIX system to talk to an Internet service provider,
and your SCO UNIX system serves as a gateway router between your
internal LAN and the Internet, you should talk to that provider before
upgrading your SCO's TCP/IP installation to 1.2.1o.  You'll need to
change the IP address on your end of your point-to-point link, which
will require a routing change in the provider's network.

Ken (at SCO) says that they have no plans to release a patch to
restore the "un-numbered interface" capability to their TCP/IP
product.  So if this will affect you, please be careful and plan ahead
before you update your system.
--
Bob Sutterfield, Tech Support Manager
Morning Star Technologies                             +1 614 451 1883
1760 Zollinger Rd, Columbus Ohio USA, 43221-2856      +1 800 558 7827
support@MorningStar.Com                               +1 614 459 5054 (FAX)