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

ZBeacon binds to wrong interface (or no option to specify broadcast interface) #686

Closed
kylemallory opened this issue Mar 8, 2019 · 0 comments

Comments

@kylemallory
Copy link
Contributor

When trying to broadcast beacons on a system with multiple network interfaces, broadcasts are not seen on all interfaces.
It appears that in a multi-network interface environment, ZBeacon will bind to an "automatically selected" interface (per java.nio.DatagramChannel docs). Subsequent broadcasts are only issued on that interface, potentially preventing it from broadcasting beacons on the correct network. Changing the "host" parameter in the ZBeacon constructor only changes the address to which broadcasts are broadcast to, but not the interface to which broadcasts are sent from.
ZBeacon should have a parameter that allows the user to specify the address (and thus interface) from which beacons should originate.

fredoboulo added a commit to fredoboulo/jeromq that referenced this issue Mar 12, 2019
broadcast address.
Solution: Create a builder to specify an optional broadcast address

Fixes zeromq#686
fredoboulo added a commit to fredoboulo/jeromq that referenced this issue Mar 12, 2019
broadcast address.
Solution: Create a builder to specify an optional broadcast address

Fixes zeromq#686
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

No branches or pull requests

1 participant