➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author giampaolo.rodola
Recipients asvetlov, giampaolo.rodola, jeeger, vstinner, yselivanov
Date 2019-03-06.12:54:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551876879.65.0.520095436705.issue36208@roundup.psfhosted.org>
In-reply-to
Content 
I'm not sure I understand the issue, but setting IPV6_V6ONLY to 0 by default is not an option because asyncio wants to serve IPv4 and IPv6 with 2 distinct sockets on purpose. The reason for that is because when an IPv4 connection occurs we want getpeername/getsockname to return '127.0.0.1' instead of '::ffff:127.0.0.1'.

Also, IPV6_V6ONLY = 1 is set by default on all platforms. It is not set on Windows because IPPROTO_IPV6 constant is missing due to issue29515, but that doesn't matter because IPV6_V6ONLY = 1 is already the default on Windows. As for Linux, /proc/sys/net/ipv6/bindv6only shouldn't matter because setting the option in Python is supposed to overwrite what /proc/sys/net/ipv6/bindv6only dictates.

With that said, what's your use case exactly? Why does your test script uses AF_INET6 and an IPv4 address?
History
Date User Action Args
2019-03-06 12:54:39giampaolo.rodolasetrecipients: + giampaolo.rodola, vstinner, asvetlov, yselivanov, jeeger
2019-03-06 12:54:39giampaolo.rodolasetmessageid: <1551876879.65.0.520095436705.issue36208@roundup.psfhosted.org>
2019-03-06 12:54:39giampaolo.rodolalinkissue36208 messages
2019-03-06 12:54:39giampaolo.rodolacreate