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

Stale multicast address #17

Open
wasnotrice opened this issue Sep 25, 2019 · 0 comments · May be fixed by #16
Open

Stale multicast address #17

wasnotrice opened this issue Sep 25, 2019 · 0 comments · May be fixed by #16

Comments

@wasnotrice
Copy link

wasnotrice commented Sep 25, 2019

When an interface has been changed to a different network, it can use a stale multicast address, resulting in an EADDRNOTAVAIL error.

Expected: the interface uses the multicast address for the current network
Actual: the interface uses the multicast address for the first network it saw

Steps to reproduce:

  1. Connect to a wifi network
  2. Start a dnssd browser
  3. Stop the dnssd browser
  4. Connect to a different wifi network
  5. Start a dnssd browser

An error like this is thrown:

Error: setMulticastInterface EADDRNOTAVAIL
at Socket.setMulticastInterface (dgram.js:566:11)
at Socket.eval (webpack:///./node_modules/dnssd/lib/NetworkInterface.js?:238:41)
at Socket.emit (events.js:182:13)
at startListening (dgram.js:128:10)
at state.handle.lookup (dgram.js:249:7)
at process._tickCallback (internal/process/next_tick.js:63:19)

@wasnotrice wasnotrice linked a pull request Sep 25, 2019 that will close this issue
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 a pull request may close this issue.

1 participant