-
Notifications
You must be signed in to change notification settings - Fork 730
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
Add proxy support to the neighbor functions #149
Conversation
} | ||
} | ||
|
||
// TODO: seems not working because of cache |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably should fix this todo before merging
Thanks for adding this. One other thought. The iproute2 package allows you to list proxies separately. I'm wondering if we really want to include proxies by default or if it should be two separate commands? NeighList and NeighProxyList. Thoughts? |
I actually was thinking the same thing after I submitted the PR. Plus, no chance of breaking someone's current user cases. I'll make the changes and update the PR. |
- Don't require a MAC address for a neighbor proxy - Include proxies in the list of neighbors Signed-off-by: Zvi "CtrlZvi" Effron <viz+GitHub@flippedperspective.com>
The condition to demand a lladdress for neigh.Flags != NTF_PROXY is just buggy, since there are various other flags such as NTF_USE, NTF_EXT_MANAGED, etc where this is not required. Besides, the kernel handles this internally anyway if it demands a NDA_LLADDR attribute. Simply get rid of the NTF_PROXY flag/condition since it's wrong. Fixes: d710fba ("Add proxy support to the neighbor functions (vishvananda#149)") Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
The condition to demand a lladdress for neigh.Flags != NTF_PROXY is just buggy, since there are various other flags such as NTF_USE, NTF_EXT_MANAGED, etc where this is not required. Besides, the kernel handles this internally anyway if it demands a NDA_LLADDR attribute. Simply get rid of the NTF_PROXY flag/condition since it's wrong. Fixes: d710fba ("Add proxy support to the neighbor functions (#149)") Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
The condition to demand a lladdress for neigh.Flags != NTF_PROXY is just buggy, since there are various other flags such as NTF_USE, NTF_EXT_MANAGED, etc where this is not required. Besides, the kernel handles this internally anyway if it demands a NDA_LLADDR attribute. Simply get rid of the NTF_PROXY flag/condition since it's wrong. Fixes: d710fba ("Add proxy support to the neighbor functions (vishvananda#149)") Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
The condition to demand a lladdress for neigh.Flags != NTF_PROXY is just buggy, since there are various other flags such as NTF_USE, NTF_EXT_MANAGED, etc where this is not required. Besides, the kernel handles this internally anyway if it demands a NDA_LLADDR attribute. Simply get rid of the NTF_PROXY flag/condition since it's wrong. Fixes: d710fba ("Add proxy support to the neighbor functions (vishvananda#149)") Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
The condition to demand a lladdress for neigh.Flags != NTF_PROXY is just buggy, since there are various other flags such as NTF_USE, NTF_EXT_MANAGED, etc where this is not required. Besides, the kernel handles this internally anyway if it demands a NDA_LLADDR attribute. Simply get rid of the NTF_PROXY flag/condition since it's wrong. Fixes: d710fba ("Add proxy support to the neighbor functions (vishvananda#149)") Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Zvi "CtrlZvi" Effron viz+GitHub@flippedperspective.com