Re: sshd and IPv4 forwarding no longer working

On 01/21/2009 05:01 PM, noah wrote:
Hi there,

I performed a recent upgrade and possibly openssh got upgraded as well.
I dont know and I am not sure how to figure that out with apt-get.

anyways somewhere in the past day or so I am no longer able to ssh to my
ubuntu server. I can see sshd running but I am not able to receive a
prompt from the daemon. Here check this out. I am able to ssh locally
but not from another server. I am also finding that I am unable to
forward IPv4 traffic through the server. Most likely the two are
related. I am trying to figure out how I can troubleshoot this since
sshd is showing it is running.

I use firestarter for my firewall but even disabling the firewall I am
unabel to forward traffic nor does sshd answer port 22. This was
working up until a day ago. Now something was changed during an upgrade
and no longer can I use my server.

here are version and /etc/ssh/sshd_config details.

noah@tsunami:~$ /usr/sbin/sshd -V
OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007

$ cat /etc/ssh/sshd_config
# Package generated configuration file
# See the sshd(8) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
ListenAddress 0.0.0.0
#ListenAddress ::

Perhaps because you have the listenAddress set to 0.0.0.0? Here is that
portion from mine:

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0

If you actually have a valid 'ListenAddress', then I _think_ that you
need a valid IP there. Try commenting out with the # and then:

sudo /etc/init.d/ssh restart




--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Relevant Pages

  • Re: Upgrading sshd?
    ... install it which puts it in /usr/local/sbin/sshd then test it. ... fired up the new one on port 2000 and tested it there. ... that worked I killed the process running on port 22, copied sshd to ... the upgrade via ssh I didn't feel like cutting myself off by accident then ...
    (freebsd-questions)
  • Re: different ssh settings for different users
    ... I believe you can do this by running a different sshd for each unique ... port (using ListenAddress, Port) that you wish to allow ssh connections ... I am not able to ssh on the port 3455 whereas on port 22 I can ssh. ...
    (Fedora)
  • Re: sshd multiple IPs multiple ports
    ... > 5.3 box that i've got unique requirements for sshd on. ... > nics, one external one internal. ... > on port 22 and to allow all user's in. ... You do the different ports with multiple ListenAddress lines in ...
    (comp.unix.bsd.freebsd.misc)
  • portmanager looping on libtool on 6.2 -> 6.3 upgrade
    ... I'm in the process of bringing a production web/mail server up to FreeBSD 7.0 from 6.2. ... After practicing the process on a non-production box set up in essentially the same manner, I discovered that the only major issue to look out for was the fact that I needed to hold back the upgrade of Python, since the CMS system running on the box will die if it doesn't have Python 2.4 specifically. ... Port Status Report "forced mode" ... I've tried simply going into /usr/ports/devel/libtool15 and running "suod make install clean", and I end up with this output: ...
    (freebsd-questions)
  • How did this happen?
    ... May 12 06:50:43 localhost sshd: Failed password for illegal user ... cgi from 212.93.149.205 port 2265 ... Starting sshd: ...
    (comp.os.linux.security)