UDP/Datagram more low level options

[GummyDonut]

Is your feature request related to a problem? Please describe.
I originally posted the problem I ran into here:
#19954
However, to keep a long story short, when sockets are created by default in nodeJS they have the "IP_MULTICAST_ALL" set to on "the socket will receive messages from all the groups that have been joined globally on the whole system." - http://man7.org/linux/man-pages/man7/ip.7.html
Groups this case being multicast groups, and unfortunately for us it is undesired behaviour,
Edit: (Few hours later, I found out my multicast broadcast was disabled, and I was sending directly to the ip, which is not multicast, but the point still stands, why no level options?)

Describe the solution you'd like
Thus we would like a means to change the ipv4 protocol options (http://man7.org/linux/man-pages/man7/ip.7.html) and the options listed in setsockopt for c (http://pubs.opengroup.org/onlinepubs/009695399/functions/setsockopt.html)
from dgram/nodejs, at the moment these options are not exposed at all.

In addition is there are reason these options have not been exposes initially? For us, without the IP_MULTICAST_ALL option exposed, multicast does not behave as intende

Describe alternatives you've considered
Some of the alternatives have been discussed in this issue: #19954
For the moment we are gonna avoid nodejs and create the socket in python as the options are
exposed there https://docs.python.org/3/library/socket.html#socket-objects

[addaleax]

@nodejs/dgram

[Trott]

re-ping @nodejs/dgram Thoughts?

[ronkorving]

I'm personally all for exposing these options. Not having been involved in the original authoring of dgram though, I'm not sure why things are the way they are.

[Trott]

Not having been involved in the original authoring of dgram though, I'm not sure why things are the way they are.

/ping @bnoordhuis maybe?

[mcollina]

I’m +1 for exposing the options, I think it just needs somebody to work on this one.

[oyyd]

It seems that windows doesn't support IP_MULTICAST_ALL directly. (Just FYI.)

[bnoordhuis]

Node.js and libuv only support what can reasonably supported across platforms. As @oyyd mentions, there's no equivalent of IP_MULTICAST_ALL on (for example) Windows, so exposing it directly isn't an option.

However, libuv could call setsockopt(IP_MULTICAST_ALL, 0) to turn off promiscuous mode on Linux, that would make the behavior align with Windows and other Unices. Would that work?

The question then is if there's anyone out there relying (possibly unwittingly) on the existing behavior. We probably won't find out until we change it...

[bnoordhuis]

OP didn't speak up and no one else spoke out pro or contra so I'm closing this out. Let me know if I should reopen.