Thanks for your help, it seems an issue from Brocade hardware switch that
reply wrong field.
It works fine with Open vSwitch software switch.
2016-04-14 10:49 GMT+08:00 Ben Pfaff :
> On Thu, Apr 14, 2016 at 10:41:47AM +0800, Dickens Yeh wrote:
> > 2016-04-14 2:40 GMT+08:00 Ben Pfaff :
> >
> > >
On Thu, Apr 14, 2016 at 10:41:47AM +0800, Dickens Yeh wrote:
> 2016-04-14 2:40 GMT+08:00 Ben Pfaff :
>
> > On Wed, Apr 13, 2016 at 05:17:03PM +0800, Dickens Yeh wrote:
> > > I have use the tool ovs-ofctl to dump flows.
> > > When I dump, if the flow have match the nw_proto with 17, it shown
> > **
2016-04-14 2:40 GMT+08:00 Ben Pfaff :
> On Wed, Apr 13, 2016 at 05:17:03PM +0800, Dickens Yeh wrote:
> > I have use the tool ovs-ofctl to dump flows.
> > When I dump, if the flow have match the nw_proto with 17, it shown
> ***parse
> > error*** like this.
> >
> > ovs-ofctl dump-flows tcp:192.168.1
On Wed, Apr 13, 2016 at 05:17:03PM +0800, Dickens Yeh wrote:
> I have use the tool ovs-ofctl to dump flows.
> When I dump, if the flow have match the nw_proto with 17, it shown ***parse
> error*** like this.
>
> ovs-ofctl dump-flows tcp:192.168.130.74:6633 -O OpenFlow13
> 2016-04-13T08:54:43Z|
Dears,
I have use the tool ovs-ofctl to dump flows.
When I dump, if the flow have match the nw_proto with 17, it shown ***parse
error*** like this.
ovs-ofctl dump-flows tcp:192.168.130.74:6633 -O OpenFlow13
2016-04-13T08:54:43Z|1|ofp_util|WARN|OFPST_FLOW reply bad match
OFPST_FLOW reply (OF1.3
This is what I get, I am wondring if it is ok ?
ovs-ofctl dump-flows mybridge -O OpenFlow13
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0x0, duration=47.815s, table=0, n_packets=619, n_bytes=88743,
priority=1 actions=CONTROLLER:65535
cookie=0x0, duration=46.332s, table=0, n_packets=0, n_bytes=0,
The error you saw still indicates a bug. What actions were there?
On Tue, Mar 01, 2016 at 06:22:29AM -0800, David Gabriel wrote:
> I fixed this issue.
> In fact I have to use the -O option to specify the openflow version
> ovs-ofctl dump-flows mybridge
>
> *-O OpenFlow13*
> Thanks.
>
> 2016-03-
I fixed this issue.
In fact I have to use the -O option to specify the openflow version
ovs-ofctl dump-flows mybridge
*-O OpenFlow13*
Thanks.
2016-03-01 2:15 GMT-08:00 David Gabriel :
> Dears
>
> I have an issue when I use ovs-ofctl dump-flows command to display flows.
> In fact I am using ryu c
Dears
I have an issue when I use ovs-ofctl dump-flows command to display flows.
In fact I am using ryu controller to set writing metadata instruction. From
the controller side all is fine but when I try to display the flows basing
on the aformentionned command I get the following error but I disab
