Flow-mod replies? Maybe because they are associated with a Flow-removed
message sent by the switch? Not sure. Usually, messages initiated by the
controller that don't expect a reply, should have xid=0 if I'm not mistaken.
The buffer_id is necessary if the switch is configured to buffer packets so
Thanks for the reply, this makes sense. What still creates some confusion,
though, is the fact that ODL controller does use some non-zero xid in its
FLOW_MOD replies. But this might be more of ODL's issue.
What I am trying to do is find a simple way to match OpenFlow requests and
responses in orde
Hi.
I think that the xid is only used in messages that are considered
"requests" (mainly from the controller) and require a reply.
Because a PacketIn is not a request, it is an "asynchronous" message, it is
not "mandatory" to set a xid.
Nikos Anastopoulos escreveu no dia quinta, 28/04/2016
às 16:
Hi,
I am exploring traffic captures from tests with Mininet/Openvswitch 2.5 and
OpenDaylight controller, and try to understand why the transaction ID (xid)
field in PACKET_IN messages is always zero, while for the rest message
types (either switch- or controller-initiated) it is correctly set to s
