Need help with adding default routing under 3.2.4.2
Pat Welch
I've picked up a client still on Open Desktop, which is 3.2.4.2 under
the hood.
The client is 500 miles away, and has no internet access, and he has a
VOIP phone connection that is too poor for modem connections (we tried).
I need to get internet access going for him - but the syntax under 5.x,
route add default xx.xx.xx.xx, gets an error asking for the metrics on
the route, something defaulted to under SCO 5.0.x
I never worked much with 3.2.4.2, having moved over to SCO from AT&T
Unix after 5.0 came out.
Does anyone have a URL for the old 3.2.4.2 man pages, or have the
correct syntax and procedures to get 3.2.4.2 on the internet?
And while I'm wishing, is there a compiled version of SSH that will work
under 3.2.4.2?
I've already had him cut and paste the syntax for /etc/resolv.conf (3.2
uses that, right?) with his local DNS numbers, and he is connected to
the internet via Time/Warner cable.
He can ping by IP but not by name at the moment.
TIA.
--
----------------------------------------------------
Pat Welch, UBB Computer Services, a WCS Affiliate
SCO Authorized Partner
Microlite BackupEdge Certified Reseller
Unix/Linux/Windows/Hardware Sales/Support
(209) 745-1401 Cell: (209) 251-9120
E-mail: pat...@inreach.com
----------------------------------------------------
John Boland
> Hi all.
>
> I've picked up a client still on Open Desktop, which is 3.2.4.2 under
> the hood.
>
> The client is 500 miles away, and has no internet access, and he has a
> VOIP phone connection that is too poor for modem connections (we tried).
>
> I need to get internet access going for him - but the syntax under 5.x,
> route add default xx.xx.xx.xx, gets an error asking for the metrics on
> the route, something defaulted to under SCO 5.0.x
Pat,
Try
route add default <IP> 0
If that doesnt work let me know and I can kick off an ODT 3.0
system and see what the man page says.
John
Steve M. Fabac, Jr.
> Hi all.
>
> I've picked up a client still on Open Desktop, which is 3.2.4.2 under
> the hood.
>
> The client is 500 miles away, and has no internet access, and he has a
> VOIP phone connection that is too poor for modem connections (we tried).
>
> I need to get internet access going for him - but the syntax under 5.x,
> route add default xx.xx.xx.xx, gets an error asking for the metrics on
> the route, something defaulted to under SCO 5.0.x
>
> I never worked much with 3.2.4.2, having moved over to SCO from AT&T
> Unix after 5.0 came out.
>
> Does anyone have a URL for the old 3.2.4.2 man pages, or have the
> correct syntax and procedures to get 3.2.4.2 on the internet?
>
> And while I'm wishing, is there a compiled version of SSH that will work
> under 3.2.4.2?
>
> I've already had him cut and paste the syntax for /etc/resolv.conf (3.2
> uses that, right?) with his local DNS numbers, and he is connected to
> the internet via Time/Warner cable.
>
> He can ping by IP but not by name at the moment.
>
> TIA.
>
John's already answered the route add problem. The /etc/resolv.conf
is used by 3.2v4.2:
$ cat resolv.conf
hostresorder local bind /nis
domain xxxxx.org
nameserver 10.3.31.80
nameserver 10.3.31.79
$
The above is from a copy of a client's 3.2v4.2 full system backup
restored to my system for development work on their Infomix application.
Ok, here's the man page from 3.2v4.2
route(ADMN) route(ADMN)
Name
route - manually manipulate the routing tables
Syntax
/etc/route [ -f ] [ -n ] [ command [net | host] destination gateway
[ metric ] ]
Description
route is a program used to manually manipulate the network routing
tables. It is normally not needed, since the routing daemon, routed,
manages the system routing table and therefore handles this function.
route accepts optional commands, as well as arguments to those commands,
as follows:
command The command can be either add, to add a route, or delete, to
delete route.
net | host
These optional keywords, net or host force the destination to
be interpreted as a network or a host, respectively. If one of
these optional keywords does not follow the command, routes to
a particular host are distinguished from those to a network by
interpreting the Internet address associated with destination.
If the destination has a ``local address part'' of INADDR_ANY,
the route is assumed to be to a network; otherwise, it is
presumed to be a route to a host.
destination
This is a host or network for which the route is ``to''.
gateway This is the gateway to which packets should be addressed.
metric This is an optional count indicating the number of hops to the
destination. If no metric is specified, route assumes a value
of 0.
Please note the following:
If the route is to a destination connected via a gateway,
metric should be greater than 0.
All symbolic names specified for a destination or gateway are
looked up first in the host name database; see hosts(SFF). If
this lookup fails, the name is then looked for in the network
name database; see networks(SFF).
route uses a raw socket and the SIOCADDRT and SIOCDELRT ioctl's to do its
work. As such, unly the super user may modify the routing tables.
Options
-f Flush the routing tables of all gateway entries. If this is used in
conjunction with one of the commands described above, the tables are
flushed prior to the command's application.
-n Prevents attempts to print host and network names symbolically when
reporting actions.
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
Pat Welch
Thanks, Steve!
Pat Welch
Thanks, John.
Nico Kadel-Garcia
> And while I'm wishing, is there a compiled version of SSH that will work
> under 3.2.4.2?
And while you're wishing, can I have a pony?
More seriously, 3.2.4.2 is so far out of date it's not reasonable for
any un-cracked version of SSH to be expected to even compile on it.
Unless you can assemble a GNU compatible toolchain with gcc, GNU make,
etc., such as the gnutools package of 5.0.7, you're going to have one
heck of a time even trying to compile it. The random number generators
of modern SSH clients, in particular, are unlikely to be able to
compile.
Tony Lawrence
> Try
>
> route add default <IP> 0
Well, yeah but that won't "stick" like it does in Windows. You need
to put it in a startup script (on this version, on modern SCO it's in /
etc/tcp, see http://aplawrence.com/SCOFAQ/FAQ_scotec4defaultroute.html
for the various options).
Pat Welch
Hi, Tony.
I'm aware the route command is not sticky.
Once I get access, I had planed to add the command to whatever 3.2.4.2
uses to control startup behavior - I just don't recall if they use
/etc/rc or scripts in /etc/rc2.d as in OS5.
Tony Lawrence
> Tony Lawrence wrote:
> > On Oct 21, 4:04 am, John Boland <bonix...@gmail.com> wrote:
>
> >> Try
>
> >> route add default <IP> 0
>
> > Well, yeah but that won't "stick" like it does in Windows. You need
> > to put it in a startup script (on this version, on modern SCO it's in /
> > for the various options).
>
> Hi, Tony.
>
> I'm aware the route command is not sticky.
>
> Once I get access, I had planed to add the command to whatever 3.2.4.2
> uses to control startup behavior - I just don't recall if they use
> /etc/rc or scripts in /etc/rc2.d as in OS5.
/etc/rc2.d
But you'd know that seconds after logging in anyway, so I'm not saying
this for your benefit.
I'm wondering when the last 4.2 system will die.. I still see some
now and then. Even saw a Tandy 6000 not too many years ago :-)
Pat Welch
A Tandy 6000??? holy cow, *ix breath!!
Trip down memory lane: I was fascinated by, and broke my budget at the
time when I got one, in late 1977/early 1978 when the TRS-80 came out.
With a whopping 4 K (not MB) of RAM and an audio grade cassette recorder
to store programs and data on.
That was where I learned that sleep was for wimps - I taught myself
TRS-80 basic at night and then risked falling asleep working on 8 foot
tall printing presses at my day job at the time.
I kept that up for 6 months or so, then up and quit the day job and went
back to college to larn that there computer stuff properly, using
punched cards and terminal basic like real programmers did. :)
I still shudder when the word COBOL is mentioned. I used to do my
Fortran problems in Cobol and vice versa. A simple report program in
Cobol required me 2-finger typing the punch card machine for 2000 cards,
when the exact same report in Fortran took about 80 cards.