Does not work when options.interface is specified

[moky80]

When options.interface is specified:
require("multicast-dns")({interface:"192.168.1.1"})
it didn't work (no error, just no services found) while in the very same system omitting the options worked. The system actually has only one interface 192.168.1.1.

[nriley]

I ran into something similar in a situation where I did need to use options.interface. options.interface is used in two places — I am not sure it needs to be used in both.

It is used not only to override the default interface (automatic selection of default interface does not do great in complex network environments — at least in my case it generally picks the wrong interface) but also to bind. If I do specify an interface I get EADDRINUSE, I guess because I also have mDNSResponder running. I ended up just removing the reference to opts.interface from bind and it seems to work just fine — dns-sd shows me that multicast-dns has registered on the correct interface and bind works just as it did if I hadn't specified options.interface.

The change I made was specifically to comment out opts.interface here:

    socket.bind(port, undefined /* opts.interface */, function () {

[RangerMauve]

I just ran into this issue and @nriley 's solution resolved it.

@mafintosh Would you be open to a PR that adds a new localAddress option which will be used in .bind() instead of opts.interface? This would be a major version change.

[pascalStm]

I also have a problem that, if I parameter interface with my ip address to select the right interface, I receive multicast udp packets with this address, I must remove "opts.interface" from the bind command to receive all multicast udp packets of all my clients

by putting "ip" instead of "opts.interface" it works for the multicast

[pipex]

If anyone is still wondering about this after one year like me :p

It seems that the latest version of the package adds a bind to options that is used as address in the socket.bind() call. Setting it to 0.0.0.0 seems to fix the problem.

[ke4nec]

If anyone is still wondering about this after one year like me :p

It seems that the latest version of the package adds a bind to options that is used as address in the socket.bind() call. Setting it to 0.0.0.0 seems to fix the problem.

Thanks!
require("multicast-dns")({bind: "0.0.0.0", interface:"192.168.1.1"});

[otaviojacobi]

A complement to this, 0.0.0.0 might not be the most secure interface to bind to (as it will accept incoming connection from any address). An alternative, that seems to work file for me is binding to the mDNS default address 224.0.0.251

edit: It does not seem to work on mac