https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #12 from Jason A. Donenfeld ---
Terrific!
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.or
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
Mark Johnston changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #10 from Jason A. Donenfeld ---
Hey Mark -- wondering if the latest port, v0.0.20210428, solves this for you.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #9 from Jason A. Donenfeld ---
Should now be released with
https://cgit.freebsd.org/ports/commit/?id=4933972df03262847a7609001138597495cd72d5
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
Mark Johnston changed:
What|Removed |Added
Status|New |In Progress
--- Comment #8 from Ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #7 from Jason A. Donenfeld ---
> Is it possible to have wg_socket_bind() succeed if it's able to bind at least
> one of the sockets, assuming that sobind() returns EADDRNOTAVAIL for the
> other?
Nice idea. That seems like a s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #6 from Mark Johnston ---
(In reply to Jason A. Donenfeld from comment #5)
Indeed, I'm not really sure why we prohibit bind() if no addresses from the
corresponding family are assigned. That behaviour appears to predate FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #5 from Jason A. Donenfeld ---
Woof, I see what you mean now. That problem also applies to v4 sockets too!
Basically if there's no interface with an address in the family, then bind
fails. We could check for ret==EADDRNOTAVAIL a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #4 from Mark Johnston ---
(In reply to Jason A. Donenfeld from comment #3)
I can't quite see how. The problem is basically that in wg_socket_bind(), the
sobind() call for the v6 socket will fail if the VNET does not have a v6
a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
Jason A. Donenfeld changed:
What|Removed |Added
CC||ja...@zx2c4.com
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
--- Comment #2 from Kyle Evans ---
(In reply to Kyle Evans from comment #1)
He pointed out that it was already fixed and our upstream base just a bit too
old; rebased forward and my secondary nit is gone.
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
Kyle Evans changed:
What|Removed |Added
CC||kev...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254212
Bug ID: 254212
Summary: can't initialize an if_wg interface with IPv6 disabled
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
13 matches
Mail list logo