yahoo-eng-team team mailing list archive

[yangjianfeng <1831706@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When the packets which from remote qr-* port enter `br-int` bridge, their `in_port` field will become to `patch-tun`(vxlan network) or `int-br-vlan`(vlan network), the way will result in these packets mustn't be processed by ovs flow `NORMAL` action, because of the `NORMAL` action will result in the ovs bridge update `fdb` table, but these packets `in_port` field is not correct, so ovs bridge will record an error MAC forward entry. Although, the current design about DVR is OK(It use `outpt` action for these packets). But, I think we can modify these packets' `in_port` field as local qr-* so that we can simplify the flow tables. 
For example, the below flows can be deleted:
  table=60, priority=4,dl_vlan=288,dl_dst=fa:16:3e:2d:d7:85 actions=strip_vlan,output:"tap0500d7e2-87"
  table=60, priority=4,dl_vlan=287,dl_dst=fa:16:3e:bc:ec:67 actions=strip_vlan,output:"test-vlan02"
  table=60, priority=4,dl_vlan=287,dl_dst=fa:16:3e:bf:0c:35 actions=strip_vlan,output:"tapbcd046ef-26"
  table=60, priority=4,dl_vlan=287,dl_dst=fa:16:3e:b6:03:cd actions=strip_vlan,output:"test-vlan"
  table=60, priority=4,dl_vlan=203,dl_dst=fa:16:3e:8f:88:bc actions=strip_vlan,output:"tap2610c99a-52"
I think the below flow is enough if these packets' `in_port` field be modified as appropriate value.
  table=60, priority=3 actions=NORMAL

One more thing, I think it can be a resolution about the patch:
https://review.opendev.org/#/c/639009

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1831706

Title:
  [DVR] Modify `in_port` field of packets which from remote qr-* port

Status in neutron:
  New

Bug description:
  When the packets which from remote qr-* port enter `br-int` bridge, their `in_port` field will become to `patch-tun`(vxlan network) or `int-br-vlan`(vlan network), the way will result in these packets mustn't be processed by ovs flow `NORMAL` action, because of the `NORMAL` action will result in the ovs bridge update `fdb` table, but these packets `in_port` field is not correct, so ovs bridge will record an error MAC forward entry. Although, the current design about DVR is OK(It use `outpt` action for these packets). But, I think we can modify these packets' `in_port` field as local qr-* so that we can simplify the flow tables. 
  For example, the below flows can be deleted:
    table=60, priority=4,dl_vlan=288,dl_dst=fa:16:3e:2d:d7:85 actions=strip_vlan,output:"tap0500d7e2-87"
    table=60, priority=4,dl_vlan=287,dl_dst=fa:16:3e:bc:ec:67 actions=strip_vlan,output:"test-vlan02"
    table=60, priority=4,dl_vlan=287,dl_dst=fa:16:3e:bf:0c:35 actions=strip_vlan,output:"tapbcd046ef-26"
    table=60, priority=4,dl_vlan=287,dl_dst=fa:16:3e:b6:03:cd actions=strip_vlan,output:"test-vlan"
    table=60, priority=4,dl_vlan=203,dl_dst=fa:16:3e:8f:88:bc actions=strip_vlan,output:"tap2610c99a-52"
  I think the below flow is enough if these packets' `in_port` field be modified as appropriate value.
    table=60, priority=3 actions=NORMAL

  One more thing, I think it can be a resolution about the patch:
  https://review.opendev.org/#/c/639009

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1831706/+subscriptions