OVS does provide metadata. You are not seeing it because you're setting
metadata after sending the packet.
On Fri, May 13, 2016 at 07:10:06PM +0300, Alexander Beetle wrote:
>
>
> Got it. Thank you.
> OFPXMT_OFB_METADATA would also work for my goal. But tests show that metadata
> is not sent as well.
>
> On switch:
> $ sudo ovs-ofctl -O OpenFlow13 dump-flows s2
> OFPST_FLOW reply (OF1.3) (xid=0x2):
> cookie=0x0, duration=12.958s, table=0, n_packets=0, n_bytes=0,
> priority=1,udp,tp_dst=30012
> actions=CONTROLLER:65535,write_metadata:0x1/0xffffffff
> On controller:
> PACKET IN ARRIVED
> OFPPacketIn received: buffer_id=ffffffff total_len=220 reason=ACTION
> table_id=0 cookie=0 match=OFPMatch(oxm_fields={'in_port': 1})
>
> >Пятница, 13 мая 2016, 18:14 +03:00 от Ben Pfaff <b...@ovn.org>:
> >
> >On Fri, May 13, 2016 at 12:19:34PM +0300, Alexander Beetle wrote:
> >> Running OF1.3, I set match condition to OVS with certain flow
> >> specification and an instruction to send that flow to a controller.
> >>
> >> $ sudo ovs-ofctl dump-flows s2
> >> NXST_FLOW reply (xid=0x4):
> >> cookie=0x0, duration=22.075s, table=0, n_packets=0, n_bytes=0,
> >> idle_age=22, priority=1,udp,tp_dst=30012 actions=CONTROLLER:65535
> >> <skipped> I want to know which match condition has been triggered and
> >> expect that PACKET_IN will include the whole OFPMatch condition
> >> in oxm_fields, but it only contains incoming port.
> >
> >OpenFlow doesn't provide that information.
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
