[ovs-dev] why ovs can't send packets to in_port.

nickcooper-zhangtonghao nic at opencloud.tech
Sat Jun 10 01:53:57 UTC 2017


Thanks.

> On Jun 10, 2017, at 12:44 AM, Ben Pfaff <blp at ovn.org> wrote:
> 
> On Fri, Jun 09, 2017 at 08:28:41PM +0800, nickcooper-zhangtonghao wrote:
>> 	Why OvS does not support that we output a packet to a port which it is coming from.
>> In the case, eth1 can receive vlan1 and vlan2 packets and I hope when receiving packets, 
>> ovs can strip vlan1 packets, push it vlan2 and send it to eth1, and strip vlan2 packets,
>> push it vlan1 and send it eth1. 
>> 
>> openflow:
>> ovs-ofctl add-flow br-trans priority=100,in_port=1,dl_vlan=1,actions=strip_vlan,mod_vlan_vid:2,output:in_port
>> ovs-ofctl add-flow br-trans priority=100,in_port=1,dl_vlan=2,actions=strip_vlan,mod_vlan_vid:1,output:in_port
>> 
>> I guess it is necessary to support that feature. If not, we can doc the ovs-ofctl manpage for more detail.
> 
> The manpage already mentions this.  The FAQ has lots of detail:



More information about the dev mailing list