[issue36208] AsyncIO V4MAPPED addresses with V6ONLY.

Jan Seeger added the comment: The intention for V4MAPPED is to allow "single-stack" usage of V4 and V6 addresses (or am I misunderstanding the purpose of the V4MAPPED socket option here?). The application only handles V6 addresses, and the system transparently converts from mapped addresses t

[issue36208] AsyncIO V4MAPPED addresses with V6ONLY.

Giampaolo Rodola' added the comment: 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 getpeernam

[issue36208] AsyncIO V4MAPPED addresses with V6ONLY.

STINNER Victor added the comment: See also bpo-35934. -- nosy: +giampaolo.rodola, vstinner ___ Python tracker ___ ___ Python-bugs-l

[issue36208] AsyncIO V4MAPPED addresses with V6ONLY.

New submission from Jan Seeger : I'm working with aiocoap, which uses the AI_V4MAPPED flag to use IPv4-mapped addresses for dual-stack support. When trying to run on Windows, creating a connection fails, because the socket option IPV6_V6ONLY is set to true per default on Windows, whereas the