Hello,
I'm not sure if this has been covered before, but...
I'm having the weirdest problems with static routes. It doesn't happen
often. When it happens, it can really mess things up. The static route on
one of my machines changed earlier today, and the machine stopped allowing
people to login. The machine is an alpha 4100, 2GB RAM, 1 NIC, running Tru64
UNIX 4.0f (jumbo pak 1). It's an SAP test machine. It's set up so that the
machine gets a static route on boot up. It's not running routed or gated.
Here are relevant segments of config files:
/etc/routes:
default 22.22.22.1
/etc/rc.config:
ROUTED="no"
ROUTED_FLAGS=
ROUTER="no"
GATED="no"
GATED_FLAGS=""
And here's what I see for default route when I ran netstat -r:
default rocdcr1-e0-0.vta.o UGS 0 24 tu0
I also see a bunch of dynamic routes to the PC's that are connected to this
machine, but I don't care much about those.
This morning, when I was fixing the static route problem, the default route
looked like the following:
default rocdcr3.vta.org UGMS 1 6788 tu0
I looked up the man pages and the "M" means modified by redirect.
What I've managed to gather from our network guys is that there was some
sort of "network event" in one of our buildings, around the time the static
route changed. It leads me to believe that the machine was trying to respond
to connected users, but was not able to reach them. It decided it needs to
take another route to reach the connected users.
If this is indeed what had happened, how do I prevent it from happening
again? Is there something I can do to make static routes truly unchangeable?
Thanks, I will summarize.
Received on Tue Feb 29 2000 - 23:48:30 NZDT