-
Notifications
You must be signed in to change notification settings - Fork 373
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 finding destination MAC by IP in traceflow #981
Conversation
Thanks for your PR. The following commands are available:
These commands can only be run by members of the vmware-tanzu organization. |
/test-all |
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.
LGTM
Can one of the admins verify this patch? |
The test was incorrect (traffic is dropped by an ingress policy rule). However, this only became apparent after antrea-io#981 was merged and the DMAC of the Traceflow packet started being set correctly.
The test was incorrect (traffic is dropped by an ingress policy rule). However, this only became apparent after #981 was merged and the DMAC of the Traceflow packet started being set correctly.
The test was incorrect (traffic is dropped by an ingress policy rule). However, this only became apparent after antrea-io#981 was merged and the DMAC of the Traceflow packet started being set correctly.
Find the destination MAC in traceflow controller by destination IP via local cache.
Solved a TODO in traceflow. Testing accepted on local machine.