[ovs-dev] Async Packet-In message not received after OpenFlow15 Packet-Out message

[Vasundhara G]

Hi Team,

Does OVS 2.5+ support Packet-In asynchronous message for OpenFlow 1.5?

A brief background-I am working on OpenFLow 1.5  Ext- 427 in OpenVSwitch. 
Ext- 427 -  It supports setting all pipeline fields of the packet in the  Packet-Out message.
1. It adds new packet-out message for OF 1.5.
2. Moves in_port field inside match structure.
3. Adds pipeline fields in match structure.

To test encoding-decoding of pipeline fields, the following commands are sent :

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ovs-ofctl -O OpenFlow13 monitor br0 --detach --no-chdir --pidfile
ovs-appctl -t ovs-ofctl ofctl/send 0409000c0123456700000080
ovs-appctl -t ovs-ofctl ofctl/barrier
ovs-appctl -t ovs-ofctl ofctl/set-output-file monitor.log
ovs-ofctl  -O OpenFlow15 packet-out br0 CONTROLLER  'set_field:0xfafafafa5a5a5a5a->metadata, controller'  '0001020304050010203040501234'
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

In return,  decoded pipeline fields and OFPT(1.3) asynchronous Packet-In message are expected.
The pipeline fields are encoded-decoded successfully but OFPT(1.3) asynchronous Packet-In message is not received. 

I debugged the issue and found that the length of Guarded list is received as zero. Is this in any way related to the data sent in Packet-out message?

--
Regards,
Vasundhara
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you