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.

Sign up for GitHub

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

Jump to bottom

IPv6 link-local addresses lose interface information #51

Open
Kriechi opened this issue Feb 18, 2019 · 2 comments · May be fixed by #117
Open

IPv6 link-local addresses lose interface information #51

Kriechi opened this issue Feb 18, 2019 · 2 comments · May be fixed by #117

Comments

@Kriechi
Copy link

Kriechi commented Feb 18, 2019

As a client using the browse API, I receive a list of IPv6 address in the ServiceEntry.
An IPv6 link-local address is only useful when the corresponding interface (e.g., eth1) is known as well. The ServiceEntry contains link-local IPv6 address, but the interface name is missing.

Is there a way to retrieve the interface name for each IPv6 address (link-local ones at least)?
@makon
Copy link

makon commented Jan 25, 2021

Have you found a solution to the problem?

@Kriechi
Copy link
Author

Kriechi commented Jan 25, 2021

@makon not really - I ended up brute-forcing it by simply trying all interfaces with this IP - until one gave a valid response to my endpoint.

@marten-seemann marten-seemann mentioned this issue Dec 7, 2023
Open
@jclab-joseph jclab-joseph linked a pull request Dec 7, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: support link-local address jclab-joseph/zeroconf
2 participants
@Kriechi @makon