-
Notifications
You must be signed in to change notification settings - Fork 94
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
why is overlay dest mac 0000000000 valid for outbound traffic for BMv2 #583
Comments
DST MAC s/be in CA/PA mapping. Look at packet processing log. Overlay DST MAC = all 0's, yet bmv2 still forwards packet. Once exiting the pipeline, it s/be changed. Probably not in ENI address table. The reason this works: we don't know DST MAC at first. We have fake/dummy MAC (all 0's or other MACs), and this will work. If the MAC stays as all 0's, then we have a bug. Perhaps P4 code is not behaving as desired. |
@mgheorghe to check this given the info above |
hi @mgheorghe - did you happen to have a chance to test this? TY! |
hi @vikumarks and @mgheorghe - do we still need this one? TY! |
hi @vikumarks and @mgheorghe - do we still need to test this one? |
why dest mac can be 00000000 ?
i looked at https://github.com/sonic-net/DASH/blob/main/documentation/general/dash-sai-pipeline-packet-flow.md#59-matching-stages-and-metadata-publishing and i'm not clear if dst mac needs to match the "outbound_ca_to_pa_#eni1nsg0acl0i0A"
The text was updated successfully, but these errors were encountered: