----- Original Message -----
From: "Alex"
Newsgroups: comp.unix.sco.misc
To:
Sent: Wednesday, August 10, 2005 3:17 PM
Subject: Problem with routes disappearing.


>I am actually having two completely different sets of servers at
> different locations have a problem that is very similar but not quite
> identical. All of the servers in question are IBM SC5200's with Sco
> Openserver 5.0.6 What is happening is that I have to add routes for
> the IPSEC VPN tunnels we have to these clients. The routes seem to just
> disappear. On one of the sets of servers the route is actually
> completely gone from the routing tables and has to be readded. I tried
> to use a cron job to readd the routes periodically but that doesnt seem
> to work either. On the other set of servers the route is still there
> but stops working and cant be seen with netstat -rn. I have to delete
> it and readd it to get it to start working again. Here's an example of
> the second problem. The route in question is route add -host
> 192.168.1.14 10.1.39.1
>
> This first example is taken after the route stopped working, as you can
> see it is not visible in this netstat.
>
> server1 # netstat -rn
> Routing tables
> Destination Gateway Flags Refs Use Interface
> default 192.168.1.254 UGS 0 0 net0
> 10.1.39 10.1.39.2 UC 1 0 net1
> 10.1.39.2 127.0.0.1 UGHS 0 0 lo0
> 127.0.0.1 127.0.0.1 UH 7 124 lo0
> 192.168.1 192.168.1.201 UC 1 0 net0
> 192.168.1.201 127.0.0.1 UGHS 0 0 lo0
>
> server1 # route add -host 192.168.1.14 10.1.39.1
> add host 192.168.1.14: gateway 10.1.39.1: File exists
>
> server1 # route delete -host 192.168.1.14 10.1.39.1
> delete host 192.168.1.14: gateway 10.1.39.1
>
> server1 # route add -host 192.168.1.14 10.1.39.1
> add host 192.168.1.14: gateway 10.1.39.1
>
> server1 # netstat -rn
> Routing tables
> Destination Gateway Flags Refs Use Interface
> default 192.168.1.254 UGS 0 0 net0
> 10.1.39 10.1.39.2 UC 1 0 net1
> 10.1.39.2 127.0.0.1 UGHS 0 0 lo0
> 127.0.0.1 127.0.0.1 UH 7 124 lo0
> 192.168.1 192.168.1.201 UC 1 0 net0
> 192.168.1.14 10.1.39.1 UGHS 0 0 net1
> 192.168.1.201 127.0.0.1 UGHS 0 0 lo0
>
> Any ideas as to whats happening to this route???

cd /etc
mv routed routed.disabled
mv gated.conf gated.conf.disabled # ignore error if not exist
shutdown -g0 -i6 -y # this = reboot so warn first!


Explanation:
Probably a routing daemon is doing it's job, which is to dynamically
re-write the routing table based on instructions it receives from other
routing daemons on other machines on your network.

SCO Open Server includes at least 3 different routing daemons out of the
box, namely routed and gated and irdd.
5.0.6 and below ship with routed enabled by default.
5.0.7 ships with none enabled by default.

/etc/tcp starts and stops various network services and performs other
network start/stop actions like ifconfig and "route add" and starting either
routed or gated at boot and any time you manually run /etc/tcp start or
stop. /etc/tcp (on 5.0.6 and lower) will start gated if /etc/gated.conf
exists, which it doesn't unless you created one. If gated.conf doesn't exist
and routed does exist (which is does unless you move it) then it will start
routed. So on a stock 5.0.6 (or lower) box, routed is enabled by default.
There is no "nicer" way I know of to disable routed other than simply
renaming /etc/routed. /etc/tcp does look first to see if routed exists it
doesn't just try to run it so I guess that was always the official way to
disable it. irdd is installed and commands to start it exist in /etc/tcp but
are completely commented out so nothing ever starts that automatically.

This is on 5.0.6 and lower.

