How did that flow get added? I don't think that OVS datapaths support
wildcarding eth_type.
On Thu, Nov 23, 2017 at 05:55:35PM +0800, 焦利涛 wrote:
> Hi all:
> how does the match with flow table work?
> such as:
> #ovs-dpctl dump-flows
> # in_port(2),eth_type(0/0x0000), packets:0, bytes:0, used:never, actions:3
>
> if there is a package from port 2, but it doesn't go to port 3.
> why does it not work?
>
> ------------------ 原始邮件 ------------------
> 发件人: "Aaron Conole";<acon...@redhat.com>;
> 发送时间: 2017年11月14日(星期二) 凌晨0:48
> 收件人: "Ben Pfaff"<b...@ovn.org>;
> 抄送: "焦利涛"<309569...@qq.com>; "bugs"<b...@openvswitch.org>;
> 主题: Re: [ovs-discuss] ovs-dpctl problem
>
>
>
> Ben Pfaff <b...@ovn.org> writes:
>
> > On Mon, Nov 13, 2017 at 11:21:38AM -0500, Aaron Conole wrote:
> >> "焦利涛" <309569...@qq.com> writes:
> >>
> >> > Hi ：
> >> > I have a problem that when i use the ovs-dpctl to add a flow into
> >> > datapath, it occurs "ovs-dpctl:
> >> > parsing flow key (Invalid argument)"
> >> >
> >> > example:
> >> > root@jlt:~# ovs-dpctl add-flow system@myDP
> >> > "in_port(1),eth_type(0x800),ipv4
> >> > (src=172.31.110.4,dst=172.31.110.5)" 2
> >> > ovs-dpctl: parsing flow key (Invalid argument)
> >>
> >> You may be able to use 'dmesg' to see which key is missing.
> >
> > I believe that this particular error comes from the userspace parser,
> > not the kernel.
>
> Seems you're correct.
>
> Even more, using the supplied command:
>
> 11:45:39 aconole {master} ~/git/ovs/lib$ sudo ovs-dpctl add-flow myDP
> "in_port(1),eth_type(0x800),ipv4(src=172.31.110.4,dst=172.31.110.5)" 2
> 11:45:57 aconole {master} ~/git/ovs/lib$ sudo ovs-dpctl dump-flows
> in_port(1),eth_type(0x0800),ipv4(src=172.31.110.4,dst=172.31.110.5),
> packets:0, bytes:0, used:never, actions:2
>
> Maybe there's an issue with whatever OvS version is being used (although
> I don't know of any such issues).
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
