Thanks! The change to oxm_serialize_header helped immensely.
I'm working on adjusting the tablefeatures test packet_data. I'll
also test experimenter oxm id's.
-Bill
On Tue, Apr 4, 2017 at 9:59 PM, Iwase Yusuke wrote:
> Instead, I guess we need to extend ofproto.oxm_serialize_header() to
> i
Hi Bill
Thank you for your report!
On 2017年04月05日 12:20, William Fisher wrote:
> When an OXM id is serialized in a table features request, the OXM
> header that is serialized sets the oxm_length to 0. That is, the OXM
> id for "eth_dst" is sent as
>
> 8600 instead of 8606 (the last byt
When an OXM id is serialized in a table features request, the OXM
header that is serialized sets the oxm_length to 0. That is, the OXM
id for "eth_dst" is sent as
8600 instead of 8606 (the last byte is the length of the value).
There's a comment in the code that explains the issue was un
