Date: Fri, 7 Jul 2000 11:21:04 -0700 (PDT) From: Jason Fesler <jfesler@gigo.com> To: Gabriel Ambuehl <gabriel_ambuehl@buz.ch> Cc: Luigi Rizzo <luigi@info.iet.unipi.it>, Chris Shenton <cshenton@uucom.com>, Alan Batie <batie@rdrop.com>, isp@FreeBSD.ORG Subject: Re: Re[4]: load balancing Message-ID: <Pine.BSF.4.21.0007071116360.69269-100000@heaven.gigo.com> In-Reply-To: <11591545084.20000707190001@buz.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
> What if it's pingable, but ssh failed? And how do you solve the Where we work, we do it with a simple inetd daemon that understasnds simple commands (no ssh, very limited command set, and protected by firewall). If the box is up *at all*, that functionality has also been up. We've been fortunate. Otherwise, we'd have our pagers going nuts, and we would use a console to get to the machine [all hosts have consoles hooked up via terminal servers]. One could make the IP changing interface as simple or complex as deemed fit, for the application they will fill. If they are loose on the net without good firewalls (likely if on a budget) then SSH would probably be the only way. I'd use SSH with *restrictions* - have SSH only permit specific commands to be ran via the rsa key. Or, use non-privileged accounts for ssh'ing, and allow the non-priv account access to ifconfig. Really, its up to the end site to figure out how far they need to go. One could even arguable have the baby sitter box use serial cables to log in via console and do the job.. Have fun :-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007071116360.69269-100000>