Skip to content
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

added optional 'network interface' address option #1

Merged
merged 1 commit into from
Jan 12, 2015

Conversation

lukaaash
Copy link
Contributor

I was unable to receive some queries and found out that explicitly specifying a multicast interface in socket.addMembership solved this. I'm not sure exactly why (addMembership should add memebership to all valid interfaces by default), but it looks like this is not a rare issue: http://stackoverflow.com/questions/14130560/nodejs-udp-multicast-how-to

Therefore, I believe adding an option to specify the interface argument for the addMembership might be useful. I'm not very familiar with UDP, however - perhaps it would be even better to make it possible to specify multiple interfaces, etc.

@mafintosh
Copy link
Owner

this is great!

mafintosh added a commit that referenced this pull request Jan 12, 2015
added optional 'network interface' address option
@mafintosh mafintosh merged commit 44d929a into mafintosh:master Jan 12, 2015
mafintosh added a commit that referenced this pull request Jan 12, 2015
@mafintosh
Copy link
Owner

Added some docs for this in the README. Released in 1.2.0. Thanks for the patch

@lukaaash
Copy link
Contributor Author

Thanks a lot, that was fast! :-)
By the way, at least on Windows, you can pass the interface's IP address instead of interface name as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants