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

2022-07-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265064 --- Comment #11 from Mike Karels --- Created attachment 235512 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235512&action=edit alternative patch I'd prefer to keep the two patches separate, in part because I don't know enough

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

2022-07-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265064 --- Comment #10 from f...@cantconnect.ru --- Made a differential revision for this: https://reviews.freebsd.org/D35967 -- You are receiving this mail because: You are the assignee for the bug.

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

2022-07-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265064 --- Comment #9 from f...@cantconnect.ru --- (In reply to Mike Karels from comment #8) NULL cred is to fix bug 210276. It it not wrong in any case, it means "prevent reusing busy ports regardless of which creds they are using". Obtained stru

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

2022-07-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265064 --- Comment #8 from Mike Karels --- (In reply to firk from comment #7) Thanks for the new patch. That's simpler (less invasive) than the patch I was working on, and I can simplify it just a little more. One question: why pass NULL for cr

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

2022-07-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265064 --- Comment #7 from f...@cantconnect.ru --- Created attachment 235507 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235507&action=edit patch to fix connect EADDRINUSE (In reply to Mike Karels from comment #6) Ok, I misunderstoo