🚀 go-pugleaf

I think this is more of a software problem rather than a routing problem.
I'm running 8.2(7) on out Cisco AGS+/3 quite successfully until a few
days ago. During that time, we lost our X.25 link to the outside world,
through which we encapsulate our IP packets. When the line was down, a
host on our local network broadcast to fact that it knew how to get to 
the route 0.0.0.0 (ie the default) in 2 hops (yes, one hop to itself,
and one back to the cisco) - hence a routing loop was formed. 

This isnt the problem though. The problem then occurred in that the 
Cisco changed its configuration to point to this host as the default
route, and subsequently, when the X.25 switch was brought back up, 
routing was mangled.

Is this a known problem, and do i need to upgrade software (i think one
is on the cards when we *finally* get the FDDI card we've been promised
for months, and has not yet appeared. 

Thanks in advance.

--
Glyn Simpson, Systems Officer,  //  Voice: +44 (0) 21 414 6575
University of Birmingham        //  Fax:   +44 (0) 21 414 3952
Email: G.Simpson@bham.ac.uk     //  NIC Handle: GS56