[Bug 265064] connect(2): unexpected EADDRINUSE when connecting from IPv6 wildcard to IPv4 address

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265064

--- Comment #5 from firk@cantconnect.ru ---
(In reply to Mike Karels from comment #2)

No, wildcard ipv6 bind() shouldn't fail just because ipv4 port for the
specifiec ipv4 address is busy. I'm not sure how this error should be reported
to userland, but it surely shouldn't be triggered until we try to connect() to
ipv6-wrapped ipv4 address. May be it will be okay to return EADDRNOTAVAIL from
such connect(), considering wildcard-bound socket as partially unbound socket
as we really have to do new ipv4-bind() over existing ipv6-wildcard-bind.

-- 
You are receiving this mail because:
You are the assignee for the bug.