Has anyone seen a situation where traffic to a particular host or subnet
whose subnet is defined by a route maintained by routed stops working?
Basically, the situation seems to be this: we have "routed -q" running
on our DU 4.0D boxes, and mostly, we can ping a box on a different
subnet through our router that's advertising via RIP v1 the routes it
maintains. However, sometimes we can't ping anything, and the problem
seems to be unique to the machine. All other computers in the network
can still ping correctly but the one afflicted box. The route table
continues to show the correct routes, but nothing happens. Flushing the
route table and restarting routed seems to fix the problem. This is kind
of annoying. Has anyone seen this previously, and if so, do you have a
solution?
--
Robert L. McMillin | Not the voice of Syseca, Inc. | rlm_at_syseca-us.com
Personal: rlm_at_helen.surfcty.com | rlm_at_netcom.com
Received on Tue Sep 22 1998 - 04:18:14 NZST