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... signature.asc Description: Digital signature
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!! Don't use version 1 unless you really have SSH v.1 around. SSH2 only would be a whole lot better in security terms. dpkg-reconfigure ssh to change the setting should do it. I have 2 connections on the computer. Internet going through ppp0 and Ethernet connecting the box to the LAN. For whatever reason, my box always treated my 1492 port as Eth0 (which was not used) and my NIC as Eth1. For no apparent reason, after the install of SSH, my NIC is now detected by the system as Eth0 - but that is not the end of my problems... See various threads on this: you are not the only one with eth0/eth1 changes - it is possible to force an interface to an eth mapping. This is possibly a udev issue? 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! In addition to installing SSH, did you install anything else or do an apt-get update which brought in a whole load of packages? As someone else said: which version: testing/Etch or unstable/Sid? If running unstable/Sid - did it pull in avahi or zeroconf? I am about to pull my hair out!! At this point I am willing to just get rid of SSH so I ran apt-get remove SSH, but my system did not go back to pre-installation condition. Is there any way to UNINSTALL SSH and have my box back the way it was?! apt-get remove packagename ; dpkg -P packagename will remove and purge configuration files for any packagename Tyson Varosyan Technical Manager, Uptime Technical Solutions LLC. [EMAIL PROTECTED] www.up-times.com 206-715-TECH (8324) UpTime/OnTime/AnyTime -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: SSH ate my computer!
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. Tyson Varosyan Technical Manager, Uptime Technical Solutions LLC. [EMAIL PROTECTED] www.up-times.com 206-715-TECH (8324) UpTime/OnTime/AnyTime -Original Message- From: Edward Shornock [mailto:[EMAIL PROTECTED] 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 [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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. [EMAIL PROTECTED] www.up-times.com 206-715-TECH (8324) UpTime/OnTime/AnyTime -Original Message- From: Edward Shornock [mailto:[EMAIL PROTECTED] 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 [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSH ate my computer!
According to Edward Shornock, 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. If this doesn't work, try to identify the actual package that caused the problem. That way you file a bug against it- which is a major step toward getting it fixed. 1. apt-get -s install ssh ...that tells you which packages would get installed if you installed. Next try to install each package separately and check your network connection after each one. 2. apt-get -s install (pkg)=(version) ...check to see if a particlar package can install simply (with no dependencies). find one that is a simple (one-package) install. 3. apt-get install (pkg)=(version) ... install one of the packages that ssh depends on 4. check to see if your problem has recurred. if not, continue with the next dependent package. if so- that last package was your culprit 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... Also check with 'route' to see that your default connection is what you expect it to be. If you ifdown connections you aren't using if should be OK. Best Regards, Tony -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
