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

.advertise network interface binding? #26

Open
Freundschaft opened this issue Nov 11, 2016 · 2 comments · May be fixed by #38
Open

.advertise network interface binding? #26

Freundschaft opened this issue Nov 11, 2016 · 2 comments · May be fixed by #38

Comments

@Freundschaft
Copy link

how can I set on which interface the advertise packets should be sent out while using .advertise()?
Currently it seems that node-discover uses only one of the available network interfaces in a multi network interface scenario.
did I miss something or is binding to a specific interface not available?

@wankdanker
Copy link
Owner

Are you specifying a value for address? This is the bind address used here which is just a call to Node's udp bind() method.

If no address is specified then it by default uses 0.0.0.0 which apparently should bind to all interfaces. I've not tested it though. So, I would expect that you should be able to specify no value for address and it should just work. Is the broadcast/mutlicast destination address valid for the subnets of each interface?

@Freundschaft
Copy link
Author

with specification of the bind address it works, unfortunately binding to all interfaces did not work for us, and bound to only one interface, and it was unclear based on which criterion this interface was selected
the bc/mc address was valid for each interface

@aikar aikar linked a pull request Feb 13, 2020 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.

2 participants