sshd and IPv4 forwarding no longer working
NoOp
glgxg at sbcglobal.net
Thu Jan 22 02:24:25 UTC 2009
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 at 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
More information about the ubuntu-users
mailing list