Bug 155012

Summary:	sshd listens only on ipv6
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	peter czanik <peter>
Component:	Network	Assignee:	Petr Ostadal <postadal>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Blocker
Priority:	P5 - None	CC:	suse-beta
Version:	Beta 6
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	content of /etc/ssh/ssh* output from ssh -vvv localhost output from sshd -ddd

Description peter czanik 2006-03-03 15:31:26 UTC

Tested on both i386 and PPC: the sshd server listens only on ipv6. It has to be forced in /etc/ssh/sshd_config with 'AddressFamily inet' to accept connections on ipv4.

Comment 1 Michael Gross 2006-03-03 16:27:21 UTC

Raising severity to BLOCKER.

Comment 2 Petr Ostadal 2006-03-06 09:44:18 UTC

send me the log from sshd -ddd ans ssh -vvv and /etc/ssh/ssh*_config
No one had this problem in betas.

Do you have disabled rcSuSEfirewall2 or enabled ssh port in SuSEfirewall?

Comment 3 peter czanik 2006-03-06 10:33:43 UTC

Tested now on my laptop, and that does not have this problem. It has rcSuSEfirewall2 disabled.

My other i386 installation is currently deleted (due to kernel problems reverted to stable 10.0).

My PPC machine has rcSuSEfirewall2 enabled. But even with rcSuSEfirewall2 sshd only binds to ipv6. I'll attach files now.

Comment 4 peter czanik 2006-03-06 10:34:37 UTC

Created attachment 71316 [details]
content of /etc/ssh/ssh*

Comment 5 peter czanik 2006-03-06 10:36:10 UTC

Created attachment 71317 [details]
output from ssh -vvv localhost

Comment 6 peter czanik 2006-03-06 10:36:44 UTC

Created attachment 71318 [details]
output from sshd -ddd

Comment 7 peter czanik 2006-03-06 11:14:17 UTC

Checked on an other i386 machine, rcSuSEfirewall2 disabled, and ssh binds only to ipv6.

Comment 8 Petr Ostadal 2006-03-06 16:32:31 UTC

I can't reproduce it on i386 and x86_64, could you append strace -f of sshd and ssh?

Comment 9 peter czanik 2006-03-06 19:35:54 UTC

Strange. I can't reproduce it now either, everything works OK. But you see the logs, that ssh was only able to connect using ipv6. I'll make a new install later this week, and see what happens.
For now I leav it 'needinfo'.

Comment 10 Petr Ostadal 2006-03-07 06:53:26 UTC

Yes logs say that is binding port on local (:: or 127.0.0.1), when you try bind ipv4, it fails, therefore we remove ipv4 binding when ipv6 binding successed and sshd listen on both local addreesses.

But the log from ssh -vvv was strange, when you can reproduce it again with strace, it would help me to reslove your problem. Now I close this blocker bug as invalid, please reopen it when you reproduce it again.