On 3/6/24 08:54, Zhangweiwei via discuss wrote:
> Hi,
> 
> I set tag 0 on port tapVm72and tapVm71, and then send ping packets with vlan
> 100 from tapVm72to tapVm71. But ovs-tcpdump cannot capture any packets with
> vlan on tapVm72. It seems that vlan check is failed in mirror_packet(), 
> because
> tapVm72 is an access port and the vlan packets are dropped. This is not 
> reasonable
> because OVS does not use NORMAL forward. When using custom OpenFlow tables, 
> mirror
> action should not consider tag configuration.

I don't think that is related to tapVm72 being an access port.
Could you, please, run ovs-appctl ofproto/trace on a packet
arriving from tapVm72 ?

Note that since mitapVm72 is not in vlan 0, mirrored traffic will
have both vlan tags pushed to the packet.  For this to work the
vlan-limit configuration should be 2 or 0 (unlimited).  Default
value is 1 and that may be one reason why packets are not delivered
to mitapVm72.  ofproto/trace should be able to confirm if that is
the case.

Best regards, Ilya Maximets.

> 
> 1、ovs version: 3.2.1
> 2、Bridge
> [root@localhost openvswitch-3.2.1]# ovs-vsctl show
>     Bridge vds1-br
>         Controller "tcp:172.20.66.228:6633"
>             is_connected: true
>         Controller "tcp:172.20.66.229:6633"
>             is_connected: true
>         fail_mode: secure
>         datapath_type: netdev
>         Port vxlan_vds1-br
>             Interface vxlan_vds1-br
>                 type: vxlan
>                 options: {key=flow, local_ip="3.3.3.70", remote_ip=flow, 
> tos=inherit}
>         Port tapVm72
>             tag: 0
>             Interface tapVm72
>                 type: dpdkvhostuserclient
>                 options: {vhost-server-path="/var/run/openvswitch/tapVm72"}
>         Port mitapVm72
>             Interface mitapVm72
>         Port tapVm71
>             tag: 0
>             Interface tapVm71
>                 type: dpdkvhostuserclient
>                 options: {vhost-server-path="/var/run/openvswitch/tapVm71"}
>         Port vds1-br
>             Interface vds1-br
>                 type: internal
>     ovs_version: "3.2.1"
> 
> 3、dpcls:
> 
> [[root@localhost openvswitch-3.2.1]# ovs-appctl dpctl/dump-flows -m | grep tap
> 
> ufid:21fadb70-e3c1-4a2c-a0db-a042daa051c4, 
> recirc_id(0),dp_hash(0/0),skb_priority(0/0),in_port(tapVm71),skb_mark(0/0),ct_state(0/0x30),ct_zone(0/0),ct_mark(0/0),ct_label(0/0),packet_type(ns=0,id=0),eth(src=52:54:00:67:d5:61,dst=52:54:00:9a:bf:ed),eth_type(0x8100),vlan(vid=100,pcp=0/0x0),encap(eth_type(0x0800),ipv4(src=2.2.70.1,dst=2.2.70.2/255.255.192.0,proto=1,tos=0/0,ttl=64/0,frag=no),icmp(type=0/0,code=0/0)),
>  packets:4388, bytes:447576, used:0.420s, dp:ovs, actions:tapVm72, 
> dp-extra-info:miniflow_bits(5,2)
> 
> ufid:83a55534-3c62-4415-9aa7-bd8486675c68, 
> recirc_id(0),dp_hash(0/0),skb_priority(0/0),in_port(tapVm72),skb_mark(0/0),ct_state(0/0x30),ct_zone(0/0),ct_mark(0/0),ct_label(0/0),packet_type(ns=0,id=0),eth(src=52:54:00:9a:bf:ed,dst=52:54:00:67:d5:61),eth_type(0x8100),vlan(vid=100,pcp=0/0x0),encap(eth_type(0x0800),ipv4(src=2.2.70.2,dst=2.2.70.1/255.255.192.0,proto=1,tos=0/0,ttl=64/0,frag=no),icmp(type=8/0,code=0/0)),
>  packets:4388, bytes:447576, used:0.420s, dp:ovs, actions:tapVm71, 
> dp-extra-info:miniflow_bits(5,2)

_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to