On 20 Aug 2003 15:49:11 -0700, [email]joenall.com[/email] (Joe Nall) wrote:
Yep, depending on whether the router was static or dynamic.>I have an application that is communicating with a remote SCO Unix
>server. The SCO server has multiple network interfaces and we are not
>on the default interface so a static route has been added to /etc/tcp.
>Our WAN connection to this server is down frequently. After many (but
>not all) of the network outages the static route to our system is
>missing (netstat -rn | grep my-ip-address).
>Is this known behavior (dropping a route if the network is
If the route was established through an RIP-1 broadcast from the
router, the unspecified version of OSR5 will eventually time out.
However, the static default route should not time out unless
overscribbled by a RIP broadcast announcing a different default route.
This is what is probably happening. There is some contraption on your
knotwork that is belching RIP broadcasts and OSR5 is doing its best to
If you don't need RIP-1 capabilities on the OSR5 box (i.e you only
have one route to the internet), then simply kill and disable the
routed daemon which is really RIP with a goofy name. Edit the file:
and comment out the lines that start routed. If this is a 3.2v5.0.6
or later box, then the proceedure is somewhat different and can be
excavated from somewhere on:
Never mind. Nothing there thanks to SCO removing all the old TA's.
Oh probably. However, it would be interesting to first see what>If so are there any options to the route add command to change this
you're using. Something like:
route add default ip_address_of_router
should be sufficient.
>The remote SCO server is not mine, but the admins have been supportive
>in trying to resolve the issue. They just don't know how to deal with
>the dropped route except to readd the route when we call.
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice [url]http://www.LearnByDestroying.com[/url]
# 831.421.6491 digital_pager [email]jefflcruzio.com[/email] AE6KS