----- Original Message -----
From: "Ted Summers" <djtbs1@qwest.net>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Tuesday, September 20, 2005 10:01 PM
Subject: Re: Fixing route table
> In article <-o2dndk2tsXTya3eRVn-pA@giganews.com>,
> "Tony D." <nospam@nospam.com> wrote:
>
>> We run a Windows Network with web accress via ISA2000 on a proxy server.
>> Our new proxy server (192.168.1.28) replaces an older unit
>> (192.168.1.21).
>>
>> Our major applications are on SCO 5.05 server whose routing table is
>> shown below. My static routes to our subnets (192.168.2.0, 192.168.3.0,
>> 192.168.4.0) are added at bootup (/etc/rc2.d/S85.tcp). Whenever the
>> Unix server is rebooted it looses the internet route for our edi
>> transmissions and these have to be manually entered so the host can be
>> found through the new proxy (192.168.1.28). The routing table shows many
>> routes to the OLD proxy 192.168.1.21. I have cleaned the Windows
>> servers of all references to the old proxy. How can I find where the
>> Unix routes through 192.168.1.21 are coming from?
>>
>>
>> Routing tables
>> Destination Gateway Flags Refs Use Interface
>> default 192.168.1.28 UGS 2 0 net0
>> 64.178.59.82 192.168.1.28 UGHS 0 0 net0
>> 64.233.161.147 192.168.1.21 UGHD 0 2 net0
>> 66.135.192.123 192.168.1.21 UGHD 0 3 net0
>> 66.135.192.124 192.168.1.21 UGHD 0 10 net0
>> 68.142.226.54 192.168.1.21 UGHD 0 7 net0
>> 127.0.0.1 127.0.0.1 UH 12 334279 lo0
>> 192.168.0.12 192.168.1.21 UGHD 0 8 net0
>> 192.168.1 192.168.1.24 UC 1 0 net0
>> 192.168.1.24 127.0.0.1 UGHS 0 0 lo0
>> 192.168.2 192.168.1.1 UGS 22 712 net0
>> 192.168.3 192.168.1.1 UGS 0 0 net0
>> 192.168.3.14 192.168.1.21 UGHD 0 1 net0
>> 192.168.4 192.168.1.1 UGS 5 84 net0
>> 192.250 192.168.1.28 UGS 0 0 net0
>> 192.250.28 192.168.1.28 UGS 0 0 net0
>> 192.250.28.66 192.168.1.21 UGHD 0 153 net0
>> 207.207.237.232 207.207.237.235 UC 1 0 net1
>> 207.207.237.235 127.0.0.1 UGHS 1 6 lo0
>> 209.144.44.11 192.168.1.21 UGHD 0 14 net0
>> 212 192.168.1.28 UGS 0 0 net0
>> 212.67.80.60 192.168.1.21 UGHD 0 17 net0
>> 216.109.118.66 192.168.1.21 UGHD 0 12 net0
>> 216.178.92.131 192.168.1.21 UGHD 0 2 net0
>> 224 192.168.1.24 UCS 0 0 net0
>
> I had to do this - manual edit of a file. Don't remember the file. Found
> the answer on aplawrence.com- a great resource / consultant....have
> found many answers to my questions at the site....
>
> Regards,
> TS
There is an official spot for extra routes, but I almost never see it used
by others:
vi /usr/internet/etc/sco_ip/routes
If there is no such file then try this:
find /etc/rc* /etc/init.d -depth |xargs grep -l "192\.168\.1\.21"
Usually if they even have any extra routes or even a default route for the
internet,
it was done by adding commands to /etc/rc.d/8/userdef
or by adding a new script anywhere in /etc/rc.d/*
or by adding a new script in /etc/rc2.d with a number higher than 85 so it
runs after S85tcp
examples: /etc/rc2.d/S99route, S86route, S99defaultroute, S99gateway,
S99mycompany
You'll notice when looking along those lines that there is an
/etc/rc2.d/S90iproute (really /etc/init.d/iproute)
That's not an add-on, that's the stock script that reads
/usr/internet/etc/sco_ip/routes
Or they edited /etc/tcp (aka /etc/rc2.d/S85tcp)
Basically, since most people were'nt aware of the routes file (or maybe
before some particular version the S90iproutes script didn't exist yet?) you
have to browse /etc, /etc/init.d /etc/rc.d and /etc/rc2.d and look for
things that aren't stock. The above spots, which are all covered by that
find command, should turn it up though.
Brian K. White --
brian@aljex.com --
http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!