Rob Sherwood rob.sherwood@... writes:
Hi Gopal,
What you're doing seems to be right, but my (very arbitrary) guess is
that you either have some endian issues or are not packing the message
correctly. The way to check is to grab the openflow wireshark
dissector from the openflow
Hi all
What is the expected/standard way to handle error messages to flow_mod
requests?
If they are treated as SYNC messages, then my application would have to wait for
an ack. But if the switch has happily accepted the flow_mod, it does not send
back anything - causing my app to hang forever.
Hi,
The choice is yours.
To do a synchronous call, send the flow_mod followed up a
barrier_request. You will get the barrier_reply back.
To do asynchronous calls, just send the flow_mod and wait for error
messages. The error messages should carry the same xid (transaction
id) as the flow_mod