On 5.0.7 (possibly also 5.0.6 after some update) you can edit ROUTERDAEMON*
variables in /etc/default/tcp to turn any routing daemons on or off and they
are all off by default.

OR, ... Maybe you need the routing daemon because your network is large and
needs to be automatic/dynamic.
In which case, find and fix the machine that's broadcasting the bad RIP
packets that the SCO box is picking up.

Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

----- Original Message -----
From: "Brian K. White"
Newsgroups: comp.unix.sco.misc
To:
Sent: Wednesday, August 10, 2005 4:38 PM
Subject: Re: Problem with routes disappearing.


>
> ----- Original Message -----
> From: "Alex"
> Newsgroups: comp.unix.sco.misc
> To:
> Sent: Wednesday, August 10, 2005 3:17 PM
> Subject: Problem with routes disappearing.
>
>
>>I am actually having two completely different sets of servers at
>> different locations have a problem that is very similar but not quite
>> identical. All of the servers in question are IBM SC5200's with Sco
>> Openserver 5.0.6 What is happening is that I have to add routes for
>> the IPSEC VPN tunnels we have to these clients. The routes seem to just
>> disappear. On one of the sets of servers the route is actually
>> completely gone from the routing tables and has to be readded. I tried
>> to use a cron job to readd the routes periodically but that doesnt seem
>> to work either. On the other set of servers the route is still there
>> but stops working and cant be seen with netstat -rn. I have to delete
>> it and readd it to get it to start working again. Here's an example of
>> the second problem. The route in question is route add -host
>> 192.168.1.14 10.1.39.1
>>
>> This first example is taken after the route stopped working, as you can
>> see it is not visible in this netstat.
>>
>> server1 # netstat -rn
>> Routing tables
>> Destination Gateway Flags Refs Use Interface
>> default 192.168.1.254 UGS 0 0 net0
>> 10.1.39 10.1.39.2 UC 1 0 net1
>> 10.1.39.2 127.0.0.1 UGHS 0 0 lo0
>> 127.0.0.1 127.0.0.1 UH 7 124 lo0
>> 192.168.1 192.168.1.201 UC 1 0 net0
>> 192.168.1.201 127.0.0.1 UGHS 0 0 lo0
>>
>> server1 # route add -host 192.168.1.14 10.1.39.1
>> add host 192.168.1.14: gateway 10.1.39.1: File exists
>>
>> server1 # route delete -host 192.168.1.14 10.1.39.1
>> delete host 192.168.1.14: gateway 10.1.39.1
>>
>> server1 # route add -host 192.168.1.14 10.1.39.1
>> add host 192.168.1.14: gateway 10.1.39.1
>>
>> server1 # netstat -rn
>> Routing tables
>> Destination Gateway Flags Refs Use Interface
>> default 192.168.1.254 UGS 0 0 net0
>> 10.1.39 10.1.39.2 UC 1 0 net1
>> 10.1.39.2 127.0.0.1 UGHS 0 0 lo0
>> 127.0.0.1 127.0.0.1 UH 7 124 lo0
>> 192.168.1 192.168.1.201 UC 1 0 net0
>> 192.168.1.14 10.1.39.1 UGHS 0 0 net1
>> 192.168.1.201 127.0.0.1 UGHS 0 0 lo0
>>
>> Any ideas as to whats happening to this route???
>
> cd /etc
> mv routed routed.disabled
> mv gated.conf gated.conf.disabled # ignore error if not exist
> shutdown -g0 -i6 -y # this = reboot so warn first!
>
>
> Explanation:
> Probably a routing daemon is doing it's job, which is to dynamically
> re-write the routing table based on instructions it receives from other
> routing daemons on other machines on your network.
>
> SCO Open Server includes at least 3 different routing daemons out of the
> box, namely routed and gated and irdd.
> 5.0.6 and below ship with routed enabled by default.
> 5.0.7 ships with none enabled by default.
>
> /etc/tcp starts and stops various network services and performs other
> network start/stop actions like ifconfig and "route add" and starting
> either
> routed or gated at boot and any time you manually run /etc/tcp start or
> stop. /etc/tcp (on 5.0.6 and lower) will start gated if /etc/gated.conf
> exists, which it doesn't unless you created one. If gated.conf doesn't
> exist
> and routed does exist (which is does unless you move it) then it will
> start
> routed. So on a stock 5.0.6 (or lower) box, routed is enabled by default.
> There is no "nicer" way I know of to disable routed other than simply
> renaming /etc/routed. /etc/tcp does look first to see if routed exists it
> doesn't just try to run it so I guess that was always the official way to
> disable it. irdd is installed and commands to start it exist in /etc/tcp
> but
> are completely commented out so nothing ever starts that automatically.
>
> This is on 5.0.6 and lower.
>
> On 5.0.7 (possibly also 5.0.6 after some update) you can edit
> ROUTERDAEMON*
> variables in /etc/default/tcp to turn any routing daemons on or off and
> they
> are all off by default.
>
> OR, ... Maybe you need the routing daemon because your network is large
> and
> needs to be automatic/dynamic.
> In which case, find and fix the machine that's broadcasting the bad RIP
> packets that the SCO box is picking up.
>
> Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!


Also, I don't know how you are setting up the extra routes at boot but on
5.0.6 there is actually an "official" place to specify routes so that they
get added at boot.
mkdir -p /usr/internet/etc/sco_ip (the dir might not exist)
vi /usr/internet/etc/sco_ip/routes

and add lines like this:
net|host destination gateway [optional netmask]

example from my own box (I'm doing default route another way so it's not in
here)
# vpn
net 192.168.0.0 10.0.0.10 255.255.0.0

I have a 10.0.0.0/255.255.255.0 lan, and a hardware vpn router at 10.0.0.10
and a bunch of remote sites with 192.168.*.* lans, each with their own
similar vpn router.
one site is 192.168.31.* another is 192.168.32.* etc... and my default
gateway is on a different net connection so my default route is not
10.0.0.10
so I have one route that says 192.168.*.* --> 10.0.0.10 which covrs all the
vpn ip's in one easy shot. If there was only one net connection and the vpn
router was also the default gateway router then I wouldn't even need that.

in your case you'd have this:
# default gateway
net default 192.168.1.254
# some comment
host 192.168.1.14 10.1.39.1

And all the other routes I see above are created automatically.

Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

> Also, I don't know how you are setting up the extra routes at boot but on
> 5.0.6 there is actually an "official" place to specify routes so that they
> get added at boot.
> mkdir -p /usr/internet/etc/sco_ip (the dir might not exist)
> vi /usr/internet/etc/sco_ip/routes
>
> and add lines like this:
> net|host destination gateway [optional netmask]
>
> example from my own box (I'm doing default route another way so it's not
> in
> here)
> # vpn
> net 192.168.0.0 10.0.0.10 255.255.0.0
>
> in your case you'd have this:
> # default gateway
> net default 192.168.1.254
> # some comment
> host 192.168.1.14 10.1.39.1

Correction,
I forgot that the new GATEWAY= variable in /etc/default/tcp came into
existence in 5.0.6 so you wouldn't put "net default ..." in routes either.
Although you could, and if you did it would override /etc/default/tcp.

Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

> Also, I don't know how you are setting up the extra routes at boot but on
> 5.0.6 there is actually an "official" place to specify routes so that they
> get added at boot.
> mkdir -p /usr/internet/etc/sco_ip (the dir might not exist)
> vi /usr/internet/etc/sco_ip/routes
>
> and add lines like this:
> net|host destination gateway [optional netmask]
>
> example from my own box (I'm doing default route another way so it's not
> in
> here)
> # vpn
> net 192.168.0.0 10.0.0.10 255.255.0.0
>
> in your case you'd have this:
> # default gateway
> net default 192.168.1.254
> # some comment
> host 192.168.1.14 10.1.39.1

