-
Notifications
You must be signed in to change notification settings - Fork 367
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
[Windows] Use uplink MAC as source if packet is output to uplink #3516
Conversation
With noEncap mode the Pod packet to remote Pod/Node is output to the uplink interface directly. This change modifies the source MAC with the uplink interface's MAC, so that it doesn't require hybrid configurations on the host interface. Signed-off-by: wenyingd <wenyingd@vmware.com>
/test-windows-all |
/test-windows-e2e |
Codecov Report
@@ Coverage Diff @@
## main #3516 +/- ##
==========================================
- Coverage 65.58% 55.79% -9.79%
==========================================
Files 277 391 +114
Lines 27264 52463 +25199
==========================================
+ Hits 17881 29272 +11391
- Misses 7483 20756 +13273
- Partials 1900 2435 +535
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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
/test-windows-all |
/test-windows-conformance |
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.
@XinShuYang not only promiscuous mode, could you check whether it can work without enabling "MAC Address Changes" and "Forged transmits"? I think this patch is irrelavant to promiscuous mode, which is not required at all from the begining. |
@wenyingd without this patch, vsphere and cloud platforms need to disable MAC check to work around, could you backport it to previous releases starting from 1.2 as well? |
@tnqn I understand we need to disable "Forged transmits" to drop packets with noneffective MAC address, could you explain why it is necessary to disable "MAC Address Changes" for this PR? |
@XinShuYang Not only for this PR, I think in theory we don't require any of these options to be configured but all of them were required to be set to specific values due to either misunderstanding or implementation bug. My point is to ensure everything works as expected, then we can remove these restrictions from document (if there is any) to clarify. |
@tnqn Thanks for the explanation, I will retest it with new setup. |
/test-windows-all |
/test-windows-e2e |
With noEncap mode the Pod packet to remote Pod/Node is output to the
uplink interface directly. This change modifies the source MAC with the
uplink interface's MAC, so that it doesn't require hybrid configurations
on the host interface.
Fixes #3505
Signed-off-by: wenyingd wenyingd@vmware.com