Date: Tue, 26 Jul 2022 14:56:52 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 265064] connect(2): unexpected EADDRINUSE when connecting from IPv6 wildcard to IPv4 address Message-ID: <bug-265064-7501-mD41Pih4gu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265064-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-265064-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265064 --- 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 repor= ted 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 f= rom such connect(), considering wildcard-bound socket as partially unbound sock= et as we really have to do new ipv4-bind() over existing ipv6-wildcard-bind. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265064-7501-mD41Pih4gu>