-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
deps: add support for interface broadcast addresses #23438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
deps: add support for interface broadcast addresses #23438
Conversation
Hi! Could you open a pull request against https://github.com/libuv/libuv/ with the libuv changes first? We generally avoid doing our own patches on top of libuv releases. (The libuv part also looks semver-major, which may be a challenge on its own.) |
4e8f315
to
fe4e223
Compare
There are existing discussions in libuv/libuv#158 and libuv/libuv#1371 about extending libuv's support for network interfaces. |
Done. See libuv/libuv#2033. |
fe4e223
to
d2111b4
Compare
I saw those, and from what I can tell they deal with larger architectural issues, like getting addresses for non-IP families, interfaces with no layer-3 configuration, etc. That's a bit orthogonal to what I'm doing here. |
8dc06d4
to
e219e50
Compare
I managed to get this ( |
Currently it returns the empty string |
8ae28ff
to
2935f72
Compare
how do we move forward on this one? |
heya @pprindeville! any chance you're going to pick this up again? No worries if not. If not, anyone else? If not... we should probably close this out. |
I can try, but I'm not entirely sure what the blocker is. What do I need to do that I haven't done, or redo, in order to advance this? |
@pprindeville it looks like there's an open question (similar to mine!) in libuv/libuv#2033 (review). I'm assuming that if those can get merged in, this can get merged in if I'm reading the PRs correctly. So, ideally, finishing that PR up then coming back to this one once that lands :) |
@pprindeville I think the PR that was blocking was merged, or I am wrong? |
This issue/PR was marked as stalled, it will be automatically closed in 30 days. If it should remain open, please leave a comment explaining why it should remain open. |
@pprindeville This PR hasn't had any activity for a while (and the stalebot isn't up), so I've marked this as |
Yeah, after 6 years, whatever expectation of progress I had has dwindled. |
e219e50
to
dd745f2
Compare
Not using the correct broadcast address in applications can cause disasterous results. Rather than letting the programmer guess at the broadcast address and try to derive it correctly, allow him to query the system instead for the correctly configured state. Fixes: nodejs#23437 Depends-on: libuv/libuv#2033
dd745f2
to
840cc89
Compare
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes