Setting the default gateway for SCO Openserver 5

Thanks yuzh,

1. I found out that one server is running 5.0.4, the other 5.0.5.

2. We tried to use the scoadmin before, but the default gateway settings are nowhere to be found.  There is something odd called a "broadcast address", but its structure is not that of a gateway ip.

The 5.0.4 box is going away in less than a year, so it's not worth the pain or expense of upgrading.

Not much different between sco 5.0.4 and 5.0.5, when you run scoadmin, look at the network manager, it should be there.

or try:

vi /etc/gateways
and
vi /etc/networks

I've looked in scoadmin's network manager.  There is no mention of routing or gateways.

There is no gateways file in /etc.

This is the listing in the /etc/networks file:

ce
loopback   127
test-net   192.0.2
multicast  224

You need to have a look at /etc/default/tcp file
and change the GATEWAY variable (configure a default route by supplying the IP address of the system to which network traffic should be directed if no other routes can resolve the destination)

Here are the contents of /etc/default/tcp

DOMAIN=
NETMASK=
BROADCAST=

Doesn't look like this file is being used by anything!

try :

As root either on the console or in an xterm (with TERM set to xterm)
run the command

     # /etc/inet/menu
     
Then either reboot or run the script
     # /etc/inet/rc.restart  # restart inetd and internet software

Here are the contents of /etc/default/tcp

DOMAIN=
NETMASK=
BROADCAST=

Doesn't look like this file is being used by anything!

There is no /etc/inet/ directory.

There is no /etc/inet/ directory.

Is there some reason you need to run SCO? It's very very very old.

If you have $$$$, upgrade to UnixWare (later version from SCO).

If you don't have $$$$, but don't have any particular dependancies, consider Linux or FreeBSD.

We have to run SCO until next year.  Long story...

As of right now I'm beginning to believe that UNIX isn't all it's cracked up to be.  This would be a 10 second operation in Windows 2000.  Don't mean to stir any pots here, but shouldn't this be an easy thing to do???

I just forgot to ask you a basic question, could you please post the output of

uname -a

from my memory there are some differet between the Enterprise version and just a normal OpenServer Host system. The Enterprise system has more network support, the Open Host likely just stand alone.

SCO UNIXWare hade /etc/inet

But in the worst case you can edit /etc/gated.conf (default
not on the system, do "man gated.config" to find out the details), or edit /etc/rc2.d/S90iproute file to manually put your routing infor there.

This is an easy thing to do in a modern Unix variant. It's not easy in Windows for Workgroups either.

Okay,

The output of uname -a:
Older server: SCO_SV fkgsrv03 3.2 2 i386
Newer server: SCO_SV unixsrva 3.2 5.0.5 i386

I believe I failed to mention that both are running SCO OpenServer.  Sorry about that.

We've tried the S90iproute and S99route (saw these on the Caldera website) and they didn't work.  It's as if the server is ignoring common IP files and working off something else...

Last night, per instructions by a consultant, we added a line to the /etc/default/tcp file:
/etc/route add default 10.x.x.x 0 > /dev/null 2>&1
This seemed to work when we typed netstat -rn.  The route table showed the following line:
default 10.x.x.x UGS 0 0 net0
However, after typing the route add line manually, the entry is this:
default 10.x.x.x UCS 0 0 net0

The difference only appears to be in the "flags" column (UCS=right,UGS=wrong).  Our consultant doesn't know what the flags mean.  This could be the key?!?!!!?!

Can you decipher, yuzh?

I can remember what does it mean now (I have not use SCO 5.0.4 OpenServer Host for about 2.5 year), do a man route
to find out. Please pay attention to the way it specify the IP. (There might be something different between the OLD SCO and the New one. and Some of the network features are not available in the SCO Host system, Enterprise is the FULL Version )

Sorry, I mean I can not remember ! The keyboard is going too fast !

I did a "man netstat" to find out what the flags mean:

U = up
G = gateway
C = clone (?)
S = static

I don't know what to look for in the "man route" command, but nothing there seems to indicate how to keep this routing table entry from becoming a "clone".

Do a man route to find out the options/modifiers.

Try the following command:

/etc/route add default your-gateway

to see if anything happen.

If it doesn't work, try the do the followings:
    /etc/route add NIC-IP 127.0.0.1
    * setup route from localhost to the interface(your box ip)
    /etc/route add gateway-ip NIC-IP
    * setup route from the interface to your gateway.

