On Sat, Nov 09, 2002 at 02:37:45PM +0000, Antony Stone wrote: > On Thursday 07 November 2002 7:53 pm, Guillaume Marcais wrote: > > > We have remote routers that we access with ssh. Sometime, I am not > > careful enough and I enter stupid routing information that not only > > leaves our clients connectionless but also prevents me from accessing > > the router. Then truck roll, long downtimes and angry customers... I am > > really a child sometimes :) > > I recommend you set up an auto-answer modem connected to the serial port of > the router. If the router is a Linux box, installing an internal modem may > be cheaper or more convenient. Sorry to act like an echo, but seconded - as long as you've got some kind of Caller Line Identification restrictions on the modem. Or a "console server" or similar, a seperate host you can access regardless of the changes to the router's configuration that gives you a serial connection to the host. Or have a working minimal configuration that permits you to have remote access. Then before you make a change use an "at" job or similar to bring that working configuration up in five minutes unless you can ssh in and stop it... that way you know you'll be able to get back into the router to have another crack at the problem. -- FunkyJesus System Administration Team
