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

Multiple interfaces: associate IPs with interface #12

Closed
grandcat opened this issue Mar 2, 2017 · 2 comments
Closed

Multiple interfaces: associate IPs with interface #12

grandcat opened this issue Mar 2, 2017 · 2 comments

Comments

@grandcat
Copy link
Owner

grandcat commented Mar 2, 2017

If there are multiple interfaces, all IPs are merged together and send as a list of addresses to all clients.
As some addresses from one interface may not be reachable via an other interface, outgoing packets have to be personalized by egress interface.

@grandcat grandcat added this to ToDo in Future Releases Mar 2, 2017
@tmm1
Copy link
Contributor

tmm1 commented Apr 12, 2017

I've run into this as well and its pretty annoying.

Do you know if there's any API in golang to tell which interface the packet came from?

@tmm1
Copy link
Contributor

tmm1 commented Apr 13, 2017

Never mind, I found the answer here: http://stackoverflow.com/questions/35442824/how-to-read-both-input-interface-and-remote-socket-address-for-an-udp-datagram-r

I'll see if I can start a PR.

@grandcat grandcat moved this from ToDo to In Progress in Future Releases Apr 23, 2017
@grandcat grandcat moved this from In Progress to Done in Future Releases May 2, 2017
@grandcat grandcat closed this as completed May 2, 2017
cpuchip pushed a commit to cpuchip/zeroconf that referenced this issue Jul 27, 2022
cpuchip pushed a commit to cpuchip/zeroconf that referenced this issue Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants