[dgram]socket.addMembership() does not add membership to every interface

[tberthe]

I have 3 network interfaces on my computer (2 ethernet + 1 virtual for VirtualBox) connected to different independent networks.
With Wireshark I inspected the packets generated when calling socket.addMembership() without specifying a multicast interface and I noticed the Membership Report / Join group request is only sent on 1 interface (the default route) but not on the others.

Here is a simple program demonstrating the problem:

var dgram = require('dgram');
var s = dgram.createSocket('udp4');

var MULTICAST_IP = "225.0.0.1"

s.bind(8001, function() {
  s.addMembership(MULTICAST_IP);
  console.log("listening on all addresses");
});

s.on("message", function (msg, rinfo) {
  console.log("server got: " + msg + " from " +
  rinfo.address + ":" + rinfo.port);
});

But if I specify every interface when calling socket.addMembership(), the proper Membership Report / Join group requests are sent and the multicast messages sent on any network is received.

Both network interfaces are up and support broadcast and multicast, they have the following IP:
-enp2s0: 10.80.10.28 (default route)
-enp6s0: 172.20.3.26
-virbr0: 192.168.122.1 (NAT / virtual box)

The problem has been reproduced with io.js 1.6.4 and 2.0.1 (linux x64).

[Trott]

Any chance you know if you're still experiencing this problem or not? I suspect that if you are, that the issue is in libuv but I'm having trouble replicating. What's the Wireshark filter you are using?

[jsdario]

I am still experiencing this problem ✋

When I type deamon.addMembership('239.0.16.18') I can receive messages from the ethernet interface (with ip 172.27.64.47), however if I force it on the wlan0 one, it works deamon.addMembership('239.0.16.18', '192.168.0.1').

So by the moment I have to bind to all interfaces in a loop.

[igierard]

I also experienced this having it only bind to one interface. On windows 10. Seemed to only bind to the VirtualBox host interface.