yuzh,

If you'll notice, in the original question I stated that we are typing /etc/route add default 10.x.x.x after every reboot.  This does work.  

Please also refer to the comment I posted 09/04/2002 07:31AM PST.  This demonstrates the difference between entering the line in the /etc/default/tcp file and typing manually.  I really believe that the "C" flag is the key here.

dex

Have you try to put :
  /etc/route add default 10.x.x.x

  In a startup script (call it something like /etc/rc2.d/S99route or whatever), instead of putting it in  the /etc/default/tcp file
  See what happen !

Please see my comment from 09/04/2002 07:31AM PST.

Maybe it would be helpful for you to read everything through one more time.  I'm beginning to repeat myself a bit :)

dex

ok try to use:

route add -cloning /etc/route add default gateway-ip


PS: the command line modifiy -cloning is available in  
    Solaris, I'am not sure that if it work in SCO or not,
    Just give it a try.

      Routing Flags
     Routes have associated flags which  influence  operation  of
     the  protocols  when  sending to destinations matched by the
     routes. These flags may be set  (or  sometimes  cleared)  by
     including  the following corresponding modifiers on the com-
     mand line:
     Modifier                    Flag                      Description

     -cloning             RTF_CLONING           generates a new route on use
     -xresolve            RTF_XRESOLVE          emit mesg on  use  (for  external
                                                lookup)
     -iface               ~RTF_GATEWAY          destination is directly reachable
     -static              RTF_STATIC            manually added route
     -nostatic            ~RTF_STATIC           pretend route added by kernel  or
                                                daemon
     -reject              RTF_REJECT            emit  an  ICMP  unreachable  when
                                                matched
     -blackhole           RTF_BLACKHOLE         silently  discard  pkts   (during
                                                updates)


    If this can't solve your problem, I thing we have to wait for someone currently work with SCO boxes or you figure it out by yourself.

Good luck on this one.

    In the future, if you are thinking about the OS change, Linux, Solaris, FreeBSD might be the options. Easy to get support.

It appears that I failed to make sure the S99route file name began with a capital "S".  A lower case "S" is ignored altogether.

Thanks for your help, yuzh!

dex

You are welcome. To enable a start up script, the file name must be start with Capital "S", to disable it just simplely rename the script name, the most commond one is to use lower case "s".

dexweaver, I have a SCO_SV nibstest 3.2 5.0.6 i386, to resolve the problem you are having I added the gateway to the /etc/tcp file and it worked.

DOMAIN=
NETMASK=
BROADCAST=
GATEWAY=

Borrowed fron another source...Easier than typing...

Setting a default route is easy:

route add default xxx.xxx.xxx.xxx

is all it takes.  However, unlike NT systems (which stick it in the Registry), that won't survive a reboot.

If you have 5.0.6, you have the file /etc/default/tcp and you can edit that to add the route to the

GATEWAY=

line.

If you have 5.0.4 or 5.05, a nice place to add routes is /usr/internet/etc/sco_ip/routes.  The startup script /etc/rc2.d/S90iproute reads that file and sets routes.  The format is pretty obvious:

# comments are ok
# simple form
net default 10.1.1.3
# it's smart enough to delete the previous default
net default 192.168.1.2
# routes to specific hosts
host 192.168.1.8 10.1.1.7
# netmasks optional
net 192.168.1.0 10.1.1.3 255.255.255.0
# if field 1 isn't host or net, it's ignored
happiness 172.16.80.10 10.1.1.1
sanjose 172.16.80.10 10.1.1.1

Prior to 5.0.4, some folks would  edit /etc/tcp to add the "route add" line.  That has the advantage  of letting you use tcp stop and tcp start and have the route set, but keep in mind that an upgrade will overwrite /etc/tcp.

The typical solution pre 5.0.4 is to add a /etc/rc2.d/S99route file and add the "route add" command to it.(the file does not exist- you have to create it).  Remember to make it executable (chmod 755).

Keeping the route on any version can be affected by running  programs like routed- a router on the network may have a different idea what routes should be set, and it may send RIP updates- if routed is running on your system, your routing table will change.  Comment routed out of /etc/tcp to disable it.

Note that a device on the other side of a router has to have a route BACK to you also.

Also, you need to reboot or manually type the route add command to have this work immediately