Description of problem:
I have a DSL router that fails to respond to AAAA records properly:
3.853196 192.168.100.67 -> 192.168.100.1 DNS Standard query A pkgs.fedoraproject.org
3.853344 192.168.100.67 -> 192.168.100.1 DNS Standard query AAAA pkgs.fedoraproject.org
3.897350 192.168.100.1 -> 192.168.100.67 DNS Standard query response A 220.127.116.11
3.903481 192.168.100.1 -> 192.168.100.67 DNS Standard query response
This results in:
ssh: Could not resolve hostname pkgs.fedoraproject.org: Name or service not known
This is the case even with ipv6 completely disabled. Work around is to run "ssh -4 hostname". Other programs like firefox and thunderbird work with ipv6 disabled.
Version-Release number of selected component (if applicable):
See also bug 697149.
This should fix:
--- openssh-5.6p1/sshconnect.c.getaddrinfo 2011-04-25 11:02:00.622740776 -0600
+++ openssh-5.6p1/sshconnect.c 2011-04-25 11:06:39.505254267 -0600
@@ -343,6 +343,7 @@
memset(&hints, 0, sizeof(hints));
hints.ai_family = family;
hints.ai_socktype = SOCK_STREAM;
+ hints.ai_flags = AI_V4MAPPED | AI_ADDRCONFIG;
snprintf(strport, sizeof strport, "%u", port);
if ((gaierr = getaddrinfo(host, strport, &hints, &aitop)) != 0)
fatal("%s: Could not resolve hostname %.100s: %s", __progname,
I see this has been fixed in rawhide, will we see it fixed in F15 soon? Thanks!
please test it and report. I do not put it into f15 before positive feedback.
If you have no way how to test it in rawhide I prepare testing package for you.
Works perfectly. Thanks.
openssh-5.6p1-31.fc15.1 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openssh-5.6p1-31.fc15.1'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
openssh-5.6p1-31.fc15.1 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.