On Mon, Apr 09, 2007 at 07:48:11PM -0700, Dusty Wilson wrote:
Sorry if I missed it, but has anyone mentioned netstat?
sudo netstat -lnp | grep ssh
That should show if you have any running ssh processes listening on
your server and which IP addresses/port numbers it is listening on.
If
On Mon, Apr 09, 2007 at 07:48:11PM -0700, Dusty Wilson wrote:
Sorry if I missed it, but has anyone mentioned netstat?
sudo netstat -lnp | grep ssh
That should show if you have any running ssh processes listening on
your server and which IP addresses/port numbers it is listening on.
If
On Tue, Apr 10, 2007 at 08:06:36AM -0400, Roberto C. Sánchez wrote:
sudo netstat -lnp | grep ssh
That should show if you have any running ssh processes listening on
your server and which IP addresses/port numbers it is listening on.
If you haven't already done such a thing, could you
Hello! :)
On Mon, Apr 09, 2007 at 03:53:24PM +0200, Jochen Schulz wrote:
If you suspect SSH is being blocked by a system not under your control,
you could try to have sshd listen on a port other than 22 (443 comes to
mind). Maybe your ISP/hosting provider blocks 22.
Yes, my ISP/hosting
csanyipal wrote:
Hello!
I have installed on Etch openssh-client openssh-server.
I can to login to localhost with ssh.
I want to allow a remote user to login with ssh on to my system.
What is the contents of your /etc/hosts.allow and /etc/hosts.deny?
According to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 10, 2007 at 03:17:58PM +0200, csanyipal wrote:
Hello! :)
On Mon, Apr 09, 2007 at 03:53:24PM +0200, Jochen Schulz wrote:
If you suspect SSH is being blocked by a system not under your control,
you could try to have sshd listen on
On Tue, Apr 10, 2007 at 03:29:24PM +0200, Jörg-Volker Peetz wrote:
I have installed on Etch openssh-client openssh-server.
I can to login to localhost with ssh.
I want to allow a remote user to login with ssh on to my system.
What is the contents of your /etc/hosts.allow and
Hello!
I have installed on Etch openssh-client openssh-server.
I can to login to localhost with ssh.
I want to allow a remote user to login with ssh on to my system.
I use iptables as a firewall and have added a rule to open the port 22:
$ sudo iptables -L
...
target prot opt source
On Mon, Apr 09, 2007 at 03:01:32PM +0200, csanyipal wrote:
Hello!
I have installed on Etch openssh-client openssh-server.
I can to login to localhost with ssh.
I want to allow a remote user to login with ssh on to my system.
I use iptables as a firewall and have added a rule to open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Apr 09, 2007 at 03:01:32PM +0200, csanyipal wrote:
Hello!
I have installed on Etch openssh-client openssh-server.
I can to login to localhost with ssh.
I want to allow a remote user to login with ssh on to my system.
I use
csanyipal:
I use iptables as a firewall and have added a rule to open the port 22:
That probably means you are blocking any traffic not explicitly allowed,
correct? Maybe it would help to show us your complete iptables script.
And you are connected directly to the internet, right? No NAT?
$
On Mon, Apr 09, 2007 at 09:35:50AM -0400, Douglas Allan Tutty wrote:
Just because you opened the port doesn't mean that ssh will listen on
that interface automatically; tell it.
Port 22
May I also suggest limiting ssh logins to members of the ssh group? And
disallow root login via ssh.
On Mon, Apr 09, 2007 at 03:53:24PM +0200, Jochen Schulz wrote:
I use iptables as a firewall and have added a rule to open the port 22:
That probably means you are blocking any traffic not explicitly allowed,
correct? Maybe it would help to show us your complete iptables script.
I attach
On Mon, Apr 09, 2007 at 06:12:06PM +0200, csanyipal wrote:
On Mon, Apr 09, 2007 at 03:53:24PM +0200, Jochen Schulz wrote:
I use iptables as a firewall and have added a rule to open the port 22:
That probably means you are blocking any traffic not explicitly allowed,
correct? Maybe it
On Mon, Apr 09, 2007 at 03:01:32PM +0200, csanyipal wrote:
Hello!
I have installed on Etch openssh-client openssh-server.
I can to login to localhost with ssh.
I want to allow a remote user to login with ssh on to my system.
I use iptables as a firewall and have added a rule to open
csanyipal ha scritto:
On Mon, Apr 09, 2007 at 09:35:50AM -0400, Douglas Allan Tutty wrote:
Just because you opened the port doesn't mean that ssh will listen on
that interface automatically; tell it.
Port 22
Have you any setting for option ListenAddress in /etc/ssh/sshd_config ?
gc :-)
On Mon, Apr 09, 2007 at 07:18:58PM +0200, Franck Joncourt wrote:
First of all, if I were you, I would try to get an access to your
ssh server through 127.0.0.1.
# telnet 127.0.0.1 22
should display SSH banner. Something like this :
###
Trying 127.0.0.1...
Connected to 127.0.0.1.
On Mon, Apr 09, 2007 at 07:04:16PM +0200, gianca wrote:
csanyipal ha scritto:
On Mon, Apr 09, 2007 at 09:35:50AM -0400, Douglas Allan Tutty wrote:
Just because you opened the port doesn't mean that ssh will listen on
that interface automatically; tell it.
Port 22
Have you any
csanyipal:
On Mon, Apr 09, 2007 at 03:53:24PM +0200, Jochen Schulz wrote:
I use iptables as a firewall and have added a rule to open the port 22:
That probably means you are blocking any traffic not explicitly allowed,
correct? Maybe it would help to show us your complete iptables script.
csanyipal ha scritto:
Port 22
Have you any setting for option ListenAddress in /etc/ssh/sshd_config ?
Yes:
#ListenAddress ::
#ListenAddress 0.0.0.0
So there is no limitation.
You said you can ssh localhost, didn't you?
nmap localhost should show port 22 is open.
And can you ssh
On Mon, Apr 09, 2007 at 08:56:40PM +0200, Jochen Schulz wrote:
Hm, weird setup. So you get a non-public IP address on eth0 via DHCP and
a static public address for ppp0?
Exactly!
I do:
$ sudo tcpdump -vv -i ppp0 port 22
tcpdump: listening on ppp0, link-type LINUX_SLL (Linux cooked),
On Mon, Apr 09, 2007 at 09:02:49PM +0200, gianca wrote:
Have you any setting for option ListenAddress in /etc/ssh/sshd_config ?
Yes:
#ListenAddress ::
#ListenAddress 0.0.0.0
So there is no limitation.
You said you can ssh localhost, didn't you?
Yes, I can! :)
nmap localhost should
On Mon, Apr 09, 2007 at 07:33:31PM +0200, csanyipal wrote:
On Mon, Apr 09, 2007 at 07:18:58PM +0200, Franck Joncourt wrote:
$ sudo telnet 127.0.0.1 22
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
SSH-2.0-OpenSSH_4.3p2 Debian-9
^]
Protocol mismatch.
Connection
csanyipal:
On Mon, Apr 09, 2007 at 08:56:40PM +0200, Jochen Schulz wrote:
If you can see either both incoming and outgoing packets or no packets
at all, your setup is fine and someone else is dropping them. If you see
only incoming packets, it's your fault.
Could you try to login again,
On 4/9/07, gianca [EMAIL PROTECTED] wrote:
You said you can ssh localhost, didn't you?
nmap localhost should show port 22 is open.
And can you ssh 85.222.164.13?
Have any other pc in you private lan to try to ssh to yours?
gc :-)
Sorry if I missed it, but has anyone mentioned netstat?
sudo
25 matches
Mail list logo
