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

Connecting to Multiple Interfaces is Broken #54

Open
stephenrauch opened this issue May 1, 2016 · 0 comments
Open

Connecting to Multiple Interfaces is Broken #54

stephenrauch opened this issue May 1, 2016 · 0 comments
Labels

Comments

@stephenrauch
Copy link
Collaborator

stephenrauch commented May 1, 2016

When connecting to multiple interfaces, this library is currently treating those interfaces as the same network. This is very broken, as any single broadcast domain must be treated independently. Any service name is only unique on a single broadcast domain and to assume otherwise does not work. If connecting on multiple interfaces, then the name spaces must not be combined. (there are other issues with this approach, but one show stopper is enough, I won't bother describing others)

Workaround:

This library should always have a specific interface address specified when initializing a ZeroConf() instance on a multi-homed host. The only exception would be when the ZeroConf() instance will only be used for browsing for services, and then only if connecting on a multi-homed host in which only one interface can have zeroconf services.

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

No branches or pull requests

1 participant