Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1025 - sshd refuses to start on IPv6-capable systems.

Attached to Project: Arch Linux
Opened by Ulrik Mikaelsson (rawler) - Wednesday, 23 June 2004, 21:22 GMT
Last edited by Judd Vinet (judd) - Wednesday, 23 June 2004, 23:20 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.6 Widget
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I'm experiencing problems with starting sshd on my two IPv6-capable machines. /var/log/errors state a line saying sshd was unable to bind to 0.0.0.0:22. The ssh daemon is started, however, but does not answer on connection attemps, neither local nor remote.

Netstat shows the ssh daemon using the port, so clearly it is used somehow.

When I add -4 to /etc/rc.d/sshd it starts up fine, however, but of course IPv6 connection attempts are ignored.

Obviously this is not the expected behaviour, could someone please investigate?
This task depends upon

Closed by  Judd Vinet (judd)
Thursday, 08 July 2004, 17:23 GMT
Reason for closing:  Works for me
Comment by Judd Vinet (judd) - Wednesday, 23 June 2004, 23:20 GMT
Yea, I get that "unable to bind: Address already in use" error everytime I start sshd. But it always starts. Anyone know what's up with this?

See anything useful from debug output?

[root@mars root]# sshd -6Dd
debug1: sshd version OpenSSH_3.8.1p1
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
Generating 768 bit RSA key.
RSA key generation complete.
Comment by Johannes Jordan (FoPref) - Wednesday, 30 June 2004, 13:17 GMT
know that error too, but can tell that sshd successfully listens on both ipv4 and ipv6
Comment by Ulrik Mikaelsson (rawler) - Thursday, 08 July 2004, 16:08 GMT
I've encountered the exact same problem on two different machines, both fresh installed, both in an IPv6-capable network.

However, this week I've successfully installed Arch Linux on two very similar machines, both running on a network without IPv6 capabilities, and here the situation seems to be the same as for Johannes and Judd. Sshd starts and runs, despite an error in the log.

I have no idea whatsoever what was causing this bug, but it seems it's directly related to the networks IPv6 setup. However, strangely and embarrassingly enough, today I wanted to experiment and see if sshd would listen to IPv6-connections properly on port 22, and today I discovered that it now listens properly on IPv4-connections as well, without the -4 modification.

Sorry for the hazzle. I don't know what was causing the problem, and chances are we'll never know.
Comment by Judd Vinet (judd) - Thursday, 08 July 2004, 17:22 GMT
No worries... Glad it works, even though we don't know what's changed.

Let me know if you see the problem again. I'll close this bug.

Loading...