Correction,
I forgot that the new GATEWAY= variable in /etc/default/tcp came into
existence in 5.0.6 so you wouldn't put "net default ..." in routes either.
Although you could, and if you did it would override /etc/default/tcp.

Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

On Wed, Aug 10, 2005, Brian K. White wrote:
>
>> Also, I don't know how you are setting up the extra routes at boot but on
>> 5.0.6 there is actually an "official" place to specify routes so that they
>> get added at boot.
>> mkdir -p /usr/internet/etc/sco_ip (the dir might not exist)
>> vi /usr/internet/etc/sco_ip/routes
>>
>> and add lines like this:
>> net|host destination gateway [optional netmask]
>>
>> example from my own box (I'm doing default route another way so it's not
>> in
>> here)
>> # vpn
>> net 192.168.0.0 10.0.0.10 255.255.0.0
>>
>> in your case you'd have this:
>> # default gateway
>> net default 192.168.1.254
>> # some comment
>> host 192.168.1.14 10.1.39.1
>
>Correction,
>I forgot that the new GATEWAY= variable in /etc/default/tcp came into
>existence in 5.0.6 so you wouldn't put "net default ..." in routes either.
>Although you could, and if you did it would override /etc/default/tcp.

I've found that running routed on OpenServer systems that don't really need
it can cause problems. If you're running a single static route to the rest
of the world, you don't need routed, and should comment out the startup in
/etc/tcp.

Bill
--
INTERNET: bill@Celestial.COM Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/

A Galileo could no more be elected president of the United States than
he could be elected Pope of Rome. Both high posts are reserved for men
favored by God with an extraordinary genius for swathing the bitter
facts of life in bandages of self-illusion.
-- H. L. Mencken

----- Original Message -----
From: "Bill Campbell"
Newsgroups: comp.unix.sco.misc
To:
Sent: Wednesday, August 10, 2005 7:04 PM
Subject: Re: Problem with routes disappearing.


> On Wed, Aug 10, 2005, Brian K. White wrote:
>>
>>> Also, I don't know how you are setting up the extra routes at boot but
>>> on
>>> 5.0.6 there is actually an "official" place to specify routes so that
>>> they
>>> get added at boot.
>>> mkdir -p /usr/internet/etc/sco_ip (the dir might not exist)
>>> vi /usr/internet/etc/sco_ip/routes
>>>
>>> and add lines like this:
>>> net|host destination gateway [optional netmask]
>>>
>>> example from my own box (I'm doing default route another way so it's not
>>> in
>>> here)
>>> # vpn
>>> net 192.168.0.0 10.0.0.10 255.255.0.0
>>>
>>> in your case you'd have this:
>>> # default gateway
>>> net default 192.168.1.254
>>> # some comment
>>> host 192.168.1.14 10.1.39.1
>>
>>Correction,
>>I forgot that the new GATEWAY= variable in /etc/default/tcp came into
>>existence in 5.0.6 so you wouldn't put "net default ..." in routes either.
>>Although you could, and if you did it would override /etc/default/tcp.
>
> I've found that running routed on OpenServer systems that don't really
> need
> it can cause problems. If you're running a single static route to the
> rest
> of the world, you don't need routed, and should comment out the startup in
> /etc/tcp.

/etc/tcp gets overwritten whenever you run netconfig.
renaming routed sticks

Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

In article <00fa01c59e05$359eecc0$6b00000a@venti>,
Brian K. White wrote:
>/etc/tcp gets overwritten whenever you run netconfig.
>renaming routed sticks

Not that renaming routed is a bad idea, but /etc/tcp is *edited* when you run
netconfig, mainly adding/removing ifconfig lines - it's not recreated from
scratch.
In any case, I think that in 5.0.6, router daemon startup was configured by the
ROUTER_DAEMON= line in /etc/default/tcp.

John
--
John DuBois spcecdt@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/