SCO 5.0.5 Add routes for new networks

Hi all,

n00b here. We currently have 3 SCO 5.0.5 machines in our network that run a mission management system.

Our internal network was always a 10.0.0.0 network and the machines worked fine.

Our company is going through a network upgrade for VoIP and some of our departments are now on VLANS. They are 10.1.11.x and 10.1.12.x. The SCO machines are still able to talk to anything on the 10.0.0.0 network fine but they cannot talk to anything on the new VLANs.

I have been trying to add routes to the S99route script but that hasn't solved anything. My knowledge is very limited with Unix and SCO 5.0.5 is pretty old.

No one in the company has any knowledge as the people that first built the SCO machines have moved on a long time ago.

What is the proper way to get the machines to route traffic to and from the VLANs? I have searched the net but haven't had much luck.

Thanks in advance for any help or advice you may have.

For testing a route type "/etc/route add default <IPADDRESSOFROUTER>" from the command line w/o the quotes. Then configure your router to handle the traffic. If that works put the /etc/tcp script by searching for ifconfig and the section is pretty self explanitory. The line will be "/etc/route add -net default <IPADDRESSOFROUTER> >/dev/null 2>&1 &" again w/o the quotes. Enter the default router IP address w/o the <> in the string.

You can update (edit) /etc/default/tcp, rather than modifying /etc/tcp for the default route.
You should also be aware that 5.0.5 does not run on Pentium 4 systems.
Can I install OpenServer 5.0.4 5.0.5 or 5.0.6 on a Pentium 4 based machine?

Thanks for the replies. The machines are not on any P4 systems, they are very old actually.

I didn't think that /etc/default/tcp file was even used in SCO 5.0.5 and below. I do however have the domain, broadcast and gateway in that file. They are all correct as I have not made any changes to that file.

I tried creating the /usr/internet/etc/sco_ip directory with the routes file.

I added the following to it:

net default 10.0.0.254
net 10.1.12.0 10.0.0.254

Both show up during the boot process but they still cannot reach the 10.1.12.0 network. They can still ping within the 10.0.0.0 network though. We are using a Cisco PIX at the border of our network, there are no true routers in our network that I am aware of.

The default route was added before in a S99route script which did allow some remote people to connect in. I did remove that script when I created the sco_ip/routes file.

Maybe it's a routing issue on one of the layer 3 switches. I'll have our network guy take a look.

Any thoughts what to check for?

Thanks again.

One of my clients who has a VPN use the following:
/etc/rc2.d/S99route.vpn

/etc/route add 192.168.3.105 192.168.200.254
/etc/route add 192.168.1.100 192.168.200.254

in order to reach the remote machines, where 200.254 is the gateway address, and 3.105, and 1.100 are remote work stations.
.

Thanks for the replies guys. Turns out adding the entries to the sco_ip/routes file did the trick.

The machines can't ping to the new VLAN but that's not an issue. Thanks again for the help guys.