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

in6_neighbor cache doesn't properly account for link-local next-hops #236

Open
dkg opened this issue Jan 29, 2018 · 0 comments
Open

in6_neighbor cache doesn't properly account for link-local next-hops #236

dkg opened this issue Jan 29, 2018 · 0 comments

Comments

@dkg
Copy link

dkg commented Jan 29, 2018

Depending on how route advertisements are configured, it's possible that the IPv6 next-hop could be on a link-local address (i.e. fe80:*). Doing a lookup based on that address alone is a mistake, seince there could be multiple links on the local machine, and link-local addresses need to be identified per-interface, not per-machine.

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