Hi,
This is a pointer to the error message popping up even when the
environment variable WIRESHARK is set right to /usr/include/wireshark
[export WIRESHARK=/usr/include/wireshark], as in my case -
PAX-SDN-vm
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss:~/of-dissector/src$
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.