Re: SSH ate my computer!
On Sat, Feb 11, 2006 at 09:17:53AM -0800, Tyson Varosyan wrote:
> Be that as it may, I just reloaded my whole box. I cannot remember doing
> anything else for the past 3-4 days that could have caused the problem. I
> installed SSH, rebooted, and BAM, everything haywire... In hindsight, I have
> a theory. Whether caused by SSH, I think that the network problems on my
> machine were caused by the ID of my LAN connection changing from Eth1 to
> Eth0. I think that it drove shorewall bonkers. I should have thought of
> changing the settings in the shorewall before nuking the box...
>
> Anyhow, so I now have a clean load and I still cannot get SSH server to work
> on my box. I answered all of the questions that came after the install with
> YES. I have port 22 open. What more do I need to get it to run as a daemon?
> The goal is for it to start without the need for anyone to log on to the
> box.
>
If you have the ssh server - it should run as a daemon anyway.
Check whether you have both the server and client
apt-get install openssh-server and/or dpkg-reconfigure ssh ??
What do /etc/ssh_config and /etc/ssh_d.config say ??
Which Debian version: Etch or Sid? The answer may make a difference
when replying to questions on Debian lists - some of the stuff in
unstable hasn't propagated to testing yet.
Andy
> Tyson Varosyan
> Technical Manager, Uptime Technical Solutions LLC.
> tyson@up-times.com
> www.up-times.com
> 206-715-TECH (8324)
>
> UpTime/OnTime/AnyTime
>
> -----Original Message-----
> From: Edward Shornock [mailto:debian-ml@crazeecanuck.homelinux.net]
> Sent: Saturday, February 11, 2006 12:42 AM
> To: debian-user@lists.debian.org
> Subject: Re: SSH ate my computer!
>
> On Fri, Feb 10, 2006 at 11:17:53PM -0800, Tyson Varosyan wrote:
> > Per previous thread where I was asking about options for running an
> > SSH server on my box, I ran apt-get install ssh. I was asked a few
> > simple questions and chose support for SSH 1 & 2 and selected Yes for
> > the use of some encryption key protocol. After the install, my box,
> > which was working perfectly and took hours to set up is now totally
> > hosed!!
>
> I can't see how it'd be SSH's fault...chalk it up to being a
> coincidence.
>
> > My ppp0 connection connects and dials up without issue. However, for
> > whatever reason, it is no longer pingable from the outside. I can ping
> > out, but services behind the box can no longer be reached!
>
> There's no need to remove SSH as that's not the problem, it's just a
> coincidence.
>
> Is this Sarge (stable) or Sid (unstable)? If Sid, see if a package
> named "zeroconf" was pulled in as a dependency/recommended package and
> if so, remove it with "dpkg -P zeroconf".
>
> Also, check the IP address(es) with "ifconfig" to make sure they're what
> you expect them to be. If it starts with 169.x.x.x, I'm sure of it
> being zeroconf rearing it's head...
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: