I want to add a new 2 byte long matching field, that is only available when a certain ethertype is indicated. I followed the suggestions made in the FAQ for adding a new matching field. Unfortunately, it does not work so far.
I try to configure a flow using ovs-ofctl add-flow. The command does know my matching field. In case of a typo or an invalid value it complains as expected. Furthermore, I can see the desired values of my match when I debug the add-flow command, especially the message that is transmitted using openflow. There I can see the ethertype, match field value, masks, vendor id of the experimenter extension and so on.
But the issue is that dump-flows does not show the match field. The relevant flow only matches the necessary ethertype. When I test this using mininet, it behaves exactly as dump-flows indicates.
What do I miss in my implementation? Any help is highly appreciated.
Thanks for the fast response. At the moment, the code is not presentable. I will come back later with it. Feel free to close this issue.
Kind regards
Andreas
I want to add a new 2 byte long matching field, that is only available when a certain ethertype is indicated. I followed the suggestions made in the FAQ for adding a new matching field. Unfortunately, it does not work so far. I try to configure a flow using ovs-ofctl add-flow. The command does know my matching field. In case of a typo or an invalid value it complains as expected. Furthermore, I can see the desired values of my match when I debug the add-flow command, especially the message that is transmitted using openflow. There I can see the ethertype, match field value, masks, vendor id of the experimenter extension and so on. But the issue is that dump-flows does not show the match field. The relevant flow only matches the necessary ethertype. When I test this using mininet, it behaves exactly as dump-flows indicates. What do I miss in my implementation? Any help is highly appreciated.