You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
mgheorghe
changed the title
why is overlay dest mac 0000000000 valid for outbound traffic
why is overlay dest mac 0000000000 valid for outbound traffic for BMv2
Jun 4, 2024
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 will capture and check whether it works when exiting bmv2.
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: