Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm not a server guy, and my network skills are a little rusty, so this may be a simple question. On a brand-new archlinux machine, I setup sshd, and told it to bind to Once it was running, I used netstat to confirm that it was listening on *:9223.

Running "ssh -p 9223 localhost" connected fine, but remote connections failed. I then tried "ssh -p 9223 [REMOTE_IP]" on the server, and this failed.

After trying to find the source of the problem, and failing, I set sshd to bind to [REMOTE_IP], and suddenly everything worked.

So my question is, what would cause a socket bound to to ignore connections from the ip address of the eth0 interface?

share|improve this question
What was the error message when you tried "ssh -p 9223 remote_ip"? – Khaled Dec 4 '10 at 7:59
up vote 6 down vote accepted

The case might be that your eth0 interface is using IPv6 protocol. When you configure ssh server with ListenAddress in /etc/ssh/sshd_config you turned off IPv6 protocol. netstat then have only one entry for ssh starting with tcp. Add a line ListenAddress :: to also listen on tcp6. netstat should report you two entries for ssh server one on tcp6 :::9223 and one on tcp

share|improve this answer
That's it. Thanks. – Mike Douglas Dec 4 '10 at 8:06
Glad I could help. – Casual Coder Dec 4 '10 at 8:07
How is IPv6 related? O_o – poige Feb 3 '11 at 3:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.