Description of problem: I'm facing a situation where my DSL router fails DNS responses when requested for AAAA records. I have disabled ipv6 completely on my system, but certain python calls still ask for AAAA records. The python calls should be using (AI_V4MAPPED | AI_ADDRCONFIG) for flags to disable AAAA record requests on non-ipv6 capable systems (this is the default for getaddrinfo() with null hints). Many other clients already do this, including firefox and thunderbird. Example: socket.py:553 in create_connection() calls: getaddrinfo(host, port, 0, SOCK_STREAM) results in a getaddrinfo() call in sockemodule.c with flags=0. My sense is that if flags is not explicitly passed in the python getaddrinfo() it should be set to (AI_V4MAPPED | AI_ADDRCONFIG) by default, although socket.py could be modified to pass those flags as well. Version-Release number of selected component (if applicable): python-2.7.1-7.fc15.i686
Please don't use AI_ADDRCONFIG anywhere by default. It breaks 'localhost', '127.0.0.1', link-local IPv6 and other stuff when you're not connected to the global internet. See: http://sourceware.org/bugzilla/show_bug.cgi?id=12377 http://sourceware.org/bugzilla/show_bug.cgi?id=12398 Let's look for a proper solution.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #0) > The python calls should be using (AI_V4MAPPED | AI_ADDRCONFIG) It's nonsence to use AI_V4MAPPED with AF_UNSPEC, see: http://sourceware.org/bugzilla/show_bug.cgi?id=14415 > My sense is that if flags is not explicitly passed in the python > getaddrinfo() it should be set to (AI_V4MAPPED | AI_ADDRCONFIG) by default, > although socket.py could be modified to pass those flags as well. We are going to fix AI_ADDRCONFIG so that it actually works, then it is ok to use it in applications. But getaddrinfo is used for so many other applications than just connect(), that making AI_ADDRCONFIG default is a bad idea, see: http://sourceware.org/bugzilla/show_bug.cgi?id=14966
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.