multicast dgram on non-default interface #3232

Closed
sixtus opened this Issue May 7, 2012 · 4 comments

Comments

Projects
None yet
2 participants

sixtus commented May 7, 2012

multicast dgrams really get confused once there are multiple interfaces involved and even worse, when trying to send multicast messages on the non-default interface.

it's so bad, I can't even give you a matrix of what combination leads to what result, but it's a weird combination of not hearing anything, sending on the wrong interface, and receiving on the wrong interface.

Fact:

  • dgram.send() can not determine the interface itself (as multicast can happen on any interface)
  • passing an address to bind() makes dgram stop hearing its own multicast messages
Owner

bnoordhuis commented May 7, 2012

Duly noted. I'll take patches or test cases, preferably both. :-)

sixtus commented May 8, 2012

A test case is really hard to write, as you need to set up networking correctly.

Instead, I tried to demo the strange behavior in this gist: https://gist.github.com/2633625

Owner

bnoordhuis commented May 20, 2012

Thanks, I think I see what you mean. I don't think it's a bug in node or libuv, though. I suspect that you'd see the same behavior with a program written in pure C.

Owner

bnoordhuis commented Oct 28, 2013

No follow-up, closing.

bnoordhuis closed this Oct 28, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment